#Mic too low obs studio windows 10 code#

I can confirm that deactivating the monitoring and re activating it suppresses the delay.

Every input uses the same monitoring channel (obviously).

IвЂ™m using my default audio for loopback, I havenвЂ™t configured anything fancy вЂ¦.

The graphical db meter stays synced all the time (every sources are synced, a clap is a good test).

The streaming isnвЂ™t affected nor the recording only the monitoring.

At the begining all audio are synced and time passing they become unsynced with huge delay for some. As an example IвЂ™ve added three audio input (USB webCam, wired jack mic and, phone through wifi). After some tests I discovered that not all audio source behave in the same way. I first noticed the progressive lag while I was streaming. IвЂ™m all but an expert on PA and how sound is being played on linux. IвЂ™m facing the same problem (increasing monitoring delay). What would be a good way to debug that?ДЇinally: should we reopen this issue or open a new one? OBSstudio should, after all, work with the default configuration of major distributions, or at least recognize this being a problem and possibly display a warning. The other question apart from OBS going back to less latency would be why this is building up in the first place. Your comment makes me think it might actually adapt to pulseaudio increasing, but does not recognize that is might also decrease. It looks to me like OBS is doing some internal buffering as well, which is increasing, too. The only way I found so far is to close and re-open OBSstudio. Suspending/unsuspending the null-device gets rid of the built-up latency in pulseaudio, but there is still latency left. Monitoring the latency in the output of 'pactl list sinks' shows the 'configured latency' increasing in steps up to 2 seconds. After some time (a few minutes at most), it is a few seconds. Right after creating the device, latency is there, but small. I use a null-device to create something for OBS to shove into.

I found this thread because I have a similar (the same?) problem.

#Mic too low obs studio windows 10 code#

Im not sure precisely how that code works. Its also possible we dont handle resizing our buffer when notified of increases on the other side (which might be why it continues to grow past a reasonable size).