No AT&T fiber in our area either.I have them out here all the time cleaning up noise in the neighborhood so I can at least even get my 20 up!
No AT&T fiber in our area either.I have them out here all the time cleaning up noise in the neighborhood so I can at least even get my 20 up!
So I got these errors again this morning on one of the streams. Really need to figure out what's going on with this it says had an error trying to connect to this stream or something. The stream has been going for a couple of days it it's not trying to connect to the stream. The Internet didn't go down period two other streams did not stop. The camera did not stop. I don't understand what is going on. And also I now pay $300 a month for 30MB up, so the internet is not an issue anymore.Just trying to figure out why my streams keep crashing I've included the error messages and the only log file I can find there was not a crash report.
Streams are running on a dedicated windows machine nothing but the three streams are running. I have tailored all bandwidth as much as I could. CPU is running around 30% GPU runs around 60%.
Thanks.
not sure about the color space all that is set to the default setting and auto. The cameras live stream have no color space setting.The only issues shown on the log file are HAGS and that you're using the wrong YUV color space.
And an error I have no idea what it is.Analyzer | OBS
OBS (Open Broadcaster Software) is free and open source software for video recording and live streaming. Stream to Twitch, YouTube and many other providers or record your own videos with high quality H264 / AAC encoding.obsproject.com
Doing a simple search found that the error (os_process_pipe_write for info structure failed) leads to this thread with a probable cause and solution:
Question / Help - Recording error "An unspecified error occurred while recording"
I'm having a problem recording with OBS (streaming works). I get an error message "An unspecified error occurred while recording" and when i check the logs i get [ffmpeg muxer: 'adv_file_output'] os_process_pipe_write for info structure failed. I tried a few solutions but nothing works: - 32...obsproject.com
This looks like a Settings mistake in OBSSo I got these errors again this morning on one of the streams. Really need to figure out what's going on with this it says had an error trying to connect to this stream or something. The stream has been going for a couple of days it it's not trying to connect to the stream. The Internet didn't go down period two other streams did not stop. The camera did not stop. I don't understand what is going on. And also I now pay $300 a month for 30MB up, so the internet is not an issue anymore.
Thank you for the feedback.And you may want to research further on
10:25:31.894: [Media Source 'Feeder']: settings:
10:25:31.894: input: rtsp://root:..snip...@10.0.0.31/axis-media/media.amp?streamprofile=livestream
10:25:31.894: input_format:
10:25:31.894: speed: 100
Speed = 100 - that seems ... odd
though honestly, I don't know exactly what speed that is referring to, but I'd think i might be fps, and should match your camera settings
Another thing to consider is the compression codec used from cameras to OBS PC. HEVC is more highly compressed and therefore takes (a lot?) more computational to compress, and a little more to de-compress/decode. Assuming local LAN bandwidth isn't an issue, using lower compression rates (ex H.264) might help?? maybe.. but also depends on camera codecs and which are better optimized... crap shoot, especially on lower-end security cameras
Moving onto wild guesses (and nothing more). If the cameras are not providing a stable enough feed (jitter/latency, etc) for OBS, maybe (and no idea if this would help at all) maybe some automation to disable and re-enable camera sources at regular intervals (once an hour, for a few seconds)... With Advanced Scene Switcher, I believe you could do that within OBS. I'm sure with scripting you could probably do something at camera level. and no idea if this is an issue at all.
Start with resetting YUV Space to a default setting, and try again.