Repository navigation
Conversation
Main's requiredLibraries (OpenWhispr#1687) already verifies a pack's companion libraries after install, and since OpenWhispr#2501 a pack on disk that lacks them is reported as needing an update. A parallel requiredFiles list skipped that, so a binary-only whisper.cpp 0.0.10 Linux pack read as never downloaded and got the first-time offer instead of "GPU pack needs re-downloading". The libraries are copied by the existing libPattern; the CUDA EULA that whisper.cpp#7 adds to the zip is no longer copied into the pack folder.
The fallback reason assumed every failed GPU start exited or timed out. A server that came up on the CPU with no error in its log (only "no GPU found") was saved as "startup timed out after 30 s". Say that the GPU backend never initialized instead; a log line naming the cause still wins.
…n the GPU Distro packages such as the AUR's openwhispr-cuda replace the bundled whisper-server with a CUDA build. It already transcribes on the GPU, yet Settings and the Home banner kept offering the pack (OpenWhispr#2168). The server now says when a start without pack flags comes up on a GPU. The status IPC reports it, and both offers stand down. The banner re-checks once the launch pre-warm is up.
The orphan notice ("GPU pack needs re-downloading") is for packs that data
loss removed. A pack that failed here and then vanished, like the CUDA pack
the AUR openwhispr-cuda launcher deletes on every start, isn't one, and the
notice sent users back to a download that had just failed (OpenWhispr#2168).
… tests Main added the Arabic locale and the GPU card tests after this branch was cut. Arabic lacked the six per-backend keys, so the card fell back to English there, and the card tests still expected the generic "GPU acceleration ready" / "Enable GPU" copy.
A Vulkan pin to a device that is gone (OpenWhispr#1606) makes whisper.cpp start on the CPU. The new backend check counted that as a Vulkan failure before the pin could be cleared, so the user stayed on CPU and Retry failed the same way. Settle the pin first. Also cover the startup CUDA -> Vulkan move and the Linux library path.
Restarts merge the resolved GPU options over the last start's. A fallbackToVulkan left out when false kept the old true, so after deleting the Vulkan pack a CUDA failure started the CPU binary as "Vulkan" and recorded a Vulkan failure.
The failure was saved, but open GPU cards only noticed through their 5 s server poll, which switches the backend wording but doesn't re-read the packs' status. Tell them to re-read at once, as every other GPU change does, and keep the CPU pop-up for real CPU fallbacks.
- The GPU card's status poll only ends "activating" again. Taking the pack and failure state from the server mislabelled a failed pack once a bundled GPU build was running, and Remove then deleted the other pack. The status-changed broadcast already moves the card after CUDA -> Vulkan. - A failed pack that has vanished loses its enabled flag at launch, so the orphan notice stays away after the upgrade reset clears the failure. - A GPU pack failure that lands on the bundled server reports the backend it actually runs on, and no "switched to CPU" pop-up shows when that is a GPU build.
|
Hey @IdrisGit, I pushed some commits on top of this. #2168 (the AUR
Each fix has a test that fails without it, with two gaps: the launch-time flag drop runs in
This still needs OpenWhispr/whisper.cpp#7 merged and released, then the |
|
@boseq I have resolved the conflict in whisper.cpp#7. Thanks for the heads-up about the release dependency. Once OpenWhispr/whisper.cpp#7 is merged and released, I’ll update |
Summary
Release dependency
This PR depends on the corresponding OW-whisper.cpp PR: OpenWhispr/whisper.cpp#7
The whisper.cpp PR must be merged and released first. After its release is published, this PR must update
WHISPER_CPP_TAGand the matching SHA-256 digest insrc/helpers/whisperCudaManager.jsbefore it can ship.Validation
npm run dev.Follow-ups for #2168 (boseq)
requiredLibraries, so an installed 0.0.10 pack shows "GPU pack needs re-downloading".openwhispr-cudapackage), Settings and the Home banner don't offer the pack. A pack failure that lands on that server doesn't say "switched to CPU".Fixes #1415
Fixes #945
Fixes #2168
Related: #712, #126, #531.