Bug Report [BUG] Mic Audio Defunct on Reconnect

[FerretBomb]

This has been a standing issue for some time; even if it's a minor glitch, it's still annoying to realize that you've been talking to yourself for a minute or two.
---
On getting dropped/disconnected from Twitch and reconnecting (auto or manual), the Mic audio channel becomes defunct. No sound is captured from it at all, though it is not muted. The bar does not move at all, and no mic audio is sent out on the livestream.

Workaround:
-Muting and then un-muting the mic in OBS restores it to normal service.

Reproduction steps:
1) Start livestream. Confirm mic is working.
2) Disconnect ethernet cable or WAN until OBS detects that it has lost connection to the server.
3) Reconnect ethernet/WAN and allow the auto-reconnect to establish connection.
4) Problem is presented.

Occurs both with USB microphones and standard on-board integrated audio. Other programs do not lose mic signal at any point (tested with Teamspeak and Steam). Occurs whether or not other programs are using the mic at the time.

 

[Lain]

Hm, I tried to do this and I couldn't replicate. Can anybody else who might read this try to replicate this, if you guys have time?

I don't know why this is happening to you, I feel like we'd have a lot of reports of this happening if this were happening to everybody, but why on earth would it be happening to you specifically? I'm really confused at the moment. I'll ask around to see if anyone else can get this happening.

 

[FerretBomb]

Not sure, but it only happens on disconnect/reconnect. I can't recall if it does it if I manually halt the stream and restart it, or only if it's an unexpected connection-loss to Twitch.
I have some oddities that might be related as well, but they're minor; mostly OBS 'forgetting' the state the mic was left in the last time it was shut down. Normally manifesting with a live mic at random, when I always end cast and close out with it muted. Can just re-mute it, but figured it was out of the ordinary.

Tossed on a logfile of when it happened during the recent Twitch maintenance if that'll help at all, and here's a link to the VOD of the return. http://www.twitch.tv/ferretbomb/b/528965785
I remembered to mute/unmute, so the problem really isn't visible, but if it helps with completeness, may as well. Again, system audio is fine... but I've tested this with my mixer (USB interface), a USB mic, and my analog mic plugged into the onboard audio. It's just the mic channel. Haven't tried it with stereo mix, but... not sure what good that would do.

Only obvious bit I can see in the logs is the mixer being behind in timestamps by a small amount, but that was happening before the disconnect too.

 

[R1CH]

Your scene buffering time is really low, is there a reason why you changed it? Try with it back to the default of 700.

 

[FerretBomb]

I haven't changed it. That used to be the default.
My settings have been carried forward since almost my initial install of OBS. I saw no real need to raise it as it wasn't causing any problems, and when Jim explained what it actually did a while ago, I didn't really qualify, and the low buffering time wasn't causing any of the issues that motivated the new-default of 700. Is there a good reason from the logs that you can see to bump it up to the new default value, or just troubleshooting via standardization?

 

[XeiZ]

I actually have the same issue sometimes but i couldnt pinpoint what causes it (i rarely ever auto reconnect) and my scene buffer is normal. Since i use VB cable as input i thought it had something to do with that but apperantly im not the only one huh. However i cant reproduce it since it doesnt happen on autoreconnect to me, will pay more attention to it from now on.

 

[FerretBomb]

Still nada as far as this goes? Still happening on the most recent version.