After updating to 31.0.1 OBS freezes after 5-7 hours of broadcasting and recording.

O

orangedeal

New Member
The broadcast and recording cannot be stopped (it takes forever). In OBS browser captured image freezes. Usually OBS loads the CPU by 1-1.5%, but when this problem starts, load reaches 6%. No other settings in the system were changed. I use NVENC.
 

Attachments

  • 2025-01-30 08-37-18.txt
    99.9 KB · Views: 18
R

rockbottom

Active Member
Low hanging fruit, disable it & try again.
08:37:18.688: Hardware-Accelerated GPU Scheduling enabled on adapter!

Not sure if that SFE that's enabled on the AV1 encode is causing trouble or even needed but if it continues to freeze, try disabling it. Looks like it's meant to be used with 4/8k anyway.

09:21:33.605: codec: AV1
09:21:33.605: rate_control: CBR
09:21:33.605: bitrate: 25000
09:21:33.605: keyint: 120
09:21:33.605: preset: p7
09:21:33.605: tuning: hq
09:21:33.605: multipass: fullres
09:21:33.605: profile: main
09:21:33.605: width: 2560
09:21:33.605: height: 1440
09:21:33.605: b-frames: 2
09:21:33.605: b-ref-mode: 0
09:21:33.605: lookahead: false (0 frames)
09:21:33.605: aq: false
09:21:33.605: split encode: 15

developer.nvidia.com

Video Encoding at 8K60 with Split-Frame Encoding and NVIDIA Ada Lovelace Architecture | NVIDIA Technical Blog

Capturing video footage and playing games at 8K resolution with 60 frames per second (FPS) is now possible, thanks to advances in camera and display technologies. Major leading multimedia companies…
developer.nvidia.com developer.nvidia.com

NVIDIA Video Codec SDK v12.2

The NVIDIA Video Codec SDK provides a comprehensive set of APIs, samples, and documentation for fully hardware-accelerated video encoding, decoding, and transcoding on Windows and Linux platforms.
docs.nvidia.com docs.nvidia.com
 
R

rockbottom

Active Member
Having the multi-out going at the same time, probably not a good idea.

Split-frame encoding (SFE) is a breakthrough feature that unlocks video encoding capabilities at 8K60 and beyond. It empowers users to harness the power of multiple NVENCs within NVIDIA Ada Lovelace architecture GPUs for encoding a single video sequence. This post has explained the performance advantages of two-way SFE (using two NVENCs) and three-way SFE (using three NVENCs). The latest NVIDIA Video Codec SDK provides explicit control over SFE for optimal customization.
 
O

orangedeal

New Member
I have only three encoder threads enabled - AV1 for YouTube and local recording + h.264 for Twitch. I'm watching the loading of video encoder in MSI Afterburner and it shows 50-70% loading. After updating to 31.0.1 I immediately set the default settings to default, because OBS told me that the previous settings were deprecated. After the first freeze I disabled this function but after the second freeze I'm thinking what to do.

I hope that the problem is in the outdated version of Multi-RTMP, which was recently updated. There was version 0.6.0.0 and now 0.6.0.1. If this doesn't help then I'll have to disable Hardware-Accelerated GPU Scheduling.
 
R

rockbottom

Active Member
FYI, both AV1 encodes are using SFE.

Your Desktop Audio buffers several times in the log, usually an indication of system overload.

08:53:03.703: Max audio buffering reached!
08:53:03.703: adding 917 milliseconds of audio buffering, total audio buffering is now 960 milliseconds (source: Desktop Audio)
08:53:03.703:
08:53:03.724: Source Desktop Audio audio is lagging (over by 87741.10 ms) at max audio buffering. Restarting source audio.

10:26:44.481: Source Desktop Audio audio is lagging (over by 244998.37 ms) at max audio buffering. Restarting source audio.

10:28:14.806: Source Desktop Audio audio is lagging (over by 64656.18 ms) at max audio buffering. Restarting source audio.

10:38:59.350: Source Desktop Audio audio is lagging (over by 23179.27 ms) at max audio buffering. Restarting source audio.

10:55:15.264: Source Desktop Audio audio is lagging (over by 63597.00 ms) at max audio buffering. Restarting source audio.
 
O

orangedeal

New Member
Could it be because I very often switch the game from windowed mode to full screen and back to windowed mode? And because of this everything freezes for a second. And my OBS works on the second monitor and there everything also freezes for a second. But this didn't cause any problems before.
 
R

rockbottom

Active Member
Hard to say for sure. Update the multi-out, update the other settings already mentioned & test again. HAGS can wreck audio so it may improve or it may not, just something to keep an eye on.
 
R

rockbottom

Active Member
Looking at your audio inputs. Global & Source audio are in play, personally I use one or the other but not both concurrently. That said, your Audio Output Capture in the Scene is using Device Timing just like the Desktop Audio. Disable it for the Audio Output Capture & just use the Desktop Audio for timing purposes. Both are not arriving to OBS at the same exact time.

I never had any issues with 48/96k but sample-rates should match. OBS is @ 48k.

08:37:19.214: [win-wasapi: 'Desktop Audio'] update settings:
08:37:19.214: device id: {0.0.0.00000000}.{93acab59-e723-4f93-893b-dd665aedfd50}
08:37:19.214: use device timing: 1
08:37:19.214: [Loaded global audio device]: 'Desktop Audio'
08:37:19.214: [win-wasapi: 'Smart'] update settings:
08:37:19.214: device id: {0.0.1.00000000}.{90f6fa8a-d91f-4c6b-b7f0-af280c8fd155}
08:37:19.214: use device timing: 0
08:37:19.215: [Loaded global audio device]: 'Smart'
08:37:19.215: [win-wasapi: 'Mic'] update settings:
08:37:19.215: device id: {0.0.1.00000000}.{3c446fc1-7e70-453e-a89a-2ef5abbfb958}
08:37:19.215: use device timing: 0
08:37:19.215: [Loaded global audio device]: 'Mic'

08:37:19.215: [win-wasapi: 'Audio Output Capture'] update settings:
08:37:19.215: device id: {0.0.0.00000000}.{1ff8781d-8c5e-44c5-9a7e-0449d394d55b}
08:37:19.215: use device timing: 1

08:37:19.233: WASAPI: Device 'VoiceMeeter Input (VB-Audio VoiceMeeter VAIO)' [96000 Hz] initialized (source: Desktop Audio)
08:37:19.233: WASAPI: Device 'VoiceMeeter Aux Input (VB-Audio VoiceMeeter AUX VAIO)' [96000 Hz] initialized (source: Audio Output Capture)
08:37:19.240: WASAPI: Device 'VoiceMeeter Aux Output (VB-Audio VoiceMeeter AUX VAIO)' [96000 Hz] initialized (source: Smart)
08:37:19.245: WASAPI: Device 'VoiceMeeter Output (VB-Audio VoiceMeeter VAIO)' [96000 Hz] initialized (source: Mic)
08:37:19.297: adding 42 milliseconds of audio buffering, total audio buffering is now 42 milliseconds (source: Smart)
 
You must log in or register to reply here.
Top