Motion uses the same event Id (%v) for videos #1819
Joerg12345
started this conversation in
General
Replies: 3 comments 9 replies
-
|
Could you please upload the full log? |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Here is the complete log with 3 cameras and a newly started motion with log_type All an log_level 8. |
Beta Was this translation helpful? Give feedback.
-
|
You have set If you want an event to always have a single movie file, set movie_max_time to something very large |
Beta Was this translation helpful? Give feedback.
8 replies
-
|
In this version Here is the log file, again with 3 cameras and |
Beta Was this translation helpful? Give feedback.
-
|
yes, this was a bug, that was fixed, see comment: #1625 (comment) the correct behavior is:
If you want to have one movie per event and one picture that belongs to the one movie, you should set movie_max to some high value, as base on your need you don't need movie file split feature |
Beta Was this translation helpful? Give feedback.
-
|
Then I'll probably stick with version 4.3.2. Can an option be built into a newer version of motion that can be used to turn this behavior on/off? |
Beta Was this translation helpful? Give feedback.
-
|
No, there is no way to go back as it was a bugfix. Keep in mind that with this bug every time you get a new movie file you will also get a new event, which will include on_event_end execution even though the event has not finished yet |
Beta Was this translation helpful? Give feedback.
-
|
That may be true, but it doesn't bother me because I only use on_movie_end and on_picture_save. Thanks for the answers. Best regards, |
Beta Was this translation helpful? Give feedback.
-
|
I will open a different thread with a suggestion - but I just stumbled over this issue today. I built some glue scripts to add secondary object detection for Motion using Yolo, on the assumption that every event corresponds to a single generated movie file. I didn't realise that a number of different movie files can share an event id. Unfortunately is is impractical to set movie_max_time to a really high value, as it makes it very difficult to download, stream and review resulting footage. Also, the movie might contain only a very small portion of relevant footage, as detected by secondary detection - which would make it very difficult to find where in the movie this is, if it is a long/large movie. I will open a different thread suggesting some sort of movie_id which maybe can be exposed through on_picture_save and on_movie_end. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
If multiple events are triggered in quick succession, motion uses the same event number (%v) for videos.
I think this occurs when ffmpeg is not finished generating the first video or jpg when the second event is triggered.
And for the second event no jpg file will be created.
Here is an excerpt from the log file (log level 6).
The first video (05:39:15) has a duration of 33 seconds.
The second video (05:39:55) has a duration of 9 seconds.
The jpg file (05:39:51) belongs to the first video.
No jpg image will be generated for the second video (05:39:55).
I believe that ffmpeg was not finished generating the video 05:39:15 or generating the jpg image 05:39:51 when the event for video 05:39:55 was triggered.
I use motion 4.7.0.
Beta Was this translation helpful? Give feedback.
All reactions