Our cams seem to use a lot of disk space. Each cam is using about 2GByte per hour so about 50 GBytes/day/cam. With a dozen cams that is about 600 GBytes/day. The cams are set at 8kbps VBR (going to change it to CBR) so that should be 8192 bits/8bits/byte*24h/day*60minutes/hour*60seconds/minute = 88,473,600 bytes/day or 84MBytes/day/cam. Are those cam settings actually 8192 bytes/s instead of 8192 bits/s? That would explain the 50GBytes/day. Also are there good ways to reduce the storage size without compromising much of the image quality? Or are you just using some 8TB+ HDDs to have approx. a week of storage?
Storage Requirement
- Thread starter rfj
- Start date
Are you recording continuous instead of continuous + triggers?
Cont+trig will take a lot less space as it will record substream until triggered and then switch to mainstream.
Cont+trig will take a lot less space as it will record substream until triggered and then switch to mainstream.
looney2ns
IPCT Contributor
Optimizing Blue Iris's CPU Usage
Blue Iris uses a lot of CPU time. In most Blue Iris installations, your CPU is the limiting factor which determines how many cameras you can have. As such, it is extremely important to optimize your configuration to ensure you can get the most out of your system while consuming the least...
looney2ns
IPCT Contributor
Broachoski
Getting comfortable
I have chosen to sacrifice some quality for quantity myself. In order to keep a months worth of recordings to 8TB, running 27 cameras 24/7 I have all cameras set using "continuous + triggered" and run from 5 to 15 fps depending on my personal requirements. This has been a continual "work in progress" and have enjoyed the continual improvements over the years with BlueIris.
I record continuously at full res. Previously I only recorded on triggers but I ended up missing important events (police did come by a couple of times and each time I didn't have the recording they were looking for). So how does this "continuous + triggers" work and may I end up in the same situation where I don't have the necessary video footage?
IAmATeaf
Known around here
It records the substream until triggered when it switches over to the full res stream.
If the cams previously failed to trigger and you did nothing to rectify then you’ll at worst case have a substream recording.
If the cams previously failed to trigger and you did nothing to rectify then you’ll at worst case have a substream recording.
alastairstevenson
Staff member
Does that mean that the 'pre-record' duration of the recorded video uses the substream?
alastairstevenson
Staff member
alastairstevenson
Staff member
Which implies that the mainstream is being buffered, to provide the pre-record duration, but not yet stored until an event trigger.
I just wondered if it was the subtream that was being buffered.
Your frame rate will have a huge impact on the storage space you use. Recording 30 fps takes three times as much hard drive space as 10fps. There are only a few situations where you realistically need more than 10 frames per second being recorded. We aren't trying to make Hollywood movies here (but even they only record 24 fps).
Are most people here recording the substream and then record the main stream when there is a trigger? That seems kind of reasonable. But how do you set this up that way? I didn't see any such setting in BI. As for fps, I am recording at 15fps. Maybe I should lower that to 10fps except for the LPR cam.
Broachoski
Getting comfortable
Chosen for each camera in settings menu and under RECORD tab.
I just realized that I have some set up to record CONTINUOUS + ALERTS and some CONTINUOUS + TRIGGERED.
Could someone elaborate the difference between these 2?
I just realized that I have some set up to record CONTINUOUS + ALERTS and some CONTINUOUS + TRIGGERED.
Could someone elaborate the difference between these 2?
looney2ns
IPCT Contributor
Sub Stream Guide
.substreamGuide td { border: 1px solid #000000; } .substreamGuide a { color: #0080ff; } .substreamGuide code.inline { margin: 0; background: #f6f6f6; border: 1px solid #e0e0e0; border-radius: 0px; padding-top: 1px; padding-right: 3px; padding-bottom: 1px...
Cont+Alerts means it will only switch to mainstream if it is motion that meets your criteria for an alert - for example, like you are using DeepStack for people but only want it to switch to mainstream if the trigger meets your alert criteria.
Cont+Trig means anytime the camera is triggered, it will switch to mainstream.
Most here do Cont+Trig because sometimes those that do not meet the alert criteria contain useful information.
Cont+Trig means anytime the camera is triggered, it will switch to mainstream.
Most here do Cont+Trig because sometimes those that do not meet the alert criteria contain useful information.
looney2ns
IPCT Contributor
