Andreas Kronlachner
Member
Hello!
We implemented SRT setup in listener Mode via Option 2 (advanced settings in recording) as described in your wiki. It worked great but one issue popped up as we ran into a broken socket during our broadcast - see below:
14:03:50.088: error: Operation not supported: Invalid socket ID
14:03:50.088: process_packet: Error writing packet: Unknown error occurred
14:03:50.088: Output 'adv_ffmpeg_output': stopping
14:03:50.088: Output 'adv_ffmpeg_output': Total frames output: 405389
14:03:50.088: Output 'adv_ffmpeg_output': Total drawn frames: 405399 (405401 attempted)
14:03:50.088: Output 'adv_ffmpeg_output': Number of lagged frames due to rendering lag/stalls: 2 (0.0%)
14:03:50.088: ==== Recording Stop ================================================
It is clear, that the recording must stop - however, wenn the recording goes not to file but URL or even srt:// - it would be tremendous, if a mechanism could be implemented, which tries to re-initialize the "recording".
Current behavior is OBS showing a modal dialog with error message which then has to be confirmed manually before - again manually - the recording button needs to be pressed to re-initiate the whole - in fact streaming - not recording.
Problem is, that with this setup, somebody needs to sit in front of the Computer permanently to monitor the SRT "stream" in order to re-start manually, once the socket breaks.
Woiuld that be possible to be implemented? There is some kind of mechanism already for streaming (reconnect mechanism) - so in tihs case it would be a kind of "continue recording after failure" mechanism.
Thanks and regards
Andreas
We implemented SRT setup in listener Mode via Option 2 (advanced settings in recording) as described in your wiki. It worked great but one issue popped up as we ran into a broken socket during our broadcast - see below:
14:03:50.088: error: Operation not supported: Invalid socket ID
14:03:50.088: process_packet: Error writing packet: Unknown error occurred
14:03:50.088: Output 'adv_ffmpeg_output': stopping
14:03:50.088: Output 'adv_ffmpeg_output': Total frames output: 405389
14:03:50.088: Output 'adv_ffmpeg_output': Total drawn frames: 405399 (405401 attempted)
14:03:50.088: Output 'adv_ffmpeg_output': Number of lagged frames due to rendering lag/stalls: 2 (0.0%)
14:03:50.088: ==== Recording Stop ================================================
It is clear, that the recording must stop - however, wenn the recording goes not to file but URL or even srt:// - it would be tremendous, if a mechanism could be implemented, which tries to re-initialize the "recording".
Current behavior is OBS showing a modal dialog with error message which then has to be confirmed manually before - again manually - the recording button needs to be pressed to re-initiate the whole - in fact streaming - not recording.
Problem is, that with this setup, somebody needs to sit in front of the Computer permanently to monitor the SRT "stream" in order to re-start manually, once the socket breaks.
Woiuld that be possible to be implemented? There is some kind of mechanism already for streaming (reconnect mechanism) - so in tihs case it would be a kind of "continue recording after failure" mechanism.
Thanks and regards
Andreas