![]() So it's possible that a change made in how OBS Studio does things in some area unrelated to USB directly (buffer sizes or any other not-exposed knob even) could be what's allowing this crash to occur, because it's doing something 'more efficiently' than other similar tools do and stressing things more. In this case you're confusing the issue I won't quote chapter and verse of invalid debate types, that's being needlessly and unhelpfully is offering to regression-test versions of OBS Studio to bisect which release introduced whatever changes began allowing it to trigger this interaction with certain X99 XHCI USB 3.0 controllers under Windows even said it's likely a hardware issue and they're okay if so but want to run it to ground to confirm and it doesn't happen with older versions of OBS Studio. Likewise, if there's any way to have a debug version to see exactly what's going on, and dump the last actions taken by OBS prior to specific USB devices disappearing (maybe a rolling FIFO log of the last 5-30 seconds?), I'm more than happy to be a guinea pig to help run down what appears to be a niche and hardware-related issue.Īnd not only because my only other options are to build a new machine, stay on Classic forever, or move to xsplit. I'm willing to go through the older versions one by one until the issue starts cropping up, but with the intermittent nature and lack of reliable steps to reproduce other than 'start and let it run for a few hours', testing could take quite some time. But it's been one of the largest irritations while streaming, especially when a good track comes on.) namely the ability to sync the webcam, mic, system audio and gameplay together, so I can hum along with game music. With the addition of the ability to delay Game Capture sources in 19, there was finally a compelling reason to switch and deal with the hotkey codex. Though to be fair I didn't use 14 extensively just to check up on the features added. Prior to 19.0.3, the last I'd tested was 14.?, which didn't have the issue. For a long while I was only checking every few major versions and just using Classic due to a lack of needed new features. Does appear to consistently happen when trying to access my Behringer mixer, or at least that seems to be the most common last-line in the log.Ĭlick to expand.I haven't tried. ![]() ![]() Am open to troubleshooting, issue is semi-reproducible if intermittent on how long it takes to occur. Only the USB devices do, rendering the system unusable aside from RDP (no PS/2 keyboard/mouse port available).Įntirely possible that it may be the USB drivers freaking out, but it's definitely something about OBS Studio 19.0.3 accessing USB devices that causes the host controller crash. Logfile posted, crashlog unavailable because OBS itself does not crash. I have not tried any versions between 14 and 19 for an appreciable amount of time to determine if the issue existed in v16.*. Issue does not occur on Studio 14.*, or OBS Classic 0.659b 64-bit, though the same USB devices are in use on both with the same source parameters scenes manually recreated identically between the versions/revisions. Some devices do maintain powered-on status (Logi BRIO, n52te speedpad) but cannot control/pass data. Unplugging/replugging devices after the issue does not reconnect them. Only occurs when Studio is loading/loaded, and occurs erratically can take 10 seconds, or 4 hours. (Also on machine but unused: ASMedia USB 3.1 eXtensible Host Controller - 1.10)Įrratically after starting OBS Studio 19.0.3, all USB devices will disconnect/depower. Intel(R) USB 3.0 eXtensible Host Controller - 1.0 (Microsoft)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |