OBS Stops Decoding Video - Writes Corrupted File

[Channel-14]

Last Sunday (6/30/24) our church service video stopped recording video and showed the screenshot below from about 31 minutes until the end of video, at about 57 minutes. The previous week (6/23/24) the same thing happened, but that time at 16 minutes, lasting until the end of the video at about 44 minutes. The log files show a LOT of this:

08:47:14.124: warning: Found EOI before any SOF, ignoring
08:47:14.124: fatal: No JPEG data found in image
08:47:14.124: Video Capture Device: Error decoding video

The above errors continue from as soon as OBS is started until it is again shut down. The camera continues to provide a good image on the connected monitors, but freezes the video with the screenshot shown below in OBS. I've attached the log file from 6/30, and I have others available back to 6/9/24. They all contain multitudes of the above error warning message.

Screenshot:

Dropbox Replay

Dropbox Replay allows creative teams to better create, collaborate on and deliver content.

replay.dropbox.com

Log File:

Dropbox

www.dropbox.com

 

[Lawrence_SoCal]

For security reasons, please attach the log file directly to your post per the pinned post in this forum
Dropbox wanted a log in, wouldn't simply display/download text file, etc...

That looks like a corrupted video signal.

The camera continues to provide a good image on the connected monitors, but freezes the video with the screenshot shown below in OBS.

Am I correct that local recording and/or livestreaming are both 'worthless' at that point?
The local monitors tell you camera optics are working, etc. but that really isn't that important in your scenario, it is the transmission of that video to your OBS Studio computer that is important. How is that transmitted? hopefully not wirelessly, because if it is, first troubleshooting is to test hard-wired.
How many cameras and how connected?

My standard suggestion (based on scientific method) is minimize variables, so make sure sources are working at Operating System level before OBS Studio gets involved (not even started/running)
- maybe PC overloaded on video feeds? or a driver update impacting things? or something new (extra) running in the background?
- there are lots of possibilities (most having nothing to do with OBS Studio) but need more info to advise

 

[Channel-14]

Sorry for the links, but when I tried to attach the log files the server said they were too big (log file = 12K). I couldn't upload and link the log file from OBS because OBS was started several times after the recording incidents. While trouble shooting I created too many logs, and the software would only upload the current log.

We aren't streaming anything, only recording a video file for later cable broadcast; there are two monitors connected, one on the video controller and one in a remote room for live viewing. We have one PTZ camera connected. All connections are hard-wired, IP devices, no WiFi. I have 10 logs dating back to 6/9/24, all of which show the error message I quoted above occurring about 50 times per second. The frozen screen is not animated, it just freezes a frame and holds it for the duration of the remaining video (see example below). Audio is not affected.

While trouble shooting the system I did install the latest MS "quality update" - the monthly MS update. I also noticed a video driver was available as an optional update and I installed that as well. After updates the same error message kept appearing in the log files with about the same frequency. I also noticed the computer was being left on 24/7, when it's only used for an hour on Sunday to record the church service. While the computer is running the camera is hot the whole time, even though OBS is not running. Being "old school" I shut the computer down on the theory that powering up that camera 24/7/365 isn't going to extend its service life. It makes more sense to me to run it for the hour it's needed, then shut it down for the rest of the week.

I had to compress and upload the log file and reduce the size of the video screen cap in order to get it to go. If they are not usable in this format let me know and I'll take all the repetitive errors out of the log file and see if that helps.

Personally, I'm leaning toward a bad cable or plug connection from the video controller to the computer. Unfortunately, someone thought it would look nicer to build everything into the wall, making it really hard to crawl around under and behind counter tops!

Thanks for whatever light you can shed on this issue - your help is appreciated!

 

[koala]

Your logfile isn't 12k, it's 12 MB, full of the 3 lines you quoted in your OP. This is a sign of a defective data stream from a USB capture device.

A hardware issue. Check USB cabling and USB port, make sure it's plugged in a USB port with high enough USB speed. If it worked fine before, find out what has been changed, for example a USB cable might have been exchanged with some unsuitable cable, or someone might have plugged the existing cable into a different slot that doesn't have the proper speed. Or some of the cabling simply became defective.

 

[Channel-14]

Your logfile isn't 12k, it's 12 MB, full of the 3 lines you quoted in your OP. This is a sign of a defective data stream from a USB capture device.

A hardware issue. Check USB cabling and USB port, make sure it's plugged in a USB port with high enough USB speed. If it worked fine before, find out what has been changed, for example a USB cable might have been exchanged with some unsuitable cable, or someone might have plugged the existing cable into a different slot that doesn't have the proper speed. Or some of the cabling simply became defective.

Yeah, I caught the "k" error after I hit the send button. I didn't see any option to edit the post.

I did some additional troubleshooting this afternoon. When I turned on the computer the camera had no picture at all.

Seems like these things only happen on holiday weekends!

Here's two links to today's efforts, uploaded to the OBS server:

https://obsproject.com/logs/VCmCxOrjAjPhUpiq

https://obsproject.com/logs/JBZONFUmqwqigKsR

 

[Lawrence_SoCal]

While the computer is running the camera is hot the whole time, even though OBS is not running. Being "old school" I shut the computer down on the theory that powering up that camera 24/7/365 isn't going to extend its service life. It makes more sense to me to run it for the hour it's needed, then shut it down for the rest of the week.

I'm also old school. Back in the day, I read some fairly thorough research on motherboard impact from power cycling (powering off/on) vs being left on. *IF* really clean power being provided (ie a quality Pure Sine wave AVR UPS), my recollection was that staying on was better for PC motherboard longevity.... with a HUGE dose of ymmv / it depends (ie plenty that can reverse that recommendation).

However, when it comes to the camera, yea, putting into standby make more sense to me as well. as it is more than background standby level power go on
And the PC analysis was focused more on typical daily PC usage (ie leaving on overnight, vs powering off).
so for a dedicated once per week livestream computer, I turn off ours as well. And I've never known a consumer focused Operating System that handles long uptimes all that well anyway (so at a minimum regular (daily) logging User off, and a somewhat regular full OS reboot, with my personal approach being a full OS reboot most every day.

 

[Lawrence_SoCal]

Also, beware your USB connected cameras audio sampling rate differs from default audio sampling rate... usually not advisable
if not using the USB connected PTZ cameras audio, then I recommend disabling at source, or within Operating System, and only within OBS Studio as a last resort

And, unless you have goo dreason, I'd avoid the re-scaling video quality impact
13:28:57.763: video settings reset:
13:28:57.763: base resolution: 1920x1080
13:28:57.763: output resolution: 1280x720
and instead have base and output resolution be the same 1080p

koala knows WAY more than I do, so trust his suggestions

With that said, I'd be curious if you checked the PTZ camera settings, possibly doing a full reset... just to make sure this isn't a case of the USB cable and port being fine, and it is the data itself being something either the Operating System and/or OBS Studio isn't expecting or can't process

I'd be inclined to test each USB connected PTZ camera individually with a different, known good computer and confirm video output working at Operating System level (OBS Studio need not even be installed).

Are using the USB output on the camera? or something else into a USB adapter 'card'? And with video controller, is this camera IP connected? if yes, why use USB at all?

 

[Channel-14]

Just to follow up, and thank all of you for your assistance, I did get the system up and running again. The camera was fine, and all the other equipment functioned properly. I think our biggest issue was "cable snarl." I've attached a photo to demonstrate the worst of the cable issues. I don't think splitters and hubs take to kindly to heat, and when I see them duct-taped to the top of the cabinet I get the feeling something ain't lookin' right here! You don't even want to see what it looked like under the desk (old cable tangled with new cabling, etc.).

Right now I'm looking for a vendor that sells some sort of wall mount bracket so that I can stabilize the cabling, hubs and splitters and keep them off the floor.

Thanks again for the assistance.

 

[Lawrence_SoCal]

While looking for cable mgmt solutions (there are lots), another possibility (depending on your location) is 3D printing mounting brackets, etc. Our local public library allows for limited free 3D printing... (students at college/university often have free access to even better printers (larger item/longer print time options)... so only issue is time delay vs overnight delivery

Beware interference between power cords and data (and audio) cables... and a true quality USB cable from PTZ camera to computer would be a good idea. And presuming that is highest bandwidth device, and rest of USB 'hub' is low-bandwidth (or non-timing critical like USB flash drive for data transfer), I'd be inclined to plug PTZ camera direct into OBS Studio PC into appropriate port (model dependent), skipping the hub altogether. And if that USB hub ran overheated for an extended period of time... it may be permanently unreliable
Personally, I'd question the use of a USB hub when you have a Desktop PC to begin with... for mouse and similar, I'd be inclined, if extra ports truly required, to use a USB Keyboard with extra USB ports on the keyboard (works great for mouse)... paying attention to USB2 vs 3.x ports and devices

As for XLR audio cables, Ethernet, and others, and presuming drywall on that stub wall (ie, ok for holes, and easily repaired (patched/painted) if/when future re-arrangement takes place... simple screw mount wall zip tie work great. If there are power lines in the wall, if you can determine location, best to avoid running audio/data in parallel (ie along wall mount, or on floor/cable mgmt) with electrical cables for more than a couple of inches, if at all.

The challenge is testing any of the power and all other cables to see if any of them going 'bad'... (including may appear to work fine, but susceptible to or causing interference with neighboring cables)

 

[skepler]

OBS' lossless profile is utvideo video encoder with raw pcm audio.

Thanks for helping, had the same issue.