Reolink 811A Shuts Down 4108-HS

[Pogo]

But it works fine in Blue Iris. LOL Talk about back-assward.

So Revo, you're aware of my challenges with Reolink 4K cameras and Blue Iris..., along with just about everyone else who embarks on that particular journey. Not that I'm a big Reolink fan. I just happened upon mine in a couple of local Facebook deals that even you probably wouldn't pass up.

The 811A is a varifocal/5x Optical zoom and a pretty nice camera that I've had for a few years. Never could get it to work very well in Blue Iris until stumbling across a beta firmware distro that was bouncing around the BlueIris forum proclaiming to be the cure for all the difficulty I'd been having with it before I shelved it and put it back up on FB just to get it out of my hair.

Long story short, it was on FB for about 12 weeks with only a dozen or so clicks (probably mine mostly LOL) and the firmware fixed just about everything that was wrong with it which made it worth keeping and then some once I got it dialed in with Blue Iris. I also seem to recall it being quite happy during testing with the 4108 as are my 4K 810As which work great with it but suck with Blue Iris, hence the back-assward part.

Symptom with the 811A through the 4108 is gray or green screen as it seems to be trying to render the stream but then the NVR just gags and freezes or reboots and does the same thing all over again.

Configs match up between the Reolink camera config and the encoding settings in the NVR and they're communicating via ONVIF on port 8999 without issue (though I haven't even tried messing with any PTZ stuff and don't plan on it).

It has the same base hardware as the plain old bullet no bells or whistles 810As which look beautiful through the 4108 but are problematic in Blue Iris.
Neither have an H264 option for the main stream and BI is noted for a fairly poor implementation of its approach to H265 transcoding. Otherwise I'd run both Reolinks at H264 and be done with that. BTW, a T2599 has the same basic H265 issues with Blue Iris as Reolink. Not quite as bad, but not good either. Looks fine with H264.

So anyway, what's your take on the gray and green display with the 811A and the 4108? I don't have any ONVIF triggers or PTZ functionality set up..., at least to my knowledge. I do seem to recall some type of decoding toggle somewhere in the NVR menus but it escapes me at the moment an it's not handy for me to check.

I'm hoping it's something simple so i can add it to the 4108 mix of my 810As and a couple others that work quite well with it. Kinda funny how it's turning out to be my Reolink solution!

[Pogo]

OK. So pretend this is an Amcrest 4K H265 camera that's doing the same thing with a 4108-HS -- wiping out the display with panel block tearing/skewing and a green/gray screen.

What would cause this?

[Pogo]

BTW, Happy Birthday!

[Revo2Maxx]

Thank you for the BD wishes...
I honestly don't know. If I had some idea about what you were asking about I would have replied. I reply to other cameras related to Amcrest devices and I have replied to others that didn't mention Amcrest Device and said they were having issues with different company device. Sometimes tell them best to find another forum that offers support for that device seeing the issue was something I had not heard of. Then for your post, I was like humm don't know maybe someone else on the forum will pass through the Forum with an answer and answer or give some idea of what to check..

I guess I should have asked is the Green/Grey screen thing in the camera on the app or WebUI? or only on the NVR?

About the NVR when you load a camera on lets say Ch3, then you can right click on the GUI, click main menu, then camera, encode, then on the coding strategy there are some options for some cameras I can't say there will be any for your Reolink but that is where one would find them if there was..

I mean I have asked question with no answers as well.. Like why is my 5232E-16P not working with my Amcrest 850EB PTZ camera but does with my POS Annke, my 853, my Samsung 32x, my Alibi 25x PTZ and other PTZ cameras that I have on my system.

Then back to your system that is different from mine in the since my issue was Amcrest Vs Amcrest,, Normally I would just point out that there is as it states on the Amcest website or in the manual or both that there is Minimal support for 3rd party products. That is never an answer anyone wants to hear but is my Cop-Out move..

Could you post a picture of it so I have a better understanding of what is going on? Some times I do better with pictures..

Sorry didn't have an answer for you. Had a lot of things going on in life.

[Pogo]

Thanks for the input.

I ran across the following over on Reddit. In a nutshell, this is basically what was happening; (or more accurately, not happening.) The thread ended with nothing conclusive being determined, and not surprisingly, very little input.

In my particular case, reverting to the previous firmware version for the camera corrected the issue with the NV4108 decoding. It seems ok with Blue Iris but will require daylight to tell the tale with full color motion as I recall this firmware having a latency and time sync issue that was corrected by the version it just replaced that was wreaking havoc with the NV4108.

At this point I think it's fairly safe to conclude that it was/is yet another example of HEVC transcoding compatibility standards still not being quite ready for prime time across the board -- if they ever will..., much like Betamax being shoved down the throat of a VHS world, but even more stubbornly.

jmgao@notos:~$ ffmpeg -hide_banner -nostats -rtsp_transport tcp -i "rtsp://admin:[email protected]:554//h265Preview_01_main" -an -c:v rawvideo -pix_fmt yuv420p -f matroska - 2>&1 >foo.mkv | ts
Sep 06 23:35:32 Input #0, rtsp, from 'rtsp://admin:[email protected]:554//h265Preview_01_main':
Sep 06 23:35:32 Metadata:
Sep 06 23:35:32 title : Session streamed by "preview"
Sep 06 23:35:32 comment : h265Preview_01_main
Sep 06 23:35:32 Duration: N/A, start: 0.000000, bitrate: N/A
Sep 06 23:35:32 Stream #0:0: Video: hevc (Main), yuv420p(tv), 3840x2160, 25 fps, 25 tbr, 90k tbn, 90k tbc
Sep 06 23:35:32 Stream #0:1: Audio: aac (LC), 16000 Hz, mono, fltp
Sep 06 23:35:32 Stream mapping:
Sep 06 23:35:32 Stream #0:0 -> #0:0 (hevc (native) -> rawvideo (native))
Sep 06 23:35:32 Press [q] to stop, [?] for help
Sep 06 23:35:32 Output #0, matroska, to 'pipe:':
Sep 06 23:35:32 Metadata:
Sep 06 23:35:32 title : Session streamed by "preview"
Sep 06 23:35:32 comment : h265Preview_01_main
Sep 06 23:35:32 encoder : Lavf58.29.100
Sep 06 23:35:32 Stream #0:0: Video: rawvideo (I420 / 0x30323449), yuv420p, 3840x2160, q=2-31, 2488320 kb/s, 25 fps, 1k tbn, 25 tbc
Sep 06 23:35:32 Metadata:
Sep 06 23:35:32 encoder : Lavc58.54.100 rawvideo
Sep 06 23:35:54 [hevc @ 0x55e9cb6a4140] The cu_qp_delta 79 is outside the valid range [-26, 25].
Sep 06 23:35:54 [hevc @ 0x55e9cb6e6780] Could not find ref with POC 4
Sep 06 23:35:54 [hevc @ 0x55e9cb6d5d80] Ignoring POC change between slices: 3 -> 4
Sep 06 23:35:58 [hevc @ 0x55e9cb739b00] Could not find ref with POC 2
Sep 06 23:35:58 [hevc @ 0x55e9cb7290c0] Ignoring POC change between slices: 0 -> 2
Sep 06 23:35:58 [hevc @ 0x55e9cb7290c0] Non-matching NAL types of the VCL NALUs: 19 1
Sep 06 23:35:58 [hevc @ 0x55e9cb7290c0] Error parsing NAL unit #7.
Sep 06 23:35:59 Error while decoding stream #0:0: Invalid data found when processing input
Sep 06 23:36:00 [hevc @ 0x55e9cb6e6780] The cu_qp_delta 57 is outside the valid range [-26, 25].
Sep 06 23:36:01 [hevc @ 0x55e9cb6d5d80] The cu_qp_delta -42 is outside the valid range [-26, 25].
Sep 06 23:36:05 [hevc @ 0x55e9cb5f12c0] The cu_qp_delta -31 is outside the valid range [-26, 25].
Sep 06 23:36:09 [hevc @ 0x55e9cb7290c0] The cu_qp_delta 30 is outside the valid range [-26, 25].
Sep 06 23:36:18 [hevc @ 0x55e9cb6b4980] Could not find ref with POC 3
Sep 06 23:36:18 [hevc @ 0x55e9cb6a4140] Ignoring POC change between slices: 1 -> 3
Sep 06 23:36:19 [hevc @ 0x55e9cb739b00] The cu_qp_delta 69 is outside the valid range [-26, 25].
Sep 06 23:36:22 [hevc @ 0x55e9cb718680] Could not find ref with POC 1
Sep 06 23:36:22 [hevc @ 0x55e9cb707b80] Ignoring POC change between slices: 0 -> 1
Sep 06 23:36:22 [hevc @ 0x55e9cb707b80] Non-matching NAL types of the VCL NALUs: 19 2
Sep 06 23:36:22 [hevc @ 0x55e9cb707b80] Error parsing NAL unit #7.
Sep 06 23:36:23 Error while decoding stream #0:0: Invalid data found when processing input
This repeats once every few seconds and every time it happens, there's some sort of garbage in the video (full gray, garbled gray blocks in the updating timestamp, corrupted colors, etc.)