During almost every streaming session, at least one of my audio sources go out sync with the video. I check my log (https://obsproject.com/logs/TDOJpKFEnXGg4iv3) and I see messages like "adding [x] milliseconds of audio buffering, total audio buffering is now [x] milliseconds." I'm using Application Audio Capture (BETA) to capture Discord and game audio, but sometimes it even happens with my microphone, ("_K66 Microphone" in the logs), which I use as a scene-level Audio Input Capture. (The microphone lag is consistently only 40-60ms which I can live with.) While this seems to happen more often with Application Audio Capture (BETA), it still even happens sometimes when I don't use discrete capture sources and route applications through Desktop Audio. I reboot my machine fresh before each stream, enable Game Mode in Windows and my antivirus (ESET), load OBS as administrator, and generally try to have any games or programs relevant to the stream already open prior to starting my stream or recording. In earlier tests I would sometimes get a Max Audio Buffering error, which I've read can be indicative of high CPU activity, but at no point during stream or test recordings has my CPU been anywhere near 100% utilization. I've got the games' frame rates and other settings configured to keep my GPU usage at-or-below 80%, even while recording/streaming.
In a perfect world I could pinpoint and prevent these kinds of buffering hiccups entirely, but barring that, is there a way to "reset" an audio source while it may cut out for a split-second it'll sync back up and remove the buffering delay?
(PS: I know the overlays are tossing up all sorts of error codes in the logs; that's a separate issue that I'll work on.)
In a perfect world I could pinpoint and prevent these kinds of buffering hiccups entirely, but barring that, is there a way to "reset" an audio source while it may cut out for a split-second it'll sync back up and remove the buffering delay?
(PS: I know the overlays are tossing up all sorts of error codes in the logs; that's a separate issue that I'll work on.)