Audio problem in live

[Croma]

Hi all, as you can see from my recording, the audio gets nasty at some point...
Do you have any idea how to fix it?

Twitch

Twitch is the world's leading video platform and community for gamers.

www.twitch.tv

(I use elgato game capture with ps4 and chatlink, but before I didn't have these problems if you look at the old live shows)

 

[AaronD]

Do you have a noise suppressor? Those things think that *any* repetitive sound is noise to be removed. If that's your problem, then what you still hear is actually considered to be a failure of the suppressor, and a need to improve it.
If you want that repetitive sound, don't noise-suppress it.

 

[Croma]

Do you have a noise suppressor? Those things think that *any* repetitive sound is noise to be removed. If that's your problem, then what you still hear is actually considered to be a failure of the suppressor, and a need to improve it.
If you want that repetitive sound, don't noise-suppress it.

The only filters I have are the ones in the microphone.
Do you think the problem is the filters set in the microphone?

 

[AaronD]

The only filters I have are the ones in the microphone.
Do you think the problem is the filters set in the microphone?

If the game comes in separately from that, then no. I ask because I've seen people slap it on everything, or combine them externally (which I often recommend because OBS's audio processing is actually quite limited) and then use it on the one combined source in OBS because the mic needs it.

Follow that signal all the way through your rig, being careful to not miss anything, and see if you run across a noise suppressor anyway. It could be that you've forgotten one in OBS, or that the game is actually coming in through OBS's mic source, or it could be that your operating system or audio driver has that feature too, that was left on.

At any rate, it does sound to me - with a magazine starting off good and then fading, then the next magazine good again and then fading - like a noise suppressor *somewhere*.

 

[Croma]

If the game comes in separately from that, then no. I ask because I've seen people slap it on everything, or combine them externally (which I often recommend because OBS's audio processing is actually quite limited) and then use it on the one combined source in OBS because the mic needs it.

Follow that signal all the way through your rig, being careful to not miss anything, and see if you run across a noise suppressor anyway. It could be that you've forgotten one in OBS, or that the game is actually coming in through OBS's mic source, or it could be that your operating system or audio driver has that feature too, that was left on.

At any rate, it does sound to me - with a magazine starting off good and then fading, then the next magazine good again and then fading - like a noise suppressor *somewhere*.

I checked everywhere.
I have no filter.
Also, I get the same problem if I record in obs software and elgato software.

Do you think it's a capture card failure?

 

[AaronD]

Also, I get the same problem if I record in obs software and elgato software.

Okay, so it's not OBS. Could still be Windoze or a driver trying to insist on being "schmart", and ending up stupid instead. Are you sure you've looked at *everything*? Some things are buried so that the id10t user that Micro$haft seems to insist on doesn't stub their toe on them.

Do you think it's a capture card failure?

Assuming HDMI, I doubt it. Picture and sound on that use the same wires.

It's based on the old analog TV standard, which had lots of dead time between lines and even more between frames, just to allow the analog circuitry to reset the line scanner and the frame scanner. And a sync pulse during that dead time ensured that the picture stayed in the right place on the screen. That's all still there on HDMI, except that the sync is now a digital code on the same wires that is not a valid color.

Like the captions on analog TV, sound on HDMI is also sent on the same wires during the dead time. So if the picture is good, so is the sound from a hardware perspective, and anything else that uses the same wires.

Even if it were a different format that sends its picture and sound on different wires, I have a hard time thinking of what else would cause that behavior. A new sound that starts perfect and then fades, then resets to perfect again when it stops and restarts, is almost certainly an intentional noise suppressor *somewhere*. It might not be intentional on *your* part, but someone wrote it to do that on purpose, and it's active somewhere in that signal path. Hardware failures are almost never synchronized to the content like that. Not at such a complex-logic level, anyway.

 

[Croma]

Okay, so it's not OBS. Could still be Windoze or a driver trying to insist on being "schmart", and ending up stupid instead. Are you sure you've looked at *everything*? Some things are buried so that the id10t user that Micro$haft seems to insist on doesn't stub their toe on them.


Assuming HDMI, I doubt it. Picture and sound on that use the same wires.

It's based on the old analog TV standard, which had lots of dead time between lines and even more between frames, just to allow the analog circuitry to reset the line scanner and the frame scanner. And a sync pulse during that dead time ensured that the picture stayed in the right place on the screen. That's all still there on HDMI, except that the sync is now a digital code on the same wires that is not a valid color.

Like the captions on analog TV, sound on HDMI is also sent on the same wires during the dead time. So if the picture is good, so is the sound from a hardware perspective, and anything else that uses the same wires.

Even if it were a different format that sends its picture and sound on different wires, I have a hard time thinking of what else would cause that behavior. A new sound that starts perfect and then fades, then resets to perfect again when it stops and restarts, is almost certainly an intentional noise suppressor *somewhere*. It might not be intentional on *your* part, but someone wrote it to do that on purpose, and it's active somewhere in that signal path. Hardware failures are almost never synchronized to the content like that. Not at such a complex-logic level, anyway.

I don't know what to check or watch anymore on the net.
Everything I look at doesn't solve my problem D:
I can not understand..