dmp file (if available) as well as your regular OBS log files andĪ description of what you were doing at the time of the crash. include the contents of this crash log and the Reproduce this crash, please submit this crash report on the forums at OBS has encountered an unhandled exception and has terminated. Your mileage may vary (I imagine it depends heavily on both your CPU and the devices themselves), so try playing around with various delays and see if it works for you. I've increased it to 1200ms and have since had zero issues recording microphones properly. I had previously modified this to be 400ms, but I think that might be too short. What worked for me was increasing the "scene buffering time" under Advanced in the settings of OBS (v0.637b as of writing). As I said this is completely wild speculation, I would love to hear from the developer to see if this sounds like a possible cause. This would be strange since I assume that OBS itself uses the same APIs to access those devices, but there might be some sort of conflict/race condition between the plugin and OBS accessing DirectShow sources at the same time. This is wild speculation because I haven't actually looked directly at the source code and I'm not familiar with the DirectShow API(s), but I think what is happening is that the scene attempts to capture the DirectShow devices too soon after initializing them for use, and as a result is unable to capture the audio source properly. For anyone else experiencing the audio stuttering issue, in my (exhaustive) testing and troubleshooting, I've discovered something that seems to solve the issue, at least for me.
0 Comments
Leave a Reply. |