-
-
Notifications
You must be signed in to change notification settings - Fork 215
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
BGM removal unusable #424
Comments
Hi @starloreh. The stacktrace doesn't say errors, it just says warnings, which you can ignore. The reason the progress is stuck at 0% is because it doesn't actually track the progress of the job, I just set it to 0% until the separation job is fully completed. This confusion should be avoided, I should have said so explicitly in the progress message. Actually, the model was probably working for separation, but very slowly on the CPU. The UVR models are recommended to run on GPU, not CPU. I believe the speed difference is almost more than x10. UVR models are super slow on the CPU, it's recommended to use the GPU only. If you're using Colab, you can try T4 GPU runtime (free runtime). |
There's a suspicious bug that seems to be related to this, So I guess it's related to the VAD, not the BGM separation. This is now fixed in I'm considering about installing |
This should be fixed in #428. Please feel free to reopen! |
@starloreh I just tried to reproduce it myself with 2 hours of video, but it was not reproducible. Everything worked fine on my end, even with 2 hours of video. I'm not sure what caused the problem. |
Yes. To compare I tried https://github.com/Eddycrack864/UVR5-UI with UVR-MDX-NET-Inst_HQ_5, and it almost finished till it crashed but it was another audio of 2h 20 m |
Which OS are you using?
It stays at 0% and then consumes all RAM and finally it says Error:
in My cpuonly 32G RAM 5700G, the same thing happened. What could be the cause. Just in case I converted the opus audio into mp3 and ogg vorbis in my CPU and the same thing still happened.
The text was updated successfully, but these errors were encountered: