Recording Randomly Stopping Error number -10054 occurred

roar

New Member
There are two encoders I use every week. They are set up to stream different resolutions to different destinations using the recording tab to Output to URL method.
This has worked seamlessly for weeks but this week both encoders are randomly stopping recording with "an unspecified error occurred while recording obs".
The streaming side stays live the whole time.
When the logs are checked this is what is there:

16:58:40.829: ==== Recording Start ===============================================
17:03:05.038: process_packet: Error writing packet: Error number -10054 occurred
17:03:05.038: Output 'adv_ffmpeg_output': stopping
17:03:05.038: Output 'adv_ffmpeg_output': Total frames output: 6605
17:03:05.038: Output 'adv_ffmpeg_output': Total drawn frames: 6613
17:03:05.039: ==== Recording Stop ================================================

and

17:41:05.296: ==== Recording Start ===============================================
17:51:14.138: process_packet: Error writing packet: Error number -10054 occurred
17:51:14.138: Output 'adv_ffmpeg_output': stopping
17:51:14.138: Output 'adv_ffmpeg_output': Total frames output: 15220
17:51:14.138: Output 'adv_ffmpeg_output': Total drawn frames: 15228
17:51:14.139: ==== Recording Stop ================================================

It could happen after 10 seconds or 10 minutes and it is on both encoders after weeks of working. I am running 26.0.2.
After upgrading to 26.1.1 the black magic card was not being recognised so I had to downgrade again.

Has anyone experienced anything like this before? Thank you for any advice.

Rory
 

roar

New Member
I've ran several tests on one encoder (not sure if the other has the same idiosyncrasy ) and it seems to be after ten minutes it falls over, not exactly to the second. Which is bizarre! Like I said above this has worked for weeks

17:40:26.554: ==== Recording Start ===============================================
17:40:47.259: process_packet: Error writing packet: Error number -10054 occurred
17:40:47.259: Output 'adv_ffmpeg_output': stopping
17:40:47.259: Output 'adv_ffmpeg_output': Total frames output: 517
17:40:47.259: Output 'adv_ffmpeg_output': Total drawn frames: 525
17:40:47.259: ==== Recording Stop ================================================
17:41:05.296: ==== Recording Start ===============================================
17:51:14.138: process_packet: Error writing packet: Error number -10054 occurred
17:51:14.138: Output 'adv_ffmpeg_output': stopping
17:51:14.138: Output 'adv_ffmpeg_output': Total frames output: 15220
17:51:14.138: Output 'adv_ffmpeg_output': Total drawn frames: 15228
17:51:14.139: ==== Recording Stop ================================================
17:51:34.870: ==== Recording Start ===============================================
18:02:04.541: process_packet: Error writing packet: Error number -10054 occurred
18:02:04.541: Output 'adv_ffmpeg_output': stopping
18:02:04.541: Output 'adv_ffmpeg_output': Total frames output: 15741
18:02:04.541: Output 'adv_ffmpeg_output': Total drawn frames: 15749
18:02:04.542: ==== Recording Stop ================================================
18:02:11.814: ==== Recording Start ===============================================
18:12:21.637: process_packet: Error writing packet: Error number -10054 occurred
18:12:21.637: Output 'adv_ffmpeg_output': stopping
18:12:21.637: Output 'adv_ffmpeg_output': Total frames output: 15244
18:12:21.637: Output 'adv_ffmpeg_output': Total drawn frames: 15253
18:12:21.637: ==== Recording Stop ================================================
18:12:25.366: ==== Recording Start ===============================================
18:22:43.163: process_packet: Error writing packet: Error number -10054 occurred
18:22:43.163: Output 'adv_ffmpeg_output': stopping
18:22:43.163: Output 'adv_ffmpeg_output': Total frames output: 15444
18:22:43.163: Output 'adv_ffmpeg_output': Total drawn frames: 15453
18:22:43.164: ==== Recording Stop ================================================
18:22:46.064: ==== Recording Start ===============================================
18:22:48.603: Device 'Remote Audio' invalidated. Retrying
00:32:48.796: process_packet: Error writing packet: Error number -10054 occurred
00:32:48.796: Output 'adv_ffmpeg_output': stopping
00:32:48.796: Output 'adv_ffmpeg_output': Total frames output: 15069
00:32:48.796: Output 'adv_ffmpeg_output': Total drawn frames: 15077
00:32:48.796: ==== Recording Stop ================================================
18:50:42.555: WASAPI: Device 'Remote Audio' [44100 Hz] initialized
18:50:44.101: ==== Recording Start ===============================================
19:00:28.962: process_packet: Error writing packet: Error number -10054 occurred
19:00:28.962: Output 'adv_ffmpeg_output': stopping
19:00:28.962: Output 'adv_ffmpeg_output': Total frames output: 14621
19:00:28.962: Output 'adv_ffmpeg_output': Total drawn frames: 14629
19:00:28.962: ==== Recording Stop ================================================
19:00:32.963: ==== Recording Start ===============================================
19:10:47.157: process_packet: Error writing packet: Error number -10054 occurred
19:10:47.157: Output 'adv_ffmpeg_output': stopping
19:10:47.157: Output 'adv_ffmpeg_output': Total frames output: 15353
19:10:47.157: Output 'adv_ffmpeg_output': Total drawn frames: 15363
19:10:47.158: ==== Recording Stop ================================================
19:10:59.985: ==== Recording Start ===============================================
 

roar

New Member
No I never did, I had to use a second encoder to do the second stream.
It was working correctly for weeks and then on the same day both my encoders had the same issue.

I would be willing to upgrade my version of windows which is very old to see if it helps but I am in the middle of a weekly event and I don't want to risk breaking what is working. I total reset PC could work too but this is risky.

I wish there was an error code list to point in the direction of the problem. I found this but it is from 2016 and doesn't help with my issue. If I use the main streaming output to the same destination it works. So I know the destination is good and I know I have the bandwidth.

Sorry I cannot be more help. Let me know if you find a solution.
 

roar

New Member
Thank you for the reply.

I done a quick test there and the error code is the same but the error message is different "00:44:25.290: Output 'adv_ffmpeg_output': Number of lagged frames due to rendering lag/stalls: 87 (1.9%)"

I can do some proper tests tomorrow.
 

Attachments

  • 2021-04-14 00-40-55.txt
    12 KB · Views: 19

R1CH

Forum Admin
Developer
Your Windows 10 version is very old, it's a good idea to keep it up to date. What output format / URL are you using? 10054 usually means a network connection was terminated by the remote side.
 

roar

New Member
Yes I understand what you are saying but once I moved to a different encoder the connection worked for the three hours I used it for.
If this method never worked I would understand but I streamed more the 24 hours this way and then one day it stopped working on two encoders.

What I then realised once I checked the logs of the successful stream is that that too was failing after 10 minutes but because streams reconnects whereas records do not. So there must be something happening cyclically on the receiving side that wasn't there the precious weeks where is worked correctly.

I should have checked this but as the destination was only for anti-piracy/copyright the client never complained. This might not be the same thing that is happening with chau.guo but I would be interested in seeing is he can see the disconnects and reconnects when using the streaming option rather than the record option in the logs.

Thank you for your help.
 

roar

New Member
There is apparently a new way to do this with a plugin which I didn't know about. I have not tested it but it working for other people.
 
Top