5.2.8 - May 20, 2020 - Direct-to-disc BVR recording will now include metadata for video overlays

Since switching to Substreams my "motion" zone maps don't seem to align.

Night Mode, Motion Zones A, B, C configured with G encompassing all those zones.

Screenshot 2020-05-23 at 12.38.20.png

Yet on playback. My "old" pre-substream Zone is displayed as the area of interest??!

Screenshot 2020-05-23 at 12.38.47.png


Obviously on Playback, its using the "main" stream, at a higher resolution than the sub stream. I wonder if there's some internal confusion going on?
 
Millstone said:
Did you get this fixed?
Click to expand...
It just went away after I restarted BI...but I am now on 5.2.8.3 and it appears to all be working fine. Still no main stream in UI3 . I have noticed you must let it cycle a full set of clips per cam before you can see overlays (if you are running continuous rec clips).
 
  • Like
Reactions: sebastiantombs
hi,

i am not sure if i understand, but if i am playing back alerts or recordings i am seeing the overlays, however i use the macros for displaying info. However when i play back recordings i see the current macro values in the overlays, and not the values as they were on that moment. is there a setting that i am missing? As I expected that the overlays will now be saved in the bvr so also these values?

bart
 
bbakels said:
hi,

i am not sure if i understand, but if i am playing back alerts or recordings i am seeing the overlays, however i use the macros for displaying info. However when i play back recordings i see the current macro values in the overlays, and not the values as they were on that moment. is there a setting that i am missing? As I expected that the overlays will now be saved in the bvr so also these values?

bart
Click to expand...
ive recently noticed the same behavior and emailed Ken. I imagine he'll reply monday.
 
  • Like
Reactions: bbakels
Tinman said:
It just went away after I restarted BI...but I am now on 5.2.8.3 and it appears to all be working fine. Still no main stream in UI3 . I have noticed you must let it cycle a full set of clips per cam before you can see overlays (if you are running continuous rec clips).
Click to expand...
I've updated a couple systems to 5.2.8.3 and seems so far to be behaving. I'll check up on them tomorrow.
 
Millstone said:
I've updated a couple systems to 5.2.8.3 and seems so far to be behaving. I'll check up on them tomorrow.
Click to expand...
I am very happy with 5.2.8.3... it has allowed me to expand to 29 cameras (thanks to substreams), with another 3 to be ordered from Andy soon, since the PC can now cope with them.

Only two improvements I would like: main streams on UI3 (when individual cameras are selected) and several times a day the log file shows "restarted after unexpected shutdown" (BI service shutdown). I have yet to see the shutdown/restart happen and it seems to be a quick process so I guess only a small amount of footage is lost/not detected.
 
Well I am getting a total mess now on some of my cameras. First, the camera's 30 min clips use to be right on every half hour. Now they seem to be all over the place and when clicking a alert the clock was off several hours. This only was happening on certain cameras. I did a full database re-gen and it hosed it completely. I narrowed it down to when one of my cameras did a maintenance reboot. From that point on it appeared BI database got corrupted. I had no choice to delete all clips - database and remove sub streams for now. At this point it all looks good again. This point on I am going to forget using sub streams to see if this was the underlying issue.
 

Attachments

  • Annotation 2020-05-24 153339.jpg
    Annotation 2020-05-24 153339.jpg
    240.8 KB · Views: 25
Tinman said:
Well I am getting a total mess now on some of my cameras. First, the camera's 30 min clips use to be right on every half hour. Now they seem to be all over the place and when clicking a alert the clock was off several hours. This only was happening on certain cameras. I did a full database re-gen and it hosed it completely. I narrowed it down to when one of my cameras did a maintenance reboot. From that point on it appeared BI database got corrupted. I had no choice to delete all clips - database and remove sub streams for now. At this point it all looks good again. This point on I am going to forget using sub streams to see if this was the underlying issue.
Click to expand...
ah, now that you mention it, I did see that twice last night on a single camera (same symptoms you describe.... time-stamp out by 3.5 hours + clip length corrupted) - camera is not set to do any reboot. 1 camera out of 29 is not too bad. I will delete it and re-add it to see if that helps.
 
Well I am getting a total mess now on some of my cameras. First the camera's 30 min clips use to be right on every half hour. Now they seem to be all over the place and when clicking a alert the clock was off several hours. This only was happening on certain cameras. I did a full database regen and it hosed it completely. I narrowed it down to when one of my cameras did a maintenance reboot. From that point on it appeared BI database got corrupted. I had no choice to delete all clips - database and remove sub streams for now. At this point it all looks good again.
b0bthebuilder said:
ah, now that you mention it, I did see that twice last night on a single camera (same symptoms you describe.... time-stamp out by 3.5 hours + clip length corrupted) - camera is not set to do any reboot. 1 camera out of 29 is not too bad. I will delete it and re-add it to see if that helps.
Click to expand...
yes, it’s hard to say what did this . I did see the goofy 46 day thing back on 5.2.7.12, but after going to 5.2.8.2 and then to 5.2.8.3 all looked good till this afternoon. Then the deeper I looked the more corruption I found, once I did the repair/ regen everything was out of sync.
 
  • Like
Reactions: Millstone
b0bthebuilder said:
ah, now that you mention it, I did see that twice last night on a single camera (same symptoms you describe.... time-stamp out by 3.5 hours + clip length corrupted) - camera is not set to do any reboot. 1 camera out of 29 is not too bad. I will delete it and re-add it to see if that helps.
Click to expand...

It may be just coincidence, but deleting the offending camera and re-adding it (i.e. letting BI auto-detect it, not restoring the old settings) resulted in no irregular time-stamp overnight, so maybe a legacy setting on that one camera was causing the time-stamp + clip length corruption
 
  • Like
Reactions: Tinman, kklee and fenderman
b0bthebuilder said:
It may be just coincidence, but deleting the offending camera and re-adding it (i.e. letting BI auto-detect it, not restoring the old settings) resulted in no irregular time-stamp overnight, so maybe a legacy setting on that one camera was causing the time-stamp + clip length corruption
Click to expand...
That's great, but I can't do that for over 100 cameras. We'd lose the footage that correlates to the deleted camera too probably. I hope he finds out what the cause is.
 
Millstone said:
That's great, but I can't do that for over 100 cameras. We'd lose the footage that correlates to the deleted camera too probably. I hope he finds out what the cause is.
Click to expand...

If you keep the name the same and then do a reindex after re-adding wont it bring the old clips back?
 
You must log in or register to reply here.
Top Bottom