stopping stream problem (win10 only).

sometimes when stopping streaming/recording, both stream/record buttons will become unusable, and there was no video footage lag behind buffering. but, when I switched the streaming computer back to win10 from win11, the stop-jam issue started happening again.

therefore I would say it's mainly win10 issue, not win11, which was fine for a long time without any stop-jams.

log maybe later. just findings for now. and forced quit/exit (from task manager) of the obs software will leave obs-ffmpeg-remux process live on the background.
 
in the latest OBS version, stopping stream and recording dont stop, but stay in the stopping state.
have to terminate the program manually from task manager after pressing yes I want to exit.
and this issue is on win11 amd rtx, I have not tried win10 streaming since.

log snippet:

18:00:13.784: [obs-nvenc: 'simple_video_stream'] settings:
18:00:13.784: codec: H264
18:00:13.784: rate_control: CBR
18:00:13.784: bitrate: 6000
18:00:13.784: cqp: 20
18:00:13.784: keyint: 120
18:00:13.784: preset: p7
18:00:13.784: tuning: hq
18:00:13.784: multipass: qres
18:00:13.784: profile: high
18:00:13.784: width: 1280
18:00:13.784: height: 720
18:00:13.784: b-frames: 2
18:00:13.784: lookahead: true
18:00:13.784: psycho_aq: true
18:00:13.784:
18:00:13.839: ---------------------------------
18:00:13.840: [FFmpeg aac encoder: 'simple_aac'] bitrate: 160, channels: 2, channel_layout: stereo
18:00:13.840:
18:00:13.840: [rtmp stream: 'simple_stream'] Connecting to RTMP URL rtmp://arn04.contribute.live-video.net/app...
18:00:13.861: [rtmp stream: 'simple_stream'] Interface: Realtek PCIe GbE Family Controller (ethernet, 1000↓/1000↑ mbps)
18:00:14.144: encoder 'simple_video_stream': Cannot apply a new video_t object after the encoder has been initialized
18:00:14.164: [obs-nvenc: 'simple_video_recording'] settings:
18:00:14.164: codec: H264
18:00:14.164: rate_control: CQP
18:00:14.164: bitrate: 0
18:00:14.164: cqp: 21
18:00:14.164: keyint: 250
18:00:14.164: preset: p5
18:00:14.164: tuning: hq
18:00:14.164: multipass: qres
18:00:14.164: profile: high
18:00:14.164: width: 1280
18:00:14.164: height: 720
18:00:14.164: b-frames: 2
18:00:14.164: lookahead: false
18:00:14.164: psycho_aq: true
18:00:14.164:
18:00:14.201: ---------------------------------
18:00:14.201: [FFmpeg aac encoder: 'simple_aac_recording0'] bitrate: 192, channels: 2, channel_layout: stereo
18:00:14.201:
18:00:14.210: ==== Recording Start ===============================================
18:00:14.210: [ffmpeg muxer: 'simple_file_output'] Writing file 'D:/video/twitch/2024-03-29_18-00-14.mkv'...
18:00:15.122: [rtmp stream: 'simple_stream'] Connection to rtmp://arn04.contribute.live-video.net/app (52.223.199.110) successful
18:00:15.122: [rtmp stream: 'simple_stream'] Socket send buffer is 65536 bytes
18:00:15.124: ==== Streaming Start ===============================================
18:12:27.083: ==== Shutting down ==================================================
18:12:27.128: WASAPI: Device '[VIRTUAL_AUDIO_DEVICE_PROCESS_LOOPBACK]' Terminated
18:12:27.129: WASAPI: Device '[VIRTUAL_AUDIO_DEVICE_PROCESS_LOOPBACK]' Terminated
18:12:27.129: WASAPI: Device '[VIRTUAL_AUDIO_DEVICE_PROCESS_LOOPBACK]' Terminated
18:12:27.129: decklink: Stopping capture of 'Intensity Shuttle'...
18:12:27.135: WASAPI: Device '[VIRTUAL_AUDIO_DEVICE_PROCESS_LOOPBACK]' Terminated
18:12:27.135: WASAPI: Device 'Speakers (Realtek(R) Audio)' Terminated
18:12:27.137: WASAPI: Device 'Microphone (Realtek(R) Audio)' Terminated
18:12:27.142: WASAPI: Device '[VIRTUAL_AUDIO_DEVICE_PROCESS_LOOPBACK]' Terminated
18:12:27.142: decklink: Stopping capture of 'Intensity Shuttle'...
 
now there is a new issue, sometimes the intensity shuttle input stops working, because of changed intensity shuttle device.
I dont know if this happens because of blackmagicdesign drivers or OBS. but a secondary problem is that the OBS default
preview window does not always display the same as the full screen projector, when displaying the video/audio from the shuttle.
turning off/on the source will not help. restarting OBS software does help. sometimes the full screen projector shows the correct
video stream and the normal preview window shows only black screen.
 

qhobbes

Active Member
1. The Hardware-accelerated GPU scheduling ("HAGS") feature with Windows is currently known to cause performance and capture issues with OBS, games and overlay tools. It's an experimental feature and we recommend disabling it via these instructions.
2. One of your audio devices has a sample rate that doesn't match the OBS sample. This can result in audio drift over time or sound distortion. Check your audio devices in Windows settings (both Playback and Recording) and ensure the Default Format (under Advanced) is consistent. 48000 Hz is recommended.
OBS Sample Rate: 48000 Hz
Microphone (High Definition Audio Device): 44100 Hz
3. In many cases, wireless connections can cause issues because of their unstable nature. Streaming really requires a stable connection. Often wireless connections are fine, but if you have problems, the first troubleshooting step would be to switch to wired. We highly recommend streaming on wired connections.
4. Run OBS as Admin. To run OBS as Administrator, right click on the OBS shortcut, properties, advanced, check box, ok, apply, ok.

If still having issues after making those changes, post new log.
 
In all cases I should not have to be dealing with any of these issues.

to be more precise:
1. omg windows. this is the only thing I see any relative reasoning to even think about changing by hand. BUT: win11 currently, not win10.
2. sample rate conversions should never be an issue. I dont have an audio drift issue or any, other than audio stops completely sometimes.
3. this issue happens no matter if its wired/wireless lan.its the obs-ffmpeg-mux that stops, maybe add more fault tolerance. wifi is just fine.
4. this is just asking for trouble in general. never should be an advice or requirement. program should change its operation.

Result: I only disable HAGS for GPU in win11.

PS. some compromises are not negotiable even if some program would want to do it their way.
 
Last edited:
for the obs-ffmped-mux, instead of gracefully exiting with error, it just crashes and/or hangs.
in this case it just hangs. not very reliable imho. whatever the issue might be that causes it to hang.

must be known by now. its not random.
 

qhobbes

Active Member
Does this still happen if you use the (Use stream encoder) option for the Recording Video Encoder after starting the stream?
 
I dont remember but I require different output settings for the video file, than for the stream.
I think that happened also with "same as stream" long time ago tho.
 
Top