Skip to content
This repository has been archived by the owner on Jan 1, 2025. It is now read-only.

Demucs is slower and lower gpu utilisation than UVR with the same model? #618

Open
MrSimmo opened this issue Sep 10, 2024 · 1 comment
Open
Labels
question Further information is requested

Comments

@MrSimmo
Copy link

MrSimmo commented Sep 10, 2024

❓ Questions

I’ve run quite a few comparison splitting jobs with both Demucs downloaded here and Ultimate Vocal Remover - both using htdemucs-ft as the model and options to use the Apple Silicon gpu.

In all tests, uvr is quite a lot quicker and looking at the cpu/gpu utilisation; uvr maxes out the gpu but demucs here never seems to go above 25% gpu utilisation.

Seems odd as I thought uvr was just a front end to the same cli tool?

Does anyone know what could be causing this and how to get demucs here to fully utilise the gpu?

Cheers

@MrSimmo MrSimmo added the question Further information is requested label Sep 10, 2024
@MrSimmo
Copy link
Author

MrSimmo commented Dec 10, 2024

Ignore this, it was caused by the version of Pytorch.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant