already show current file/segment even when not yet finished

[titro]

default is a segment duration of 30 secs. this is way too low for a 7/24 recording. This results in several thousand video files per day.

If you increase segment duration you are only able to see the file (and all objects etc) and the video in the timeline after finishing the segment.

Is it possible to already show started segments in the overview and timeline even when it is still recording into that segment?

[matteius]

30 seconds is about preserving evidence, as if you drop a recording mid flight it will not be viewable. Which is part of the answer to the second question, withhout the valid h264 sequences a recording is not viewable when its in flight -- you wouldn't be able to watch it until it completes in any kind of setting is my understanding.

[titro]

but did you already made some tests how much files lightvr can handle? 3000 files per day per cam stream seems to much for handling with good performande

[titro]

hey @matteius
thought about it and what about a combination of short and long segments:

The initial recording results in short segments (10-30 seconds).

And in frequently processed "reorganisation jobs" the short segments are joined together into longer segments, e.g. 5 or 10 minutes. This would have the benefits of both worlds: short segments so almost instant are near to live video the segments on the timeline and after some hours or a day longer videos without switching between to many videos if you play the timeline for some minutes and especially: very less files on the filesystem.

I checked the database regarding the persistence changes. Not a quick fix but seems doable.

What do you think?

[matteius]

Keeping this open as a larger recording-compaction enhancement. An in-flight ordinary MP4 is not safely seekable until its metadata is finalized, so the current segment itself cannot simply be exposed early. The proposed short-segment-to-long-segment job is feasible, but it must be atomic and preserve detection intervals, tags, protection/retention state, trigger type, and timeline continuity; it must also never touch an active segment and must recover cleanly if remuxing fails. That is separate from the live timeline display fix and should not be treated as a quick filename/UI change.