H264/265/265+ hell

[fullboogie]

I have a 7608-I series with the following cameras:

(1) 2347 G2
(2) 2387G2
(4) 2347 G1
(1) 2455 G1

I tend to tinker with settings, and recently have been getting lots of errors relating to "no substream available" and "not enough resources."

Going through each camera's settings, for both main stream and substream, and writing them down, I found the following problems:

Several cameras had mainstream settings of H264, while others had mainstream settings of H265. Some had H265+.

Several cameras had substream settings of H264, while others had substream settings of H265.

Several cameras had mixed settings for video quality, bitrate, max bitrate, frame rate, etc. No idea why, hard to believe I did that, but it is what it is.

So I took time, based on my notes, to make ALL settings across all cameras consistent - in both main stream and substream - video quality, bitrate, frame rate, 264 vs 265 vs 265+, etc.

After a reboot of the NVR, everything worked great. The only downside is the the NVR somehow lost all info regarding smart events - min box, max box, area, sensitivity, schedule, etc. Had to redo all of that, but it all works now. Apparently the NVR does not like inconsistent settings.

I'd like @JB1970 comments on this. I'm guessing that all the cameras being wonky with different frame rates, different decoding, bitrates, etc., just caused the NVR to say fuck it. I'm out.

 

[JB1970]

I'd like @JB1970 comments on this. I'm guessing that all the cameras being wonky with different frame rates, different decoding, bitrates, etc., just caused the NVR to say fuck it. I'm out.

It really shouldn't matter having different frame rates, bit rates, decoding across multiple cameras. I too mess around with mine (though I've now settled on H264 and CBR for better quality. The storage space doesn't bother me and I'd rather have clear images)

Sometimes you might lose the motion detection area but I've not lost smart detection parameters previously. They're saved in the camera, so as long as the setup is carried out on the NVR local or browser UI all should be good. If however the settings are carried out on the cameras browser UI directly, it'll be necessary to reboot the NVR afterward so that the settings updated directly in the camera are read by the NVR.

 

[fullboogie]

It really shouldn't matter having different frame rates, bit rates, decoding across multiple cameras. I too mess around with mine (though I've now settled on H264 and CBR for better quality. The storage space doesn't bother me and I'd rather have clear images)

Sometimes you might lose the motion detection area but I've not lost smart detection parameters previously. They're saved in the camera, so as long as the setup is carried out on the NVR local or browser UI all should be good. If however the settings are carried out on the cameras browser UI directly, it'll be necessary to reboot the NVR afterward so that the settings updated directly in the camera are read by the NVR.

No idea what I did wrong, JB. My system worked flawlessly for years, but I can't leave well enough alone. Just had to try out a couple of G2's (disaster) and then playing around with settings on all the cameras. When all those errors starting showing up, I just put everything back to where it was. All settings changes were done via web interface with the NVR.

 

[fullboogie]

@JB1970 as a follow up to previous posts about that one G2 that never, ever, ever gives intrusion detections - I just swapped it out with a new, identical G2 and it works perfectly. There was something wrong with that camera, despite multiple firmware upgrades/downgrades, that prevented it from detecting intrusion events. I slammed it into the garbage can and now I'm happy.

 

[JB1970]

@JB1970 as a follow up to previous posts about that one G2 that never, ever, ever gives intrusion detections - I just swapped it out with a new, identical G2 and it works perfectly. There was something wrong with that camera, despite multiple firmware upgrades/downgrades, that prevented it from detecting intrusion events. I slammed it into the garbage can and now I'm happy.

I've never known an issue like that but to be fair I rarely use intrusion detection. I wonder if the recommendation I've seen over on ipcamtalk of a triple factory default before and after firmware update would have resolved it (though it seems ridiculous!)

 

[fullboogie]

New cam still working perfectly. Old cam was crap. The "other" forum has a post about corrupted partitions on the cam that can't be cured, causing problems.

In any case, as always, my posts are meant for posterity for anyone encountering similar problems.