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
Firstly thank you for the effort that has been put into localvocal so far.
Unfortunately, I've encountered a crash in LocalVocal 0.3.4 on Windows 10 with Cuda 12
Whenever this version of localvocal runs, it'll be fine until it attempts it's first transcription and then it will hard crash OBS, cause windows to do a memory dump of obs64.exe and not write anything to it's own logs.
I've traced through Windows eventvwr logs and found that this is which module is causing the crash
I notice recently that there's now some difference between the CUDA builds, since for 0.3.3 there was a CUDA 11 build and one for CUDA 12 - I've always gotten the one for 12 and that's typically worked fine for me, so could it be related to this change?
Thank you for reading and I hope you may have some ideas. Please let me know if there's anything I can provide. For now I've just rolled back to 0.3.3 and that seems to work okay. <3
The text was updated successfully, but these errors were encountered:
@accessiblepixel upgrade your Nvidia drivers
this crash has been reported, and obs v30.2.x has asked users to update Nvidia display drivers becasue of compatibility issues
@royshil Thanks for the reply. I'm already running a version higher than it says it needed to be in the OBS update, do I need to go newer than that?
I'm running a RTX3060 and driver version 536.40
Also, I noticed that when I left my computer for a while with OBS open and localvocal with 0.33 there was some kinda memory leak happening after a few hours.
Hi.
Firstly thank you for the effort that has been put into localvocal so far.
Unfortunately, I've encountered a crash in LocalVocal 0.3.4 on Windows 10 with Cuda 12
Whenever this version of localvocal runs, it'll be fine until it attempts it's first transcription and then it will hard crash OBS, cause windows to do a memory dump of obs64.exe and not write anything to it's own logs.
I've traced through Windows eventvwr logs and found that this is which module is causing the crash
I notice recently that there's now some difference between the CUDA builds, since for 0.3.3 there was a CUDA 11 build and one for CUDA 12 - I've always gotten the one for 12 and that's typically worked fine for me, so could it be related to this change?
Thank you for reading and I hope you may have some ideas. Please let me know if there's anything I can provide. For now I've just rolled back to 0.3.3 and that seems to work okay. <3
The text was updated successfully, but these errors were encountered: