Closed ccasecams closed 3 years ago
So these are the following issues I've found in your log
This means your using basic authentication but have provided the wrong password to your client app
Completely normal especially at the begining of the stream when we receive data from the camera mid way through a frames packet
This one is interesting it suggests it's not able to get the data from the camera
Completely normal and not related to the buffer per say. This is just to do with how we add timestamps to the streams.
Here's a real error. The data it got from the camera was not the correct format and it was unable to send it to the requested output. This needs to be fixed.
This is related to the preroll error above and suggests that the issue is in the audio source
Perhaps as a first step
Work out why your getting client basic authentication errors
Use the official app to turn off audio on all cameras and see if that helps
Killer breakdown of the issues (And really appreciated!).
I caught the :audsrc: issue, but ignored it at first because audio isn't (and hasn't ever been configured). I am going to try and toggle the audio on/off and see if that clears up the issue.
For the client authentication, I should be able to clear that up pretty quick.
Working on the audio (hopeful) fix now!
Steps taken: Fixed authentication issues Toggled audio on and back off Tried streaming with both streams first (none worked) Tried streaming with just HD (Worked but still saw the audio error messages) Tried streaming with subStream only and still had no luck. Tried changing H264 setting to 'baseline' for fluent with no luck
SD notable logs:
At the start, I see this 2-4 times usually:
0:01:37.181401000 5420 000001FAA141D2C0 WARN rtspmedia rtsp-media.c:3576:wait_preroll: failed to preroll pipeline
0:01:37.182378000 5420 000001FAA141D2C0 WARN rtspmedia rtsp-media.c:3946:gst_rtsp_media_prepare: failed to preroll pipeline
0:01:37.186723000 5420 000001FAA141D2C0 ERROR rtspclient rtsp-client.c:1087:find_media: client 000001FAA19227D0: can't prepare media
0:01:37.188255000 5420 000001FAA141D2C0 ERROR rtspclient rtsp-client.c:3286:handle_describe_request: client 000001FAA19227D0: no media
0:01:37.190097000 5420 000001FAA141D2C0 ERROR rtspclient rtsp-client.c:1046:find_media: client 000001FAA1922910: no factory for path /yardsidefront/mainStream
0:01:37.193836000 5420 000001FAA141D2C0 ERROR rtspclient rtsp-client.c:3286:handle_describe_request: client 000001FAA1922910: no media
0:01:37.195675000 5420 000001FAA141D2C0 ERROR rtspclient rtsp-client.c:1046:find_media: client 000001FAA1B93150: no factory for path /othersidefront/mainStream
0:01:37.199187000 5420 000001FAA141D2C0 ERROR rtspclient rtsp-client.c:3286:handle_describe_request: client 000001FAA1B93150: no media
0:01:37.201168000 5420 000001FAA141D2C0 ERROR rtspclient rtsp-client.c:1046:find_media: client 000001FAA1B93290: no factory for path /yardsideback/mainStream
0:01:37.204413000 5420 000001FAA141D2C0 ERROR rtspclient rtsp-client.c:3286:handle_describe_request: client 000001FAA1B93290: no media
0:01:37.206644000 5420 000001FAA141D2C0 ERROR rtspclient rtsp-client.c:1046:find_media: client 000001FAA1B933D0: no factory for path /backporch/mainStream
0:01:37.210594000 5420 000001FAA141D2C0 ERROR rtspclient rtsp-client.c:3286:handle_describe_request: client 000001FAA1B933D0: no media
0:01:37.230084000 5420 000001FAA141D2C0 ERROR rtspclient rtsp-client.c:1046:find_media: client 000001FAA1CCB270: no factory for path /othersidefront/mainStream
0:01:37.230947000 5420 000001FAA141D2C0 ERROR rtspclient rtsp-client.c:3286:handle_describe_request: client 000001FAA1CCB270: no media
Still seeing this despite Audio being off:
0:00:09.744940000 5420 000001FAA141D2C0 FIXME rtspmedia rtsp-media.c:4549:gst_rtsp_media_suspend: suspend for dynamic pipelines needs fixing
0:00:09.755989000 5420 000001FAA141D2C0 FIXME rtspmedia rtsp-media.c:4549:gst_rtsp_media_suspend: suspend for dynamic pipelines needs fixing
0:00:09.756950000 5420 000001FAA141D2C0 WARN rtspmedia rtsp-media.c:4588:gst_rtsp_media_suspend: media 000001FAA15591D0 was not prepared
0:00:09.789625000 5420 000001FAA16D0280 FIXME default gstutils.c:4026:gst_pad_create_stream_id_internal:<appsrc2:src> Creating random stream-id, consider implementing a deterministic way of creating a stream-id
0:00:09.790509000 5420 000001FAA141D2C0 FIXME rtspmedia rtsp-media.c:2868:gst_rtsp_media_seek_trickmode:<GstRTSPMedia@000001FAA15591D0> Handle going back to 0 for none live not seekable streams.
0:00:09.792953000 5420 000001FAA16CAE80 WARN basesrc gstbasesrc.c:3127:gst_base_src_loop:<audsrc> error: Internal data stream error.
0:00:09.794566000 5420 000001FAA16CAE80 WARN basesrc gstbasesrc.c:3127:gst_base_src_loop:<audsrc> error: streaming stopped, reason not-linked (-1)
0:00:09.796049000 5420 000001FAA141DA40 WARN rtspmedia rtsp-media.c:3250:default_handle_message: 000001FAA15591D0: got error Internal data stream error. (../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstPipeline:media-pipeline/GstBin:bin0/GstAppSrc:audsrc:
streaming stopped, reason not-linked (-1))
0:00:09.796097000 5420 000001FAA16CAE80 WARN queue gstqueue.c:990:gst_queue_handle_sink_event:<queue1> error: Internal data stream error.
0:00:09.803572000 5420 000001FAA16CAE80 WARN queue gstqueue.c:990:gst_queue_handle_sink_event:<queue1> error: streaming stopped, reason not-linked (-1)
0:00:09.807487000 5420 000001FAA141DA40 WARN rtspmedia rtsp-media.c:3250:default_handle_message: 000001FAA15591D0: got error Internal data stream error. (../plugins/elements/gstqueue.c(990): gst_queue_handle_sink_event (): /GstPipeline:media-pipeline/GstBin:bin0/GstQueue:queue1:
streaming stopped, reason not-linked (-1))
I can give a screenshot of the setting on the camera to show the audio off switch (and to make sure I am not missing anything). As far as I know, it would just be under the 'Audio and lighting' tab.
After that, it is a continual slow spam of this sequence:
:05:00.829884000 5420 000001FAA141D2C0 WARN rtspmedia rtsp-media.c:3576:wait_preroll: failed to preroll pipeline
0:05:00.830771000 5420 000001FAA141D2C0 WARN rtspmedia rtsp-media.c:3946:gst_rtsp_media_prepare: failed to preroll pipeline
0:05:00.833841000 5420 000001FAA141D2C0 ERROR rtspclient rtsp-client.c:1087:find_media: client 000001FAA1AF2940: can't prepare media
0:05:00.834874000 5420 000001FAA141D2C0 ERROR rtspclient rtsp-client.c:3286:handle_describe_request: client 000001FAA1AF2940: no media
0:05:00.838558000 5420 000001FAA1925000 FIXME default gstutils.c:4026:gst_pad_create_stream_id_internal:<audsrc:src> Creating random stream-id, consider implementing a deterministic way of creating a stream-id
0:05:00.838736000 5420 000001FAA19250C0 FIXME default gstutils.c:4026:gst_pad_create_stream_id_internal:<vidsrc:src> Creating random stream-id, consider implementing a deterministic way of creating a stream-id
0:05:01.088013000 5420 000001FAA192B300 WARN appsrc gstappsrc.c:1914:gst_app_src_push_internal:<audsrc> do-timestamp=TRUE but buffers are provided before reaching the PLAYING state and having a clock. Timestamps will not be accurate!
0:05:01.088940000 5420 000001FAA192B300 WARN appsrc gstappsrc.c:1914:gst_app_src_push_internal:<vidsrc> do-timestamp=TRUE but buffers are provided before reaching the PLAYING state and having a clock. Timestamps will not be accurate!
0:05:01.102370000 5420 000001FAA1925080 WARN h264parse gsth264parse.c:1492:gst_h264_parse_handle_frame:<h264parse14> broken/invalid nal Type: 1 Slice, Size: 544 will be dropped
0:05:01.103162000 5420 000001FAA1925080 WARN h264parse gsth264parse.c:1492:gst_h264_parse_handle_frame:<h264parse14> broken/invalid nal Type: 1 Slice, Size: 519 will be dropped
0:05:01.296769000 5420 000001FAA1925080 WARN h264parse gsth264parse.c:1492:gst_h264_parse_handle_frame:<h264parse14> broken/invalid nal Type: 1 Slice, Size: 632 will be dropped
0:05:01.298023000 5420 000001FAA1925080 WARN h264parse gsth264parse.c:1492:gst_h264_parse_handle_frame:<h264parse14> broken/invalid nal Type: 1 Slice, Size: 441 will be dropped
0:05:01.503283000 5420 000001FAA1925080 WARN h264parse gsth264parse.c:1492:gst_h264_parse_handle_frame:<h264parse14> broken/invalid nal Type: 1 Slice, Size: 594 will be dropped
0:05:01.504565000 5420 000001FAA1925080 WARN h264parse gsth264parse.c:1492:gst_h264_parse_handle_frame:<h264parse14> broken/invalid nal Type: 1 Slice, Size: 679 will be dropped
0:05:01.728729000 5420 000001FAA1925080 WARN h264parse gsth264parse.c:1492:gst_h264_parse_handle_frame:<h264parse14> broken/invalid nal Type: 1 Slice, Size: 486 will be dropped
0:05:01.729996000 5420 000001FAA1925080 WARN h264parse gsth264parse.c:1492:gst_h264_parse_handle_frame:<h264parse14> broken/invalid nal Type: 1 Slice, Size: 533 will be dropped
0:05:01.882707000 5420 000001FAA1925080 WARN h264parse gsth264parse.c:1492:gst_h264_parse_handle_frame:<h264parse14> broken/invalid nal Type: 1 Slice, Size: 468 will be dropped
0:05:01.883611000 5420 000001FAA1925080 WARN h264parse gsth264parse.c:1492:gst_h264_parse_handle_frame:<h264parse14> broken/invalid nal Type: 1 Slice, Size: 799 will be dropped
0:05:02.066894000 5420 000001FAA1925080 WARN h264parse gsth264parse.c:1492:gst_h264_parse_handle_frame:<h264parse14> broken/invalid nal Type: 1 Slice, Size: 664 will be dropped
0:05:02.067829000 5420 000001FAA1925080 WARN h264parse gsth264parse.c:1492:gst_h264_parse_handle_frame:<h264parse14> broken/invalid nal Type: 1 Slice, Size: 711 will be dropped
0:05:02.295482000 5420 000001FAA1925080 WARN h264parse gsth264parse.c:1492:gst_h264_parse_handle_frame:<h264parse14> broken/invalid nal Type: 1 Slice, Size: 595 will be dropped
0:05:02.296296000 5420 000001FAA1925080 WARN h264parse gsth264parse.c:1492:gst_h264_parse_handle_frame:<h264parse14> broken/invalid nal Type: 1 Slice, Size: 603 will be dropped
0:05:02.474606000 5420 000001FAA1925080 WARN h264parse gsth264parse.c:1492:gst_h264_parse_handle_frame:<h264parse14> broken/invalid nal Type: 1 Slice, Size: 785 will be dropped
0:05:02.475828000 5420 000001FAA1925080 WARN h264parse gsth264parse.c:1492:gst_h264_parse_handle_frame:<h264parse14> broken/invalid nal Type: 1 Slice, Size: 632 will be dropped
0:05:02.721009000 5420 000001FAA1925080 WARN h264parse gsth264parse.c:1492:gst_h264_parse_handle_frame:<h264parse14> broken/invalid nal Type: 1 Slice, Size: 586 will be dropped
0:05:02.722025000 5420 000001FAA1925080 WARN h264parse gsth264parse.c:1492:gst_h264_parse_handle_frame:<h264parse14> broken/invalid nal Type: 1 Slice, Size: 557 will be dropped
0:05:02.894019000 5420 000001FAA1925080 WARN h264parse gsth264parse.c:1492:gst_h264_parse_handle_frame:<h264parse14> broken/invalid nal Type: 1 Slice, Size: 558 will be dropped
0:05:02.894978000 5420 000001FAA1925080 WARN h264parse gsth264parse.c:1492:gst_h264_parse_handle_frame:<h264parse14> broken/invalid nal Type: 1 Slice, Size: 781 will be dropped
0:05:03.056743000 5420 000001FAA1925080 WARN h264parse gsth264parse.c:1492:gst_h264_parse_handle_frame:<h264parse14> broken/invalid nal Type: 1 Slice, Size: 659 will be dropped
0:05:03.057646000 5420 000001FAA1925080 WARN h264parse gsth264parse.c:1492:gst_h264_parse_handle_frame:<h264parse14> broken/invalid nal Type: 1 Slice, Size: 623 will be dropped
0:05:03.284379000 5420 000001FAA1925080 WARN h264parse gsth264parse.c:1492:gst_h264_parse_handle_frame:<h264parse14> broken/invalid nal Type: 1 Slice, Size: 718 will be dropped
0:05:03.458174000 5420 000001FAA1925080 WARN h264parse gsth264parse.c:1492:gst_h264_parse_handle_frame:<h264parse14> broken/invalid nal Type: 1 Slice, Size: 600 will be dropped
0:05:03.458990000 5420 000001FAA1925080 WARN h264parse gsth264parse.c:1492:gst_h264_parse_handle_frame:<h264parse14> broken/invalid nal Type: 1 Slice, Size: 786 will be dropped
0:05:03.662518000 5420 000001FAA1925080 WARN h264parse gsth264parse.c:1492:gst_h264_parse_handle_frame:<h264parse14> broken/invalid nal Type: 1 Slice, Size: 753 will be dropped
0:05:03.663590000 5420 000001FAA1925080 WARN h264parse gsth264parse.c:1492:gst_h264_parse_handle_frame:<h264parse14> broken/invalid nal Type: 1 Slice, Size: 611 will be dropped
0:05:03.867501000 5420 000001FAA1925080 WARN h264parse gsth264parse.c:1492:gst_h264_parse_handle_frame:<h264parse14> broken/invalid nal Type: 1 Slice, Size: 536 will be dropped
0:05:03.868677000 5420 000001FAA1925080 WARN h264parse gsth264parse.c:1492:gst_h264_parse_handle_frame:<h264parse14> broken/invalid nal Type: 1 Slice, Size: 570 will be dropped
0:05:04.055229000 5420 000001FAA1925080 WARN h264parse gsth264parse.c:1492:gst_h264_parse_handle_frame:<h264parse14> broken/invalid nal Type: 1 Slice, Size: 901 will be dropped
0:05:04.056109000 5420 000001FAA1925080 WARN h264parse gsth264parse.c:1492:gst_h264_parse_handle_frame:<h264parse14> broken/invalid nal Type: 1 Slice, Size: 570 will be dropped
0:05:04.057928000 5420 000001FAA1925080 WARN h264parse gsth264parse.c:1492:gst_h264_parse_handle_frame:<h264parse14> broken/invalid nal Type: 1 Slice, Size: 665 will be dropped
0:05:04.324239000 5420 000001FAA1925080 WARN h264parse gsth264parse.c:1492:gst_h264_parse_handle_frame:<h264parse14> broken/invalid nal Type: 1 Slice, Size: 556 will be dropped
0:05:04.325093000 5420 000001FAA1925080 WARN h264parse gsth264parse.c:1492:gst_h264_parse_handle_frame:<h264parse14> broken/invalid nal Type: 1 Slice, Size: 649 will be dropped
0:05:04.326727000 5420 000001FAA1925080 WARN h264parse gsth264parse.c:1492:gst_h264_parse_handle_frame:<h264parse14> broken/invalid nal Type: 1 Slice, Size: 696 will be dropped
0:05:20.838045000 5420 000001FAA141D2C0 WARN rtspmedia rtsp-media.c:3576:wait_preroll: failed to preroll pipeline
0:05:22.420818000 5420 000001FAA141D2C0 WARN rtspmedia rtsp-media.c:3946:gst_rtsp_media_prepare: failed to preroll pipeline
0:05:22.424065000 5420 000001FAA141D2C0 ERROR rtspclient rtsp-client.c:1087:find_media: client 000001FAA198C140: can't prepare media
0:05:22.425025000 5420 000001FAA141D2C0 ERROR rtspclient rtsp-client.c:3286:handle_describe_request: client 000001FAA198C140: no media
0:05:22.428490000 5420 000001FAA1925000 FIXME default gstutils.c:4026:gst_pad_create_stream_id_internal:<audsrc:src> Creating random stream-id, consider implementing a deterministic way of creating a stream-id
0:05:22.428713000 5420 000001FAA19250C0 FIXME default gstutils.c:4026:gst_pad_create_stream_id_internal:<vidsrc:src> Creating random stream-id, consider implementing a deterministic way of creating a stream-id
0:05:22.573086000 5420 000001FAA1920390 WARN appsrc gstappsrc.c:1914:gst_app_src_push_internal:<audsrc> do-timestamp=TRUE but buffers are provided before reaching the PLAYING state and having a clock. Timestamps will not be accurate!
0:05:22.574114000 5420 000001FAA1920390 WARN appsrc gstappsrc.c:1914:gst_app_src_push_internal:<vidsrc> do-timestamp=TRUE but buffers are provided before reaching the PLAYING state and having a clock. Timestamps will not be accurate!
I am not sure if the HD logs would shed any light, but these DO work:
Spammed until every camera connects (but they all eventually connect)
0:02:36.641610000 9052 0000021A463192C0 ERROR rtspclient rtsp-client.c:1046:find_media: client 0000021A4823C180: no factory for path /yardsidefront/subStream
0:02:36.646634000 9052 0000021A463192C0 ERROR rtspclient rtsp-client.c:3286:handle_describe_request: client 0000021A4823C180: no media
0:02:36.651811000 9052 0000021A463192C0 ERROR rtspclient rtsp-client.c:1046:find_media: client 0000021A46382440: no factory for path /yardsideback/subStream
0:02:36.653312000 9052 0000021A463192C0 ERROR rtspclient rtsp-client.c:3286:handle_describe_request: client 0000021A46382440: no media
0:02:36.657512000 9052 0000021A463192C0 ERROR rtspclient rtsp-client.c:1046:find_media: client 0000021A463821C0: no factory for path /backporch/subStream
0:02:36.658673000 9052 0000021A463192C0 ERROR rtspclient rtsp-client.c:3286:handle_describe_request: client 0000021A463821C0: no media
Still see Audio error (despite audio being off):
0:03:28.708977000 9052 0000021A46D7D880 WARN basesrc gstbasesrc.c:3127:gst_base_src_loop:<audsrc> error: streaming stopped, reason not-linked (-1)
0:03:28.722766000 9052 0000021A46420BC0 WARN rtspmedia rtsp-media.c:3250:default_handle_message: 0000021A4647BD80: got error Internal data stream error. (../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstPipeline:media-pipeline/GstBin:bin14/GstAppSrc:audsrc:
streaming stopped, reason not-linked (-1))
Still seeing this until everything is connected
0:04:28.569959000 9052 0000021A463192C0 WARN rtspmedia rtsp-media.c:3576:wait_preroll: failed to preroll pipeline
0:04:28.570806000 9052 0000021A463192C0 WARN rtspmedia rtsp-media.c:3946:gst_rtsp_media_prepare: failed to preroll pipeline
0:04:28.578211000 9052 0000021A463192C0 ERROR rtspclient rtsp-client.c:1087:find_media: client 0000021A4A05F900: can't prepare media
0:04:28.579632000 9052 0000021A463192C0 ERROR rtspclient rtsp-client.c:3286:handle_describe_request: client 0000021A4A05F900: no media
Still see this spammed non-stop even after everything is connected:
0:06:53.323709000 9052 0000021A463192C0 ERROR rtspclient rtsp-client.c:1046:find_media: client 0000021A4A05F2C0: no factory for path /yardsideback/subStream
0:06:53.324417000 9052 0000021A463192C0 ERROR rtspclient rtsp-client.c:3286:handle_describe_request: client 0000021A4A05F2C0: no media
0:06:53.341849000 9052 0000021A463192C0 ERROR rtspclient rtsp-client.c:1046:find_media: client 0000021A4A05FB80: no factory for path /alley/subStream
0:06:53.342973000 9052 0000021A463192C0 ERROR rtspclient rtsp-client.c:3286:handle_describe_request: client 0000021A4A05FB80: no media
0:07:13.243414000 9052 0000021A463192C0 ERROR rtspclient rtsp-client.c:1046:find_media: client 0000021A4823C680: no factory for path /othersidefront/subStream
0:07:13.244732000 9052 0000021A463192C0 ERROR rtspclient rtsp-client.c:3286:handle_describe_request: client 0000021A4823C680: no media
0:07:23.245495000 9052 0000021A463192C0 ERROR rtspclient rtsp-client.c:1046:find_media: client 0000021A4A05FA40: no factory for path /yardsidefront/subStream
0:07:23.246376000 9052 0000021A463192C0 ERROR rtspclient rtsp-client.c:3286:handle_describe_request: client 0000021A4A05FA40: no media
0:07:23.575847000 9052 0000021A463192C0 ERROR rtspclient rtsp-client.c:1046:find_media: client 0000021A4AB5D3D0: no factory for path /backporch/subStream
0:07:23.577390000 9052 0000021A463192C0 ERROR rtspclient rtsp-client.c:3286:handle_describe_request: client 0000021A4AB5D3D0: no media
0:07:23.610719000 9052 0000021A463192C0 ERROR rtspclient rtsp-client.c:1046:find_media: client 0000021A4A05FCC0: no factory for path /yardsideback/subStream
0:07:23.611765000 9052 0000021A463192C0 ERROR rtspclient rtsp-client.c:3286:handle_describe_request: client 0000021A4A05FCC0: no media
0:07:23.613439000 9052 0000021A463192C0 ERROR rtspclient rtsp-client.c:1046:find_media: client 0000021A46D16F50: no factory for path /alley/subStream
0:07:23.614319000 9052 0000021A463192C0 ERROR rtspclient rtsp-client.c:3286:handle_describe_request: client 0000021A46D16F50: no media
Hmm I am not sure audio is actually off because the audio pipeline should almost completely stop.
Also you mentioned video works on HD stream with audio messages? This is also odd because if audio stream fails they both fail as they are in the same pipeline.
Perhaps you could also explain this to me:
SubStream does work when changing BI5 to RTSP
neolink only supplies RTSP no other kind of stream although there are some similarities with HTTP.
Debuging from this point is going to be difficult. Ideally I would
Unfortunately I don't have a D800 to work on this.
Thanks for the help so far! No worries on the lack of a D800!
I figured to simplify things, I would try through VLC (and reduce the amount of settings that could interfere in BI5). Interesting results....
I couldn't connect to my subStream in VLC unless I clarify H264 in my neolink config. Once I forced that in Neolink, all of my subStreams worked (including in BI5).
Is this possibly an issue with how Neolink is detecting the subStream? Here is my config for one of the cameras:
[[cameras]] name = "alley" username = "admin" password = "" address = "10.0.1.100:9000" stream = "subStream" format = "h264"
The issue here (I haven't tested yet though) is that my mainStream uses H265. I assume this would mess with those streams forcing H264. I am testing now to see though.
Ok so I don't think the format = h264
did anything.
format = h264
is completly ignored in the latest neolink the setting literally does nothingformat = h264
the substream was always treated as h264
even when the setting did somethingh246
. Infact broken/invalid nal
is only applicable for h264Ahh 264 is no longer flag! I figured there was some logic already baked in, because I could see the h264 and h265 broken/invalid nal
for the respective streams when I didn't specify sub or main.
I am assuming that the lightweight 'proxy' that is neolink, can handle 6x D800 cameras without an issue, so I am counting that out as a potential issue at this point. Each camera had both streams working simultaneously today (when no other device was connected to the POE switch).
I am feeling like it is possibly my POE switch causing issues. I am going to replace it as a last ditch effort and see what happens. I was seeing some oddities on it with all devices connected (doing a few single port tests today also trying to rule out any bad ports), This is not a managed switch, so vlans aren't possible. I should know Saturday if the switch was the issue.
Thanks again for all the support on this! Sorry for all the troubles so far!
May I ask what these seeing some oddities
means? With hd camera streams the data is so large it is split over many UDP packets and even with a large buffer size it tends to miss some. I recommend you try with tcp and see if the oddities persist.
Sure!
So I have been using TCP the entirety of my tests. Since the pipeline isn't a concern, I wanted the reliability instead.
I changed the ip's so it could easily be dissected without a legend When only one camera is running in Neolink, it looks clean (even with mainStream and subStream going):
22863 38.491367 Cam1 PC S101 78 0.186632000 9000 → 52161 [PSH, ACK] Seq=20239577 Ack=1 Win=4478 Len=24
22864 38.492072 Cam1 PC S101 1514 0.000705000 9000 → 52161 [ACK] Seq=20239601 Ack=1 Win=4478 Len=1460
22865 38.492137 PC Cam1 TCP 54 0.000065000 52161 → 9000 [ACK] Seq=1 Ack=20241061 Win=8212 Len=0
22866 38.492350 Cam1 PC S101 1514 0.000213000 9000 → 52161 [ACK] Seq=20241061 Ack=1 Win=4478 Len=1460
22867 38.492350 Cam1 PC S101 1514 0.000000000 9000 → 52161 [ACK] Seq=20242521 Ack=1 Win=4478 Len=1460
22868 38.492371 PC Cam1 TCP 54 0.000021000 52161 → 9000 [ACK] Seq=1 Ack=20243981 Win=8212 Len=0
22869 38.492558 Cam1 PC S101 1514 0.000187000 9000 → 52161 [ACK] Seq=20243981 Ack=1 Win=4478 Len=1460
22870 38.492558 Cam1 PC S101 1514 0.000000000 9000 → 52161 [ACK] Seq=20245441 Ack=1 Win=4478 Len=1460
22871 38.492576 PC Cam1 TCP 54 0.000018000 52161 → 9000 [ACK] Seq=1 Ack=20246901 Win=8212 Len=0
22872 38.492768 Cam1 PC S101 1514 0.000192000 9000 → 52161 [ACK] Seq=20246901 Ack=1 Win=4478 Len=1460
22873 38.492961 Cam1 PC S101 1514 0.000193000 9000 → 52161 [ACK] Seq=20248361 Ack=1 Win=4478 Len=1460
22874 38.492961 Cam1 PC S101 1514 0.000000000 9000 → 52161 [ACK] Seq=20249821 Ack=1 Win=4478 Len=1460
22875 38.492977 PC Cam1 TCP 54 0.000016000 52161 → 9000 [ACK] Seq=1 Ack=20251281 Win=8212 Len=0
22876 38.493163 Cam1 PC S101 1514 0.000186000 9000 → 52161 [ACK] Seq=20251281 Ack=1 Win=4478 Len=1460
22877 38.493163 Cam1 PC S101 1514 0.000000000 9000 → 52161 [ACK] Seq=20252741 Ack=1 Win=4478 Len=1460
22878 38.493177 PC Cam1 TCP 54 0.000014000 52161 → 9000 [ACK] Seq=1 Ack=20254201 Win=8212 Len=0
22879 38.493363 Cam1 PC S101 1514 0.000186000 9000 → 52161 [ACK] Seq=20254201 Ack=1 Win=4478 Len=1460
22880 38.493374 PC Cam1 TCP 54 0.000011000 52161 → 9000 [ACK] Seq=1 Ack=20255661 Win=8212 Len=0
22881 38.493560 Cam1 PC S101 1514 0.000186000 9000 → 52161 [ACK] Seq=20255661 Ack=1 Win=4478 Len=1460
22882 38.493560 Cam1 PC S101 1514 0.000000000 9000 → 52161 [ACK] Seq=20257121 Ack=1 Win=4478 Len=1460
22883 38.493578 PC Cam1 TCP 54 0.000018000 52161 → 9000 [ACK] Seq=1 Ack=20258581 Win=8212 Len=0
22884 38.493764 Cam1 PC S101 1514 0.000186000 9000 → 52161 [ACK] Seq=20258581 Ack=1 Win=4478 Len=1460
22885 38.493955 Cam1 PC S101 1514 0.000191000 9000 → 52161 [ACK] Seq=20260041 Ack=1 Win=4478 Len=1460
22886 38.493955 Cam1 PC S101 1514 0.000000000 9000 → 52161 [ACK] Seq=20261501 Ack=1 Win=4478 Len=1460
22887 38.493968 PC Cam1 TCP 54 0.000013000 52161 → 9000 [ACK] Seq=1 Ack=20262961 Win=8212 Len=0
22888 38.494155 Cam1 PC S101 1514 0.000187000 9000 → 52161 [ACK] Seq=20262961 Ack=1 Win=4478 Len=1460
22889 38.494155 Cam1 PC S101 194 0.000000000 9000 → 52161 [PSH, ACK] Seq=20264421 Ack=1 Win=4478 Len=140
No retransmissions or fragment overlaps.
When I add more than one camera to Neolink, It gets messy.....:
468486 168.362814 Cam1 PC TCP 1514 0.000213000 9000 → 49837 [ACK] Seq=82270322 Ack=2397 Win=35824 Len=1460[Reassembly error, protocol TCP: New fragment overlaps old data (retransmission?)]
468487 168.362814 Cam2 PC TCP 1514 0.000201000 9000 → 49838 [ACK] Seq=82276122 Ack=2397 Win=35824 Len=1460 [TCP segment of a reassembled PDU]
468488 168.362814 Cam3 PC S101 1514 0.000193000 9000 → 49843 [ACK] Seq=82352188 Ack=2397 Win=35824 Len=1460
468489 168.362814 Cam1 PC TCP 1514 0.000000000 9000 → 49837 [ACK] Seq=82271782 Ack=2397 Win=35824 Len=1460[Reassembly error, protocol TCP: New fragment overlaps old data (retransmission?)]
468490 168.362814 Cam2 PC TCP 1514 0.000000000 9000 → 49838 [ACK] Seq=82277582 Ack=2397 Win=35824 Len=1460 [TCP segment of a reassembled PDU]
468491 168.362814 Cam3 PC S101 1262 0.000000000 9000 → 49843 [PSH, ACK] Seq=82353648 Ack=2397 Win=35824 Len=1208
468492 168.362854 PC Cam3 TCP 54 0.000040000 49843 → 9000 [ACK] Seq=2397 Ack=82354856 Win=2102272 Len=0
468493 168.362864 PC Cam1 TCP 54 0.000050000 49837 → 9000 [ACK] Seq=2397 Ack=82273242 Win=2102272 Len=0
468494 168.362871 PC Cam2 TCP 54 0.000057000 49838 → 9000 [ACK] Seq=2397 Ack=82279042 Win=2102272 Len=0
468495 168.363069 Cam1 PC TCP 1514 0.000205000 9000 → 49837 [ACK] Seq=82273242 Ack=2397 Win=35824 Len=1460[Reassembly error, protocol TCP: New fragment overlaps old data (retransmission?)]
468496 168.363069 Cam2 PC TCP 1514 0.000198000 9000 → 49838 [ACK] Seq=82279042 Ack=2397 Win=35824 Len=1460 [TCP segment of a reassembled PDU]
468497 168.363069 Cam1 PC TCP 1514 0.000000000 9000 → 49837 [ACK] Seq=82274702 Ack=2397 Win=35824 Len=1460[Reassembly error, protocol TCP: New fragment overlaps old data (retransmission?)]
468498 168.363069 Cam2 PC TCP 1514 0.000000000 9000 → 49838 [ACK] Seq=82280502 Ack=2397 Win=35824 Len=1460 [TCP segment of a reassembled PDU]
468499 168.363069 Cam1 PC TCP 1514 0.000000000 9000 → 49837 [ACK] Seq=82276162 Ack=2397 Win=35824 Len=1460[Reassembly error, protocol TCP: New fragment overlaps old data (retransmission?)]
468500 168.363097 PC Cam1 TCP 54 0.000028000 49837 → 9000 [ACK] Seq=2397 Ack=82277622 Win=2102272 Len=0
468501 168.363108 PC Cam2 TCP 54 0.000039000 49838 → 9000 [ACK] Seq=2397 Ack=82281962 Win=2102272 Len=0
468502 168.363300 Cam2 PC TCP 1514 0.000192000 9000 → 49838 [ACK] Seq=82281962 Ack=2397 Win=35824 Len=1460 [TCP segment of a reassembled PDU]
468503 168.363300 Cam1 PC TCP 1514 0.000203000 9000 → 49837 [ACK] Seq=82277622 Ack=2397 Win=35824 Len=1460[Reassembly error, protocol TCP: New fragment overlaps old data (retransmission?)]
468504 168.363300 Cam2 PC TCP 1514 0.000000000 9000 → 49838 [ACK] Seq=82283422 Ack=2397 Win=35824 Len=1460 [TCP segment of a reassembled PDU]
468505 168.363319 PC Cam2 TCP 54 0.000019000 49838 → 9000 [ACK] Seq=2397 Ack=82284882 Win=2102272 Len=0
468506 168.363326 PC Cam1 TCP 54 0.000026000 49837 → 9000 [ACK] Seq=2397 Ack=82279082 Win=2102272 Len=0
468507 168.363516 Cam1 PC TCP 1514 0.000190000 9000 → 49837 [ACK] Seq=82279082 Ack=2397 Win=35824 Len=1460[Reassembly error, protocol TCP: New fragment overlaps old data (retransmission?)]
468508 168.363516 Cam2 PC TCP 1514 0.000197000 9000 → 49838 [ACK] Seq=82284882 Ack=2397 Win=35824 Len=1460 [TCP segment of a reassembled PDU]
468509 168.363516 Cam1 PC TCP 1514 0.000000000 9000 → 49837 [ACK] Seq=82280542 Ack=2397 Win=35824 Len=1460[Reassembly error, protocol TCP: New fragment overlaps old data (retransmission?)]
468510 168.363516 Cam2 PC TCP 1514 0.000000000 9000 → 49838 [ACK] Seq=82286342 Ack=2397 Win=35824 Len=1460 [TCP segment of a reassembled PDU]
468511 168.363539 PC Cam1 TCP 54 0.000023000 49837 → 9000 [ACK] Seq=2397 Ack=82282002 Win=2102272 Len=0
468512 168.363547 PC Cam2 TCP 54 0.000031000 49838 → 9000 [ACK] Seq=2397 Ack=82287802 Win=2102272 Len=0
468513 168.363737 Cam1 PC TCP 1514 0.000198000 9000 → 49837 [ACK] Seq=82282002 Ack=2397 Win=35824 Len=1460[Reassembly error, protocol TCP: New fragment overlaps old data (retransmission?)]
468514 168.363737 Cam2 PC TCP 1514 0.000190000 9000 → 49838 [ACK] Seq=82287802 Ack=2397 Win=35824 Len=1460 [TCP segment of a reassembled PDU]
468515 168.363737 Cam1 PC TCP 1514 0.000000000 9000 → 49837 [ACK] Seq=82283462 Ack=2397 Win=35824 Len=1460[Reassembly error, protocol TCP: New fragment overlaps old data (retransmission?)]
468516 168.363737 Cam2 PC TCP 1514 0.000000000 9000 → 49838 [ACK] Seq=82289262 Ack=2397 Win=35824 Len=1460 [TCP segment of a reassembled PDU]
I know without the full capture, it is hard for you to say the this is the issue, but anything over 1 camera gives the same result. With this being a new, untested/unmanaged POE switch, I am feeling that it might be the issue here.
Ok, just to follow back up. New switch is in, but same issues with the SD streams. I don't see the perceived collision anymore when running HD only, or when connecting one SD stream, but I do see some when all of the SD streams are live.
That gave me an idea...What if I ran multiple instances of Neolink (One per SD camera) and used different ports? Surprisingly, this works (and has been working consistently for multiple reboots, multiple NIC disconnects and reconnects). I am deciding if I want to try the old POE switch before sending it back, just to confirm if that was, or was not a contributing issue.
I can try and help out if any more info is needed and this might just be a D800 specific thing (with the newer FW?). Unsure, but I thought I would close out the convo letting you know that I am up and running, with a mild workaround but I am happy if this wants to be persued as a BUG still. If not, My solution is working very well now.
I have neolink (1hd instance, and 5 SD instances), deepstack, AI Tools, and BI5 GUI setup to all start when the computer reboots and it is running clean! Thanks for all your help again!
Hey hey! If anyone has any suggestions, let me know! (Sorry this is so long! Just trying to provide as much info as possible)
Describe the bug D800 mainStream works fine, I can get all 5 camera's streams running at the same time, at 4k, without an issue. When I try to run both or even subStream only, I either get one camera to connect for a bit, or no cameras will connect over subStream. I have tried a number of different things:
Logs:
I seem to get two different sets of issues when trying substream only:
Issue 1:
Issue 2 (Really rare issue, probably not worth diving in to. Seems like a bandwidth/buffer issue, but on subStream low quality? Is H264 that much more inefficient?):
Log with both HD and SD running:
Versions NVR software: N/A - NVR disconnected at time of test Neolink software: Latest Reolink camera model and firmware: D800, v3.0.0.183_21012801 1G unmanged POE switch (new switch though) I do get sustained 600M from an older laptop cabled to that switch to an external server (so internal should have more bandwidth)