Recording becomes a mess after 56 minutes

[Key19]

Howdy!

Log File: https://obsproject.com/logs/gSaQcRvK8GTUmXF6

Log Analysis: https://obsproject.com/tools/analyzer?log_url=https://obsproject.com/logs/gSaQcRvK8GTUmXF6

I recognize that there is a big glaring red "Critical" issue in the Log Analysis. However, my question is this: why did the recording work great for the first 56 minutes but then went to crap suddenly at 56 minutes? The game didn't change. My PC's demands didn't change (that I'm aware of). I didn't run out of disk space (620 GB free). Also I've recorded in 4K forever and my machine should be able to handle it.

CPU: AMD Ryzen 7 9800X3D
MB: MSI PRO B850-VC WIFI (MS-7E56)
RAM: 64GB (Team Group DDR5 SDRAM 32GB x2, UD5-6000)
GPU: NVIDIA GeForce RTX 5080

I don't feel like my PC is lacking for being able to record 4K while also playing in 4K, especially since it did the job fine for the first 56 minutes of the recording.

I have already adjusted OBS to run as administrator always in the future. Any other thoughts or suggestions?

Thank you very much for any assistance!

 

[ShelLuser]

I don't have a solution (yet?), but do want to make something more clear (if not for me then the others).

I didn't run out of disk space (620 GB free).

All on your C drive, or do you happen to use multiple drives? Because if you're using multiple drives, then C is what matters because Windows will denote this as the system drive (and this is also where your swap gets dumped by default).

First: I'm not a fan of using OBS as administrator because in my opinion (for whatever that's worth) it's fighting symptoms. It shouldn't matter all that much. Can imagine that there might be specific issues where the software requires more direct access to drivers and/or hardware, but I don't see that here.

However, my question is this: why did the recording work great for the first 56 minutes but then went to crap suddenly at 56 minutes? The game didn't change. My PC's demands didn't change (that I'm aware of). I didn't run out of disk space (620 GB free). Also I've recorded in 4K forever and my machine should be able to handle it.

Second... there's obviously something going on with the chat/browser. I searched for that peculiar error, and found this. That thread isn't necessarily related (!) but... you say you're recording, but I get the impression you're (also?) streaming, there is a (huge) difference...

I'm a little bit puzzled by this snippet here (I'm also mentioning this for other random readers in hopes that it might give them some ideas as well):

23:53:20.199: [obs-browser: 'Chat Box'] Error: Uncaught (in promise) Error: No available storage method found. (https://streamlabs.com/vite/assets/analytics-Cpc0DHRT.js:12)
23:55:50.820: [game-capture: 'Game'] capture window no longer exists, terminating capture
23:55:50.820: [game-capture: 'Game'] capture stopped
23:56:21.200: [obs-browser: 'Chat Box'] Error: Uncaught (in promise) Error: No available storage method found. (https://streamlabs.com/vite/assets/analytics-Cpc0DHRT.js:12)
23:56:36.896: [Aitum Stream Suite] Saved configuration file
23:56:36.920: A sprite cannot be drawn without a width/height

It almost looks to me as if you were recording, just like you said, yet somehow your session was also streaming and kept streaming. At least it kept on producing those same errors.

Here's my suggestion aka 2 cents... do note: I'm not claiming this to be a solution, but merely trying to rule out possible causes:

• Create a new profile (Profile menu => New...).
  • Don't worry: this way you won't risk losing any settings!
• Enable the setup wizard and let it do its thing. Don't change anything afterward!
• Restart OBS (just to be safe; sometimes this is also required when you change sampling frequencies).

Since your scenes (+ associated sources) are still the same: try another recording. You don't have to make this last 56 minutes (no worries!), just verify if all those browser errors are still a thing.

Of course: you can use the same Profile menu to switch back to your old profile, so that all your previous settings get restored.

Hope this can help a bit.

 

[rockbottom]

You have some Rendering Lag/GPU overload along with encoding lag. Load reduction is in order.

Lots of plugins, they should all be checked & updated if needed. SE says it's for OBS 31.1.1.

Load Reduction:
This monitor is running HDR. It should be 8-bit so disable HDR & run it 120HZ. The on the fly color conversion is wasting resources. 120HZ will correct timing.
22:25:46.617: output 1:
22:25:46.617: name=HISENSE-TV
22:25:46.617: pos={-3840, 0}
22:25:46.617: size={3840, 2160}
22:25:46.617: attached=true
22:25:46.617: refresh=144
22:25:46.617: bits_per_color=10
22:25:46.617: space=RGB_FULL_G2084_NONE_P2020
22:25:46.617: primaries=[r=(0.664062, 0.311523), g=(0.273438, 0.664062), b=(0.152344, 0.052734), wp=(0.313477, 0.329102)]
22:25:46.617: relative_gamut_area=[709=1.256092, P3=0.925955, 2020=0.664311]
22:25:46.617: sdr_white_nits=240
22:25:46.617: nit_range=[min=0.010000, max=500.000000, max_full_frame=400.000000]
22:25:46.617: dpi=96 (100%)
22:25:46.617: id=\\?\DISPLAY#HECA816#5&21f11649&0&UID4352#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}
22:25:46.617: alt_id=\\.\DISPLAY2

Preset P5
22:28:57.388: [obs-nvenc: 'advanced_video_stream'] settings:
22:28:57.388: codec: H264
22:28:57.388: rate_control: CBR
22:28:57.388: bitrate: 7500
22:28:57.388: keyint: 120
22:28:57.388: preset: p7
22:28:57.388: tuning: hq
22:28:57.388: multipass: qres
22:28:57.388: profile: high
22:28:57.388: width: 1920
22:28:57.388: height: 1080
22:28:57.388: b-frames: 2
22:28:57.388: b-ref-mode: 0
22:28:57.388: lookahead: true (28 frames)
22:28:57.388: aq: true

23:57:12.524: Output 'adv_file_output': Number of lagged frames due to rendering lag/stalls: 44 (0.0%)
23:57:12.524: Video stopped, number of skipped frames due to encoding lag: 88601/292037 (30.3%)

Something else:
There may be a driver update, check WireGuard Support. The errors below are generally caused by bad EEE (Energy Efficient Ethernet) settings, updating the driver should eliminate them.
22:28:58.371: [rtmp stream: 'adv_stream'] Connecting to RTMP URL rtmp://ingest.global-contribute.live-video.net/...
22:28:58.391: [rtmp stream: 'adv_stream'] Interface: WireGuard Tunnel (type 0, 100000↓/100000↑ mbps)
22:28:58.391: [rtmp stream: 'adv_stream'] Interface has non-zero error counters (0/12 errors, 0/12 discards)

 

[rockbottom]

Some Scenes have multiple Display, Game or Window Captures. There should only be (1) per Scene to avoid interference.

22:25:54.176: - scene 'Recording':
22:25:54.176: - source: 'YouTube' (window_capture)
22:25:54.176: - source: 'Slippi' (window_capture)
22:25:54.176: - source: 'Rode PodMic (recording)' (wasapi_input_capture)
22:25:54.176: - filter: 'Gain' (gain_filter)
22:25:54.176: - filter: 'Compressor' (compressor_filter)
22:25:54.176: - filter: 'Limiter' (limiter_filter)
22:25:54.176: - source: 'Game Audio' (wasapi_output_capture)
22:25:54.176: - source: 'Game' (game_capture)
22:25:54.176: - filter: 'Source Record' (source_record_filter)
22:25:54.176: - source: 'LiveSplit' (window_capture)
22:25:54.176: - source: 'DroidCam' (droidcam_obs)
22:25:54.176: - filter: 'Chroma Key' (chroma_key_filter_v2)
22:25:54.176: - filter: 'Source Record' (source_record_filter)

 

[ShelLuser]

Some Scenes have multiple Display, Game or Window Captures. There should only be (1) per Scene to avoid interference.

Got a question if you don't mind; this doesn't necessarily apply to OP's issues but I'm simply curious: in your experience, do these potential issues lessen when you apply active control over those potential overlaps? iow: make sure to only keep one or two window captures active at the same time?

Reason I ask, other than curiosity, is because I haven't experienced any issues myself so far (yet?). Still, definitely keeping this in mind.

 

[Key19]

All on your C drive, or do you happen to use multiple drives? Because if you're using multiple drives, then C is what matters because Windows will denote this as the system drive (and this is also where your swap gets dumped by default).

Yes, all on my C drive, I only have one drive.

Second... there's obviously something going on with the chat/browser. I searched for that peculiar error, and found this. That thread isn't necessarily related (!) but... you say you're recording, but I get the impression you're (also?) streaming, there is a (huge) difference...

I can't remember if it was before this particular recording, but I did accidentally click "Start Streaming" when I was trying to select which window to have Game Capture target. I did definitely click "Stop Streaming" after and it should have only been active for about 5 seconds or less. But sometimes OBS is weird when I try to stop streaming, so maybe it just didn't fully stick when I clicked stop? I'm not sure, but I do know that I was certainly not intending to be streaming while recording.

As far as the error you're talking about, are you referring to "02:46:41.111: [obs-browser: 'Chat Box'] Error: Uncaught (in promise) Error: No available storage method found. (https://streamlabs.com/vite/assets/analytics-Cpc0DHRT.js:12)"?

I'm not sure why Chat Box is even doing anything because I was in my Recording scene the entire time and I don't have Chat Box in that scene. I guess maybe OBS runs everything in every scene so that everything is ready in case you switch to another scene? I'm not sure, I'm not a pro by any means.

I'm a little bit puzzled by this snippet here (I'm also mentioning this for other random readers in hopes that it might give them some ideas as well):

It almost looks to me as if you were recording, just like you said, yet somehow your session was also streaming and kept streaming. At least it kept on producing those same errors.

Yeah aside from accidentally clicking "Start Streaming" like I said above, I'm not sure why it would be streaming. Also, I know that I wasn't streaming because I never got a Twitch notification on my phone (whenever I stream I get a push notification to open Stream Manager or whatever it's called). I also don't see a past broadcast on either Twitch or YouTube, so when I was "live", it wasn't long enough to actually do anything. But again, maybe it didn't fully disengage for some reason?

Here's my suggestion aka 2 cents... do note: I'm not claiming this to be a solution, but merely trying to rule out possible causes:

• Create a new profile (Profile menu => New...).
  • Don't worry: this way you won't risk losing any settings!
• Enable the setup wizard and let it do its thing. Don't change anything afterward!
• Restart OBS (just to be safe; sometimes this is also required when you change sampling frequencies).

Since your scenes (+ associated sources) are still the same: try another recording. You don't have to make this last 56 minutes (no worries!), just verify if all those browser errors are still a thing.

Of course: you can use the same Profile menu to switch back to your old profile, so that all your previous settings get restored.

Hope this can help a bit.

I did make three more (short) recordings of the same game after this one. Two of them (6:30 and 6:55) did perfectly well. The other one did the same issue (7 minutes into a 8:30 recording).

One thing I can't help but wonder is if perhaps the game itself was the problem? I had never played it before, and multiple Steam users complain about "horrible optimization" and I wonder if perhaps the game itself is causing the issue. There was one log (I don't have it anymore unfortunately) that referred to a "memory leak" at the end of it. Perhaps the game has a VRAM memory leak that progressively overloads my GPU (despite it being a 5080)?

I think for now I will just see if the issue pops up with any other games/recordings. I really appreciate you taking the time to provide suggestions and try to research/solve my issue. Thank you sincerely and I'll post back if there are any further issues.

 

[Key19]

Got a question if you don't mind; this doesn't necessarily apply to OP's issues but I'm simply curious: in your experience, do these potential issues lessen when you apply active control over those potential overlaps? iow: make sure to only keep one or two window captures active at the same time?

Reason I ask, other than curiosity, is because I haven't experienced any issues myself so far (yet?). Still, definitely keeping this in mind.

This was a question I had as well. While I do have three Window Capture sources in my Recording scene, two of them are disabled (and the third, while enabled, did not have the targeted window open). I wouldn't think that having disabled sources would make a difference (intuitively) but maybe I'm wrong?

 

[rockbottom]

It doesn't matter if they're disabled. Only (1) per Scene.

OP, yes the source can cause stuttering. OBS & your system can be running perfectly fine but if the source doesn't deliver the goods in a timely or consistent manner, stuttering. Games are built on engines & if the engine is flawed, all the games built on that engine are flawed as well. First Person Shooters seem to be the worst.