Sergey 'Jin' Bostandzhyan

I think I might know what I did wrong, so it seems in the dev version the configuration has changed and the `folder` option is obsolete, one has to use...

Retested with the new storage settings, something is still off, the log shows: ``` viseron | [2024-11-18 19:49:54] [INFO ] [viseron.components.nvr.nvr.camera_1] - Stopping recording in: 1 viseron | [2024-11-18 19:49:55]...

Thank you for getting back to me! Yes indeed I saw the segments on ramdisk, but assumed they were something internal, especially seeing in the logs how they get regularly...

Did a short test with the suggested setting and the complete `.mp4` videos of individual events got created, however when I did a graceful shutdown, the `.mp4` files got lost....

> Correct, the fragments are not cleaned up since they are what Viseron uses mainly. > > The Viseron UI does not utilize the MP4 recordings at all, it only...

I have more logs and a somewhat strange behaviour, I should probably update my dev image to make sure I am running the latest code. So, after making some changes...

> The segments are stored for as long as they are wanted. > In your case, since you are only storing events, only the segments that relate to an event...

> The problem is that v2 uses `/recordings` to store "event clip" (the only kind of recording in v2) so for easier transition to v3 i had to go with...

> Yeah a lot of people seem to have the same expectations as you have. > I think writing a proper glossary and also documentation on how Viseron handles recordings...

I am still battling the "clips" issue, so my config has: ``` recorder: filename_pattern: east_%Y-%m-%d-%H:%M:%S create_event_clip: true ``` So my expectation was that it would now create those `mp4` clips...