Replies: 12 comments
-
|
Please provide the full log with |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
This is a very verbose/noisy log, but you can see that event 1 is saved as |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
There can be (and are) multiple pictures per movie and multiple movies per event so there isn't going to be a one to one correlation of pictures and movies. The current source code version does add a |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
On a earlier version they were one to one/got the same names though 🤔 I'm not sure what configuration will give multiple pictures/movies per event? I only get a single movie and picture with this config. The mismatch in filenames makes it very hard to manage these files afterwards. I would very much like them to still be given the same filenames. I'm happy to hear other input on how you are supposed to be able to manage these files if the filenames do not match? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
The Also, as I look at the code, additional problems arise with the premise that the picture time stamp should be identical to the movie time stamp. The movie time stamp correlates with the time that the movie starts. This would include the preview frames. The I'm not sure what you are "managing" with the files but I'd guess that a better key than the timestamp would be the camera id in combination with the event id. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
But this changed in a recent version? (Last time I used Motion might have been the version on Rasbian, based on Debian 10). And it seems to be inconsistent. Like I said, the I manage the files on a simple webpage. Here I use the picture as a "thumbnail" for a link to the corresponding movie. This was easy before, when the images and movies shared the same filename. If I'm not mistaken there is currently no way to do this anymore, without some extra logic and assumptions. You can't really use the eventid either, because it will be reset upon a restart of motion. I haven't been using the database support myself, but it doesn't seem (from reading the config) to store information about related files either. If it's not doable with Motion itself I guess I could disable I would still very much like it if Motion still saved these files with the same filename/timestamp though 👍 |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Could you update to the latest version 4.4.0, reproduce once again win |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I've previously used the packages available through Raspberry PI OS, but installed 4.4.0 through deb file from github now. Looks like it saved two files, still with different names: The log: |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Interesting, now there is discrepancy with timestamps: Files seems to be created at the same time as event triggered, but movie time is in the past - 2 seconds before event started. How that is possible? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Like I said....they are NOT linked to each other and represent different things. The picture is first motion which occurs after the preview capture frames. The movie starts with the preview frames that occurs before first motion. Additionally, multiple movies can come from a single event so that positively will result in a disconnect. You could get them closer together for the first movie by specifying I'll be re-tagging this as an enhancement and moving it to the discussion section. The current picture_output options will not (and as I've explained should not) have the same timestamp as the movies. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Ok, so |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
A
I see the points mentioned by @Mr-Dave . I would however still like Motion to actually provide an ability to save movies and their corresponding picture, and make sure that these files get the same names. For my use I understand if this won't be any priority though. I think I'm able to solve my own need with |
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
-
Did you read the guide?
Yes
What is the base version number of Motion being used?
4.3.x
What was the install method?
Installed via package tool
What is base architecture?
ARM-64bit
What is the distro being used?
Raspbian
Disto version number
11, bullseye
Camera type(s) being used?
Other
Describe the issue/problem and steps to reproduce
I use these related config values:
On a previous version of motion (I do not remember which) I experienced that the picture and movie filenames would match. Now they do not always match. The picture filename seems to be created 0-3 seconds after the movie filename. E.g:
I believe this can be considered an issue/bug?
It's hard to manage these files when the names for the same event doesn't match.
It would be very nice if it's possible to make sure that they do match, which I think is the expected behavior.
Relevant Motion log output (at log_level 8)
Beta Was this translation helpful? Give feedback.
All reactions