Yep that is what the BI help file says it is and it does perform just like that.
That would be within the camera itself. Most have a substream that is less quality (and thus less storage and bandwidth) than the mainstream.
So when nothing is happening, it is recording the lower quality substream, and then when something happens it switches over to the mainstream higher resolution video.
So the question is do you want 24/7 recording and do you want the substream to mainstream option that saves storage space or just record continuous and be only mainstream.
Or do you record just when triggered or alerts?
Plenty of options to chose based on what you are trying to accomplish.
Most cameras are capable of multiple video streams. Stream 1 is usually at full resolution and high bit rates. The subsequent streams are at lower resolution and lower bit rates. What BI does if sub streams are used is to record continuously from the sub stream, which save significant amounts of disk space, and switch to the main stream for alerts so full detail, resolution, is available.
Using sub streams, in my case, allows for storage of about a month versus a week for full resolution only. It also unload the CPU significantly and will drop utilization very significantly as well, typically dropping by a factor of three to four. So, if your CPU is running at 50% using full resolution continuous recording switching to sub streams, continuous-triggered or continuou-alerts, will drop the CPU utilization to as low as 15% or so.
Triggers will be for everything that triggers the camera and alerts will be the ones confirmed by DeepStack. So if you are not running DeepStack then use triggers.
LOL - usually most issues with BI (or anything LOL) comes down to user error I can make fun of it because I do it to LOL.
We see many people come here saying it isn't working and when they post screenshots we see they were changing things they thought would be good and actually made it worse LOL.
My favorite is the person that comes on here complaining their CPU is running high and claims they have done EVERY optimization, and then when you ask for screenshots, you see they didn't implement the substreams and that is probably the biggest CPU saver their is LOL. "Oh I didn't think that one was important"....the wiki exists for a reason LOL.
Same LOL - sometimes for the better, but usually for the worse LOL.
Right now I am failing miserably at trying to get clean capture of a driver in a car at night LOL. I had the camera set up great for a location and what not and thought "hmm maybe I could use this camera to ID drivers in the middle of the night". So I will probably move the camera back to its original place tomorrow.
Yeah, the different window tints and angles im seeing as they drive in the garage makes them all different. I tried With the “illuminator” on, and got about 50 % ID’ed. But My results are biased because I know all my residents faces, and what car they drive.
Triggers will be for everything that triggers the camera and alerts will be the ones confirmed by DeepStack. So if you are not running DeepStack then use triggers.
Hmmm.... Clear explanation! Will check my system now... Could be the reason why not everything is working like I would like to be seeing it....
And yes... Clicking on things and lateron thinking: maybe a bit of reading was better and saved a lot of time....
Triggers will be for everything that triggers the camera and alerts will be the ones confirmed by DeepStack. So if you are not running DeepStack then use triggers.
You can use ether depending on exactly what you're trying to do. I use continuous+alerts just to make sure nothing gets missed. Continuous+triggered means that BI, and DS if that's in use and the option is selected, must detect motion before it is flagged on the timeline.
You can use ether depending on exactly what you're trying to do. I use continuous+alerts just to make sure nothing gets missed. Continuous+triggered means that BI, and DS if that's in use and the option is selected, must detect motion before it is flagged on the timeline.
I checked out a video. picked up some pointers. The guys audio/microphone wildly ramps up and down quite a bit, but the info is there once you get past it.
I can make fun of it because I do it to LOL.
