Fallback to Vulkan for whisper.cpp in case of hipblas builds.
Is your feature request related to a problem? Please describe. When using a hipblas build, I'm always frustrated that whisper.cpp is using my CPU instead of my GPU. Unfortunately, whisper.cpp does not support ROCm or hipblas.
Describe the solution you'd like However, my AMD GPU does not only support ROCm/hipblas, but also Vulkan. Just like whisper.cpp.
Describe alternatives you've considered At the moment, I'm using a full Vulkan build to be compatible with whisper.cpp. However, I'd prefer to use ROCm when available, else fallback to Vulkan.
Technically, whisper.cpp supports ROCm. I recently changed my hardware, but before that I was able to use it directly (without a wrapper like LocalAI) with an RX 6900XT on NixOS.
I remember it didn't work right away; I was also using a Vulkan build for some time. Meanwhile, the maintainers have been making some changes, and after that, whisper.cpp started using ROCm as intended, which was evident both in the logs and in the speed.
While searching for the cause and solution, I stumbled across a change in a build variable from LLAMA_HIPBLAS to GGML_HIPBLAS, perhaps that is the problem here as well.
At least I could only find one commit with LLAMA_HIPBLAS in this repository, but none with GGML_HIPBLAS.
Here for comparison the build for the Nix package with GGML_HIPBLAS enabled and properly set rocmPackages dependencies as well as using hipcc compiler, when rocmSupport is enabled.
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days.
Can only find a GGML_HIPBLAS in a StableDiffusion-Context and LLAMA_HIPBLAS seems to be gone.
At first I thought there might be automatic detection now.
Based on the information in PR #5344, I suspect that whisper acceleration is not yet supported for ROCm.
@TimoStolz can you confirm this?
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days.
This issue was closed because it has been stalled for 5 days with no activity.