Audiocraft is a library for audio processing and generation with deep learning. It features the state-of-the-art EnCodec audio compressor / tokenizer, along with MusicGen, a simple and controllable music generation LM with textual and melodic conditioning.
MIT License
561
stars
63
forks
source link
Question: what is the application doing (takes long time) after GPU usage goes down to 0% ? #64
I am trying out the latest git version and I consistently see the following behavior:
when clicking "Generate" it obviously starts generating the audio, GPU usage goes up; then the following gets printed in the console where the application was started:
Make a video took 3.4332385063171387
video: PMfTuclUS4V9.mp4
batch finished 1 204.6192593574524
Tempfiles currently stored: 3
At this point I would have assumed that everything is "done", but the progress bars keep counting while GPU usage is at 0% and and CPU is at about 1%. My question is: is this normal or is this some sort of bug, what exactly is happening during this phase?
Here is what I mean:
I think GPU stops computing at about 15% if not earlier, takes only a few minutes. Then however it takes over half an hour to reach the 100% and nvtop looks like this during that time:
I am using the "melody" model, generating 30 secs via a simple console script does not show such delays, i.e. it takes the few minutes where the GPU is active, then my script saves the generated audio and exits. So this something extra must be happening in audiocraft plus and I am wondering what it is?
Hi,
I am trying out the latest git version and I consistently see the following behavior:
when clicking "Generate" it obviously starts generating the audio, GPU usage goes up; then the following gets printed in the console where the application was started:
At this point I would have assumed that everything is "done", but the progress bars keep counting while GPU usage is at 0% and and CPU is at about 1%. My question is: is this normal or is this some sort of bug, what exactly is happening during this phase?
Here is what I mean:
I think GPU stops computing at about 15% if not earlier, takes only a few minutes. Then however it takes over half an hour to reach the 100% and nvtop looks like this during that time:
I am using the "melody" model, generating 30 secs via a simple console script does not show such delays, i.e. it takes the few minutes where the GPU is active, then my script saves the generated audio and exits. So this something extra must be happening in audiocraft plus and I am wondering what it is?