IAmATeaf
Known around here
Switching to the main stream pre buffer would be quite difficult to do wouldn’t it? As BI would also need to be tracking the main stream all the time in case an alert condition is raised?
5.4.4.0 update - new triggered+continuous record setting
- Thread starter 105437
- Start date
Read post #16 in this thread:
The heading also changed from triggered+continuous record mode to triggered+alerts record mode, so now it appears to be going thru DeepStack to get the alert back before changing.
drjjr
n3wb
Thank you. Being new to all of this I just assumed I'd made a mistake somewhere.
Ken always surprises us with magic, so if it can be done, he can do it!, Before this feature, it was always recording mainstream, so there is probably a way - now if it is worth that effort is another story. I am guessing it would have to maybe be recording mainstream on a loop like say 30 seconds maybe, or maybe can figure out a way to do it within the buffer MB in the setting.
I guess if enough people email him and he thinks he can do it, he will!
sebastiantombs
Known around here
I sent him an email about this today. I watched a few clips and very little is actually in full resolution, it drops out after a second or two maybe related to motion detection dropping and starting as movement stops and starts. I've also been getting this error when trying to view a few consecutive clips using UI3, both on the BI machine and on my laptop "live .sem stuck". The dreaded orange clock come up and I have to refresh the page to get out of it.
Hopefully he can make these changes as that would be another big game changer like adding the substreams and DeepStack integration has been. Personally I would be fine even if it saved to mainstream on cancelled alerts if that would be an easier solution for him to implement. We would always have the confirmed alerts tab anyway if we just wanted to see those.
I will play with the option Dave suggested of upping the substream quality and see if that is a decent compromise without adding a lot to CPU usage.
Or we could clone the camera and just not have motion detection on the clone to record 24/7 and then change the main camera to trigger only, although that would be problematic wanting to watch back events as you would need both playback going.
I will play with the option Dave suggested of upping the substream quality and see if that is a decent compromise without adding a lot to CPU usage.
Or we could clone the camera and just not have motion detection on the clone to record 24/7 and then change the main camera to trigger only, although that would be problematic wanting to watch back events as you would need both playback going.
sebastiantombs
Known around here
And that wouldn't save as much disk space, recording the clone at full, albeit reduced, res 24/7 plus the main for alerts. I'm also getting "funky" behavior like a clip that should last 10 or 15 seconds and only plays a few seconds all at low res. I'll have a look at settings for those cameras, but I'm pretty sure they're all the same. What's odd is that it happens on a 5231T-Z most often. At this point I'm thinking about switching back to full time, full res but I'll wait a bit and see what Ken can come up with.
Just updated to the issue just released. Now it is taking longer to go to mainstream LOL.
sebastiantombs
Known around here
Glad I rolled back!
Double check both your main-stream and sub-stream are using the same compression settings i.e both h.264 or h.265. I had the same problem on one of my cams whereby it would trigger and then stop after a few seconds, failing to switch to the main stream. On the wild hunt for a reason, I realised in the camera config I had main-stream set to h.265 but sub-stream on h.264. Worked perfectly since!
sebastiantombs
Known around here
Been there, done that. Still too many switches to sub streams and problems with "live .sem stuck" errors on higher resolution, 4MP, cameras.
The 5.4.5 update now switches to mainstream before the motion occurs!!!
Last edited:
Looking forward to hearing how this works!
Early testing looks really good! The first trigger went to substream immediately after the motion stopped (car out of frame), but now the last 8 vehicles went to mainstream prior to car in frame and stayed mainstream for the post-trigger time.
This will add a lot of additional storage time for most people!
This will add a lot of additional storage time for most people!
sebastiantombs
Known around here
Funny how fast we get used to having all that additional storage available, isn't it
Of course this comes AFTER I got more storageFunny how fast we get used to having all that additional storage available, isn't it
Actually all is good because I had a few cams that I was running trigger only as they were not critical areas, but now, hey why not!
And I will probably switch my cams back to H264 as they look better to me than H265 and can up bitrates now.
sebastiantombs
Known around here
Yeah, I just added an 8TB drive, too. Now I've got to go back and change everything from H265 to H264 and play with bit rates, too. The leading edge takes a lot of time!
Continuous+Alerts will record substream until a confirmed AI alert is indicated and then will record mainstream for the duration of the trigger.
Continous+Triggered will record substream until ANY trigger and then will record mainstream for the duration of the trigger.
The BI help file also indicates this and the other recording settings...