'Direct 2 Disk' seems to force continuous recording

[MHotchin]

I have been working on optimizing my setup, and have run into an issue when using 'Direct to Disk' recording.

Previously, I used re-encoding, and had recording set up as 'Triggered+periodic' - every 5 sec, for 0 sec. This would record a snapshot every 5 seconds, and continuous when triggered.

I switched to 'Direct to Disk', and now the recorded video is continuous. This is blowing up my recorded video size obviously.

I saw nothing in the help file that suggested that Direct To Disk was Continuous only - is this expected behaviour?

Setup:
- Windows 10, up to date
- BI 5.9.0.7 (latest stable)
- Various cameras, specific one doesn't seem to matter. In particular:
- Reolink 823A
- Video is H265, 15fps, keyframe is 1 per second. Attached is a screenshot of the 'Record' tab of settings.

[MHotchin]

As a work-around, I've enabled lower quality second streams, and set the recording to Continuous Sub + Triggered.

However, the fact that it can switch between streams while using Direct to Disk would mean that Triggered + periodic is possible, but just not working - there's no technical obstacle to it.

Unfortunately, using a lower-quality sub-stream also affects the images provided by the BI web service. I used to get the full resolution, now all I get is the low res version even if the camera is triggered and recording high res video.

It's a hot mess. Seems like my only options are crappy snapshots and crappy non-triggered video, OR blow my disk usage out of the water.

[IAmATeaf]

In your screenshot you've set Triggered + Periodic so surely that is why it's recording 'continuously' ?

[MHotchin]

In your screenshot you've set Triggered + Periodic so surely that is why it's recording 'continuously' ?

No. When using software encoding, I get continuous video when triggered, otherwise I get 1 frame recorded every 5 seconds. The Recording icon reflects this - on when triggered, otherwise a blip every five seconds.

With direct to disk, it's always continuous.

[TimG]

From the Help file:

Video

When triggered. Video is only recorded when the camera is in a triggered state. This can greatly save on storage space over continuous recording. The pre-trigger video buffer applies only to this type of video recording. By default, multiple trigger events are stored into one file—see Combine or cut below.

When alerted. Much like When triggered, but video is only recorded when the camera is in a triggered state and the alert has been confirmed by AI or otherwise.

Continuous. Record video all of the time the camera is online and active.

Periodic. Record video in defined intervals in a discontinuous or time-lapse manner— meaning that playback gaps are removed.

Triggered + periodic. Combines when triggered with periodic. All frames are recorded when the camera is in the triggered state.

Continuous sub + alerts. When used with a dual-streaming camera along with direct to-disk, the result is a BVR file which will contain the sub-stream continuously recorded, but the main-stream only recorded when the camera is in an alerted state. During main-stream playback, the sub-stream will be upsampled whenever the mainstream is not available. This dual-stream hybrid may be exported only when reencoding is selected, although you may still export the main-stream in segments when not re-encoding. When not using dual-streams or direct-to-disk, recording of
the sub (or only) stream is continuous.

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

Now this text looks to contain your issue:

Direct-to-Disk

This option may be used to save considerable CPU time. Video taken from a network IP camera stream is directly saved to disk without re-encoding it. There are some disadvantages to this however:

• Recording may only begin on a key frame boundary. Check that your camera is sending sufficient key frames on the Cameras page in Status (at least 0.50 per second).

• Video overlays are saved as meta-data, not directly burned into the video. This may be an advantage however as you may toggle from on/off during playback.

• Cannot be used with time-lapse options. All video frames must be saved, as each frame relies on the previous one in order to be decoded for display.

• You may want to alter the quality, size, or other video characteristics.

• May only be used by network IP cameras with H.264 or H.265 streams.

• May not be used by analog or USB cameras, unless it’s an uncommon source that supplies H.264 or H.265 video.

[IAmATeaf]

Hence why it’s recording continuously?

[TimG]

It was the use of "periodic" that caught my eye

[MHotchin]

It appears that the latest update (5.9.1.5) has improved the situation. I have 'Direct to Disk' enabled, I'm using only one stream, and the recording properly records continuously when triggered.

It now records periodically, except that instead of just a snapshot, it records about 1-2 seconds of video. Still, it's better than recording continuously.