You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that the NexaVoiceInference class hardcodes the device to "cpu", making it impossible to use a GPU for inference. I suggest adding a device argument to allow switching between "cpu" and "cuda". Here’s the proposed change:
Sure, we will add the option to support using huggingface transformer style usge of CUDA, such as cuda:0 in our next release. Now all GPUs are used by defaults, if you use CUDA compilation options.
I did use CUDA compilation options (CMAKE_ARGS="-DGGML_CUDA=ON -DSD_CUBLAS=ON"). NexaTextInference, for example, do use GPU by default, but this is in NexaVoiceInference class:
I did use CUDA compilation options (CMAKE_ARGS="-DGGML_CUDA=ON -DSD_CUBLAS=ON"). NexaTextInference, for example, do use GPU by default, but this is in NexaVoiceInference class:
We hard-coded "cpu" here because to enable cuda for faster-whisper, wither cuBLAS or cuDNN is needed on your machine. Currently we cannot build this into our sdk. If we change "cpu" to "cuda" or "auto", it won't work because of lack of dependency.
However, you can achieve to run on cuda by doing this:
Refer to the faster whisper official github to know how to install cuBLAS or cuDNN as the dependency required by GPU running.
Change our python source code (on your machine, not through pull request) either in your environment packages or through pip install -e ., locate this issue and change "cpu" to "auto" or "cuda". And it should work for you then.
Thank you for your question and we will be committed to thoroughly solve this problem in the near future.
I noticed that the NexaVoiceInference class hardcodes the device to "cpu", making it impossible to use a GPU for inference. I suggest adding a device argument to allow switching between "cpu" and "cuda". Here’s the proposed change:
and here:
Would you be open to a pull request for this change?
Similar Features or References
No response
The text was updated successfully, but these errors were encountered: