Random click/pop at one point in game capture recording

chawke

New Member
On the last 2 game captures I did with Elgato 4K S to OBS Studio, there was a random blip in the in-game audio track: a loud click/pop followed immediately by a split second of silence ending with another click/pop. I attached a screenshot of the waveform at that point. However, it doesn't seem to yield any errors where it happened. For example, in the most recent capture, it happened about 4 minutes 25 seconds into the 1h+ recording, but as you can see in the attached log there's nothing at that point. The video itself was unaffected at that point, and it didn't occur on the TV while playing, only in the captured file. I'm guessing it's likelier a capture card or connector issue, but would like to cover all bases so am asking here too. Thanks for any troubleshooting recommendations.
 

Attachments

  • Screenshot 2026-10-21 at 19.25.45.png
    Screenshot 2026-10-21 at 19.25.45.png
    1.7 KB · Views: 30
  • 2026-10-21 11-17-17.txt
    2026-10-21 11-17-17.txt
    18.7 KB · Views: 34
The split-second pop+silence is still happening, and has happened with every capture since this issue started. The weird thing is the noise only occurs once per capture session (which typically ranges between about 30 to 90 minutes) and it happens at a different timestamp in each session.

I use the console HDMI cable between the console and card, and have tried 2 different HDMI cables (the one that came with the card, and a third-party one) between the card and 2 different TVs, and it's happened on all of those.

AI suggested I test on Elgato Studio. Before that I might try swapping the console HDMI cable with the HDMI cable I used with another console since the one capture I did with that other console and its HDMI cable didn't yield this issue. Thanks for any other troubleshooting suggestions related to OBS in the meantime.
 
I swapped the console HDMI cord with another HDMI cord and the issue didn't occur on this session without other setup changes, so I'm betting it's an issue related to said console HDMI cord. May report back if anything changes.
 
Back
Top