ramaz16 wrote: ↑Tue Apr 06, 2021 4:52 am
BVR Trimming
It would be nice to trim and save an existing BVR section as a separate BVR without re-encoding.
However, conversion might make them inadmissible into evidence in some jurisdictions, where video evidence is often treated by courts as "hearsay", especially if its not the original footage.
Firstly, editing the BVR introduces the exact same tamper/custody concerns from an evidentiary perspective as exporting. If you edit it, the file format is irrelevant - it is not an original.
Secondly, BI already allows a user to accomplish the same thing as a trim feature but more elegantly. The difference is how it's done. To my way of thinking, you create a clone edit its settings -> record when triggered -> disable combine/cut on the record tab, and set the clone's detector appropriate for events of interest. Every event recorded by the clone will be a discrete BVR for that event. The clone master will have it's original sensor and record settings, maybe continuous recording cut every 8 hours or whatever... but the clone will produce a BVR for each trigger and the master will have a BVR for what it records. They will both live in the stored folder. Further, you can tweak the break time and make time of the clone to capture more motion pre and post trigger.
You now have two pristine files to hand over to the police if need be - the event and a backup. The authenticity would be uncontested. So no disrespect for opposing opinions, I have trouble seeing the utility in editing and subsequently exporting a BVR file format.
Personally, I would rather see development efforts focused on a scrubber during timeline playback.
Not sayin' I'm right, I'm just sayin' that's how I see it.