Crashes OBS 27.2.0 Every Time #58
Comments
|
Same with OBS 27.2.1 |
|
Smells like a binary incompatibility problem. I would re-build the windows binaries if I knew how. Is there a vm image or something to start with? |
|
I've tried reaching out to kounoike on Twitter but I haven't gotten a response. I've used the plugin a lot and would like to see it updated and maintained |
Same problem to me, look into the details |
|
I can't reproduce with OBS 27.21 / obs-virtualbg v1.1.0. it works fine. |
|
to all, please provide
|
|
OBS: 27.2.1 x64 (fresh install) Log 2022-02-24 17-44-06 |
OBS version: |
|
|
@kounoike |
|
ah... I forgot GitHub's auto-close rule. @Stifler82 |
|
at #58 (comment) I said, "I can't reproduce". so I can't test it. |
|
I tried your artifact; it works fine on the old version of OBS, but still fails on 27.2.2, but differently. The log contains many entries of: The window for editing the filters is black. |
|
hmm... it seems as OnnxRuntime's problem. How about this artifact? it updates onnxruntime 1.9.0=>1.10.0, obs-27.2.2 |
|
I updated OBS with the OnnxRuntime from above and OBS is now crashing with the detection filter is enabled. I attached the crash and log files. BTW, is there a relatively easy way to build this from a vm or docker image? |
|
@mfgering hmm... it maybe OnnxRuntime's issue. But, I can't reproduce it. GitHub Actions build workflow is easy point to understand how to build. But, it requires building OBS. so, you should read obs's build requirements |
|
and error msg shows this line |
Ok So The artifact works but by defualt it starts out using the GPU and wont show anything. Unchecking the box makes it act as it should but now its showing OBS as using 30%+ cpu usage. Checking the GPU box doesnt seem to have any effect |
|
Crashes OBS version 27.2.3 (64-bit) on Windows 10 Pro as well. Steps to reproduce:
=> will reliably crash |
|
please read this comment: #58 (comment) |
|
Hi, all. |
It works for me. |
Quickly tried the CUDA version with 27.2.3 and it appears to work. |
|
The cuda version seems to work but still uses 38% cpu even with the GPU selected. The masking looks nicer and is much more responsive though. Am I missing someing? |
|
what about intel igpu users? |
|
updating win11 is best workaround. |
|
@zenvolta please upload log file. |
|
|
crashes OBS 27.2.3 too |
|
@mightysashiman logfile? |
|
Another crash report for OBS Studio 27.2.3 and obs-virtualbg 1.1.0 Unfortunately for me the CUDA version is not an option as I run a Radeon GPU. |
|
I tried the latest build; when enabling the "Use GPU" flag, the CPU load remains the same and this pops up in the log: (the error message translates to "No such interface supported" - and its return code is E_NOINTERFACE) |
|
Hmm, microsoft/onnxruntime#6457 hints that it might be loading the wrong DirectML... |
|
@ElSaico You have a chance of contributing PR which support ROCm/MIGraphX 😁 DirectML dll is already included. So, 6457 is not related issue, maybe... |
Seems like ROCm (and thus MlGraphX) is Linux-only at this point, unfortunately - which is not an option for half the stuff I livestream. |
|
OBS version: 27.2.3 (64-bit) |
|
not owrking for me on 27.2.4 on windows, if someone could supply the cuda version mentioned above that would be helpful |
|
same problem and same question. |
|
This all sounds consistent with what I was just experiencing setting up 1.1.0 on OBS 27.2.4. |
Using the CUDA build for Windows from this artifact, I was able to finally add the filter without crashing thanks to this tip. OBS still crashes when I enable "Blurring mask edge" though. With that option disabled, everything else seems to work fine. |
|
All of the artifacts are expired so can't test the cuda one? Anyway to fix this reliably? |
|
I am still having the same error when trying to use the GPU option. Log file attached. 16:50:52.960: [Virtual BG detector] Can't create Session error: Exception during initialization: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Upgraded OBS to 27.2.0 and this plugin crashes it every time I enable the virtual background detector filter.
This is easy to reproduce. Simply add the detector filter and enable it. Boom!
The log complains:
The crash report complains:
Thread 6C28: libobs: graphics thread (Crashed)
2022-02-16 07-14-30.txt
Crash 2022-02-16 07-14-45.txt
The text was updated successfully, but these errors were encountered: