Unable to stop BI from recording

[w1r3d]

Hello,
I am in the need of some assistance with my BI setup.
My main issue is that I cannot stop it from recording, it will record for over 4hr if I let it.
I have it set to continuously record and trigger but this will not stop even with mo motion on the screen.
Even after I make a change to the camera's setting I get the colour bars and then it keeps recording
Break time to end within 20sec and max trigger duration is 60sec.
Motion settings are min obj size 608, min contrast 48
There is a red dot on the top right corner which I believe is to show its recording and on the left 'All clips' window has a red box around the small camera picture of the top recording.
Also on the bottom right is like a film strip and red dot which when I put my cursor on it I get 'one or more camera is recording' message.
I have seen people say to click on the traffic symbol but I can not see that kind of symbol
I believe that this is the reason why my CPU usage is at 70% with only one camera added
I have purchased the full license and intend to add another 12 cameras but I need to get my CPU usage down to like 15-20%

All help is greatly appreciated

 

[wittaj]

First off, if you are recording continuously, then that means it will record continuously...

If you only want it to record on triggers, then change continuous to when triggered.

Without knowing your CPU specs can't really answer that, but the recording isn't why the CPU is high. 70% for one camera sounds like a not very powerful computer and you are probably not using substreams.

What computer do you have?

 

[Mike A.]

If you only want it to record when there's motion detected, then change the setting to "When triggered."

Continuous + Triggered records the substream continually but switches to the main stream when triggered.

If your CPU is that high you're probably not using substreams. Set that up and you'll be where you want to be as far as CPU.

 

[w1r3d]

I have it set to 'continuous + trigger' as I don't want to miss any events at least during the setting up phase.
The attached pic shows the red dot and red box which makes me think it's just recording without any triggers.
My understanding is that the 'continuous + trigger' setting should not show the red box and red dot, I am still learning this system.
Once I have this sorted out I will look into my CPU usage on a different thread.

 

[fenderman]

I have it set to 'continuous + trigger' as I don't want to miss any events at least during the setting up phase.
The attached pic shows the red dot and red box which makes me think it's just recording without any triggers.
My understanding is that the 'continuous + trigger' setting should not show the red box and red dot, I am still learning this system.
Once I have this sorted out I will look into my CPU usage on a different thread.

You are not understanding correctly. The red dot will show when recording - sub or main. The orange box around the actual live camera view will show when a camera is triggered. The red box around the clip view indicates that the file is open to be written to. Its all in the help file.

 

[Mike A.]

I have it set to 'continuous + trigger' as I don't want to miss any events at least during the setting up phase.
The attached pic shows the red dot and red box which makes me think it's just recording without any triggers.
My understanding is that the 'continuous + trigger' setting should not show the red box and red dot, I am still learning this system.
Once I have this sorted out I will look into my CPU usage on a different thread.

Continuous + trigger records continually. So it's doing what you've set it to do. Read the responses above and/or check the help file for an explanation of the various record modes.

Continuous + trigger does show the red recording dot full time since it's recording continually. The box will turn red when triggered.

 

[w1r3d]

I understand thanks the details
would having it set to continuously + trigger result in a 70% CPU usage with just 1 camera?
I will look into this further

 

[wittaj]

As I mentioned, recording continously isn't the cause of the high CPU.

I asked for what are the specs of the computer you are using and are you using the substreams? Is it a laptop? Is it Intel and if so what I number and processor? How much RAM?

 

[Mike A.]

Not typically. What computer and what camera and what settings? If you're running the Eval version, unless something has changed in more recent versions, then I think some settings to reduce CPU aren't available (e.g., direct to disk).

 

[TonyR]

Not to pile on, as you have already received several helpful answers and tips, I just want to mention a wealth of info can be found in BI's built-in "Help" file (the big ? up at the top left of the screen). Below is an excerpt found under "Recording and Clips" > "Recording options" > "Video":

"Continuous + triggered. Similar to Continuous + alerts, but main stream recording occurs upon trigger, not just alerts, ensuring that the main stream is recorded even for canceled alerts."​