The obs-ndi capture suddenly goes from 60fps to 25-30 FPS after 20 minutes of streaming.

[MarlburroW]

Hi everyone,

I use NDI to send my game capture to my streaming PC (x264 encoding to twitch with a dedicated high end CPU).
I've a smooth 60 FPS during 15-20 minutes, and suddenlty my FPS drop to 25-30 FPS.

I made a test stream to show the issue: https://www.twitch.tv/videos/1240885500
And this is moment when the FPS start to fall down: https://www.twitch.tv/marltest/clip/AthleticModernYogurtTheRinger-UD1eA4bGr_H5F90_

All metrics displayed comes from the streaming PC and not from the Gaming PC.

• As you can see in the clip, I show the NDI monitor on top right of the stream, and we see the monitor constantly smooth.This means that the source NDI stream exposed by my gaming PC is OK and is always received by the streaming PC at 60FPS, this is not a network issue.
• This also means this is not an encoding issue, because in this case the monitor view would not be smooth like this.
• This is not a GPU/CPU bottleneck or temperature issue, all hardware metrics seems to be OK during the stream.
• Restart OBS fix the issue (until it starts again after 20-30 minutes)
• When the framerate drop down, this is visible on the preview screen of OBS, which comforts me in the hypothesis that it is not an encoding problem.
• Run OBS as Admin doesn't change anything
• Didn't found anything strange in the logs (logs are displayed in realtime in my test stream).
• Windows 11 is configured in Game Mode and Ultimate Performance

Has anyone ever encountered this issue?

Thanks for your help !

 

[TomCatT]

Mine drops when there's very fast movement in VR. The OBS on the gaming rig FPS doesn't drop but on the receiving computer does drop. Some times it'll recover most of the time I'll have to quit the app.

Not sure what's going on, is there too much data going out that the receiving computer can't process it? I've tested this out on two computers with windows and Linux. All gave me the same results. I'm just not sure where the disconnect is coming from. In the past (years ago) this was never the case.