-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
^C exiting right after htdemucs_mmi #14
Comments
Have you checked whether it may have something to do with too high
overlap_demucs parameters or maybe specific song (maybe it's long)?
As a workaround you can try out also 2.1 and 2.2 Colabs with input from 2.3.
pt., 16 lut 2024, 11:40 użytkownik fedenicotra ***@***.***>
napisał:
… Hi everyone. Using the link to the v.2.3 Colab Notebook and making the
separation unchecking the *vocals_instru_only*, the code terminates with
a CTRL-C like exiting, right after the htdemucs_mmi processing. Even
copy-pasting the simple instruction mentioned in the readme produces the
same behavior. I'm running the notebook with T4 GPU. Moreover I'm noticing
a huge usage of both RAM and GPU RAM.
—
Reply to this email directly, view it on GitHub
<#14>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIJ3EHED6MUJDJRUF6S4Q2DYT4ZSNAVCNFSM6AAAAABDLZ2RDGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGEZTQMZSGIYDGNA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Like deton24 said this error is often happening with long input audio, it's happening most of the time during htdemucs_6s model processing because it needs more memory than other demucs models. How long is your input ? |
I tried with a 10 minutes mp3 and even disabling the overlap and bigskips I get the same behavior. With short songs it is fine. |
Hi everyone. Using the link to the v.2.3 Colab Notebook and making the separation unchecking the vocals_instru_only, the code terminates with a CTRL-C like exiting, right after the htdemucs_mmi processing. Even copy-pasting the simple instruction mentioned in the readme produces the same behavior. I'm running the notebook with T4 GPU. Moreover I'm noticing a huge usage of both RAM and GPU RAM.
The text was updated successfully, but these errors were encountered: