Bug: Crash on loading model #79
Comments
|
See DEBUG.md |
|
@MultipleOneLeaf |
log4-8. Maybe it's some problem with whisper. Here's the terminal log: Event Viewer logs - 2 with Vibe + 2 with Whisper: Vibe errors: Followed by Event 1005 - Application Error Whisper errors: Followed by Event 1005 - Application Error Regarding my username: |
|
Thanks!! winget install neofetch
neofetch |
|
Just for transparency's sake, on the first result it didn't detect the GPU, but after doing Note: while it says Windows 11, the problem also occurred while it was Windows 10. logsFirst result: Second result: |
|
@MultipleOneLeaf By the way, you can simply ensure if your cpu supports set RUST_LOG=vibe=trace
%localappdata%\vibe\vibe.exeIt will print it in the first message logs |
|
Unfortunately that didn't fix it for me. As can be seen in the log, my cpu supports |
|
Per the exception in event viewer you posted, the I compiled vibe again with Also added many logs to see what features the cpu support set RUST_LOG=vibe=trace
%localappdata%\vibe\vibe.exe |
|
Also didn't work. Here's the log: logs |
|
That looks better! |
|
Updated one with almost all cpu features disabled: vibe_1.0.7_x64-setup_no_avx_fma_f16c.exe set RUST_LOG=vibe=debug,whisper_rs=debug
%localappdata%\vibe\vibe.exe |
|
It works now! Here's the log just in case: logsShould I close the issue or is there anything else you'd like me to test? |
|
Amazing! I think I'll disable automatic updates for computers that don't support those instructions ( |
Let's wait to see if others have suggestions. It's interesting what the speed that you get when transcribing without those instructions (which related to optimization) |
Thank you!
On the sample you mentioned above (11 seconds of sound), it took 19 seconds. |
Meaning that one hour audio will take 1 hour and 30-40 minutes. on my CPU with optimization (no gpu) it will take 1 hour and 20-25 minutes. UpdateI released new installer for Nvidia GPUs! It's pretty heavy (300-500mb) though you don't have to install it. you can extract it with 7-zip and start |
|
Just tested with my GPU. I extracted in case it ends up making any difference in speed. The sample file took 3 seconds. I also tried then transcribing a file with 20 minutes duration - though probably only about 10 minutes worth of speech - and it took 89-90 seconds. Doing it with a different language (the one in this specific file, instead of English) it took 96 seconds. The time with CPU, from the experiment my brother did with Ryzen 5 2600 before I opened this issue, was about 40 minutes I believe. |
|
That's amazing! It's nearly as fast as high-quality transcriptions from paid APIs. Now, anyone with Nvidia GPUs can easily turn their PC into a high-quality transcription machine :) |
|
Yup. These results might be a good form of advertisement to increase interest in your project. And, in my opinion, the best part is that it is also run locally. Thank you once again for you efforts! |
|
Hello. I am using an RTX 4070 Ti Super with 7800X3D. Do I also need to install the CUDA Toolkit to use this Nvidia version you have linked? I tried the default version of Vibe, but it ran on the CPU when transcribing. However, the new Nvidia version you have linked in this reply just crashes a few seconds after clicking transcribe. |
|
@manav0619 In the section of trying original whisper you can try the following version: whisper-cublas-12.2.0-bin-x64.zip |
|
@thewh1teagle Thank you for the quick response, and apologies for being late. I am pasting below the details of the two events from Event Viewer related to the latest crash. Please let me know if you require anything else.
log``` Log Name: Application Source: Windows Error Reporting Date: 24-05-2024 22:56:38 Event ID: 1001 Task Category: None Level: Information Keywords: User: MANAV\manav Computer: Manav Description: Fault bucket 1174612636899832668, type 5 Event Name: BEX64 Response: Not available Cab Id: 0Problem signature: Attached files: These files may be available here: Analysis symbol: Log Name: Application |
|
@manav0619 instructionsa. Open `cmd.exe` b. Execute:set RUST_BACKTRACE=1
set RUST_LOG=vibe=debug,whisper_rs=debug
%localappdata%\vibe\vibe.exeAlso:
winget install neofetch
neofetch |
logs |
|
Looks like the error happens in Try to download cudnn (direct download link) If you didn't updated the driver of your GPU then also download rtx-4070_ti_super-studio-driver (direct link) |
|
@thewh1teagle logC:\Users\manav>[2024-05-25T00:24:58Z DEBUG vibe_desktop] Vibe App Running [2024-05-25T00:24:58Z DEBUG vibe_desktop::setup] webview version: 124.0.2478.97 [2024-05-25T00:24:58Z DEBUG vibe_desktop::setup] CPU Features: AVX: true AVX2: true AVX512: true AVX512-VBMI: true AVX512-VNNI: true FMA: true F16C: true [2024-05-25T00:24:58Z DEBUG vibe_desktop::setup] COMMIT_HASH: cac8c0b [2024-05-25T00:25:06Z DEBUG vibe::model] Transcribe called with { "path": "C:\\Users\\manav\\Desktop\\Audios\\samples_single.wav", "model_path": "C:\\Users\\manav\\AppData\\Local\\github.com.thewh1teagle.vibe\\ggml-large-v3.bin", "lang": "en", "verbose": false, "n_threads": 4, "init_prompt": "", "temperature": 0.4 } [2024-05-25T00:25:06Z DEBUG vibe::audio] input is C:\Users\manav\Desktop\Audios\samples_single.wav and output is C:\Users\manav\AppData\Local\Temp\.tmpAyu2jE.wav [2024-05-25T00:25:06Z DEBUG vibe::audio::encoder] decoder channel layout is 0 [2024-05-25T00:25:06Z DEBUG vibe::audio::encoder] +-----------+ | in |default--[16000Hz s16:mono]--Parsed_anull_0:default | (abuffer) | +-----------+[2024-05-25T00:25:06Z DEBUG vibe::audio] wav reader read from "C:\Users\manav\AppData\Local\Temp\.tmpAyu2jE.wav" I would also like to mention that another tool named Whisper GUI works fine and does use the GPU. I transcribed two files with it even before installing Vibe and CUDA, and had no problems. |
|
@manav0619 |
|
Reported in whisper.cpp/issues/2187 |
|
@thewh1teagle Hello. I believe there was an update in the application, which I let it install. It says vibe 1.0.9 in the settings. I am not sure if this is still the Nvidia-optimized version. But anyway, I am able to transcribe the files in this version, independent of the temperature setting. This time, it seems to be utilizing both the CPU and GPU. The process is still much slower compared to the Faster Whisper GUI I linked above, which utilizes 90+% of the GPU, with GPU temperature remaining at 50-53 °C. Vibe's GPU usage is fluctuating around 70-80%, with GPU temperature remaining at 47-48 °C. Both of these screenshots are when transcribing the same 70-minute audio file using Whisper large-v3. Vibe took almost half an hour. Faster Whisper GUI was done in around 2 minutes. |
|
Great to know that at least you it doesn't crash anymore! |
|
I added checks if the cpu is supported and if not vibe will display error message with instructions how to fix. |
What happened?
After I hit "Transcribe", the app crashes.
Since, at least from what I've noticed, there are no crash logs, here's what the cmd log shows:
log
Steps to reproduce
Tried on Windows 10 first, and now on Windows 11. Also, my brother's pc (Windows 10) for some reason has no issue with Vibe.
Could it be because I've got an old cpu (i7-3770 vs my brother's Ryzen 5 2600) or motherboard or something like that that there's some conflict happening? In case it helps, I am able to run Stable Diffusion locally without issues (both Automatic 1111 and ComfyUI).
I should also note that the user shown on the logs of Vibe is
AUTUMN~1instead ofAutumnLeaf. Since I've seen a few past issues here due to hebraic user names, perhaps the tilde (which shouldn't even be there) could be a cause.What OS are you seeing the problem on?
Window
logs
Relevant log output
App Version: 1.0.7 Commit Hash: 99ae746dc02135ad7a27ec0f9adafe016b8c96e4 Arch: x86_64 Platform: windows Kernel Version: 10.0.22631 OS: windows OS Version: 10.0.22631 Models: ggml-medium.bin Default Model: "C:\\Users\\AutumnLeaf\\AppData\\Local\\github.com.thewh1teagle.vibe\\ggml-medium.bin"The text was updated successfully, but these errors were encountered: