Replies: 1 comment
-
|
This API is fairly new and when it was released I felt like it's the same as calling a separate process, so I kept the separate process to guarantee that ram and vram will be cleared on finishing, but you raised some good points |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Is there a reason that demucs.separate is called via a os.system() call rather than keeping it internal to the existing python process using the method described in the documentation??
My guess is it's just as a convenience as the current way was the first method listed in the documentation. I'm thinking of bringing it internal so that the scripts can respect CUDA_VISIBLE_DEVICES more easily and/or be able to pass a cuda device ID in so that all models and processes respect the selected cuda device.
Beta Was this translation helpful? Give feedback.
All reactions