Send Motion-user mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/motion-user
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Motion-user digest..."
Today's Topics:
1. Re: Multiple movie files per event (Danny Medina)
2. Re: Multiple movie files per event (Jack Christensen)
3. Re: Multiple movie files per event (tosiara)
----------------------------------------------------------------------
Message: 1
Date: Thu, 10 Feb 2022 11:15:58 -0500
From: Danny Medina <[email protected]>
To: Motion discussion list <[email protected]>
Subject: Re: [Motion-user] Multiple movie files per event
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
As I'm setting things up, i began to wonder what the problem on my setup was
and it was just this.. Thanks for sharing this piece of info. I thought the
movies would max out at 1 minute hence i increased it to 5 mins (3600) and saw
no files being created.
On February 10, 2022 2:41:56 AM EST, tosiara <[email protected]> wrote:
>movie_max_time 60 means that new movie file will be created for an
>event that lasts longer than 60 seconds. You should see new file
>created every 60 seconds. Not necessarily resulted movies will all be
>60 seconds long, as if there was no motion gap during the event -
>frames are not recorded
>
>Maybe you could share a log file with -d 9 that contains at least two
>events each not less than 60 sec?
>
>
>On Thu, Feb 10, 2022 at 12:13 AM Jack Christensen
><[email protected]> wrote:
>>
>> Since installing 4.4.0 (on three Raspberry Pi ZeroW, from source), I am
>> seeing a new behavior; a single event will sometimes generate multiple
>> movie files. I guess this is not particularly an issue, but I wonder why
>> it occurs now when I didn't notice it before. Configuration file is the
>> same, I have movie_max_time 60. Wondering if anyone else has noticed this.
>>
>> For example, from the motion log. These four files were 22, 28, 9 and 15
>> seconds in length.
>>
>> [1:ml1:CAM2] [NTC] [ALL] [Feb 09 16:44:42] motion_detected: Motion
>> detected - starting event 117
>> [1:ml1:CAM2] [NTC] [EVT] [Feb 09 16:44:43] event_newfile: Writing movie
>> to file: /home/jack/motion-output/2-20220209-164442-117.mkv
>> [1:ml1:CAM2] [NTC] [EVT] [Feb 09 16:46:33] event_newfile: Writing movie
>> to file: /home/jack/motion-output/2-20220209-164633-117.mkv
>> [1:ml1:CAM2] [NTC] [EVT] [Feb 09 16:48:00] event_newfile: Writing movie
>> to file: /home/jack/motion-output/2-20220209-164759-117.mkv
>> [1:ml1:CAM2] [NTC] [EVT] [Feb 09 16:49:04] event_newfile: Writing movie
>> to file: /home/jack/motion-output/2-20220209-164903-117.mkv
>> [1:ml1:CAM2] [NTC] [ALL] [Feb 09 16:50:18] mlp_actions: End of event 117
>>
>> --
>> Jack Christensen
>> Sent from Linux Mint 20.1 using Mozilla Thunderbird
>>
>>
>>
>> _______________________________________________
>> Motion-user mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/motion-user
>> https://motion-project.github.io/
>>
>> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
>
>
>_______________________________________________
>Motion-user mailing list
>[email protected]
>https://lists.sourceforge.net/lists/listinfo/motion-user
>https://motion-project.github.io/
>
>Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 2
Date: Thu, 10 Feb 2022 13:13:21 -0500
From: Jack Christensen <[email protected]>
To: [email protected]
Subject: Re: [Motion-user] Multiple movie files per event
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8; format=flowed
Here is just the first example with -d 9. Let me know if that doesn't
fit the criteria you wanted. The two files are 0:11 and 0:10 in length,
but cover 1:05 and 0:11 elapsed time, respectively.
[1:ml1:CAM3] [NTC] [ALL] [Feb 10 12:57:05] motion_detected: Motion
detected - starting event 1
[1:ml1:CAM3] [INF] [EVT] [Feb 10 12:57:05] event_ffmpeg_newfile: Source
FPS 4
[1:ml1:CAM3] [INF] [ENC] [Feb 10 12:57:05] ffmpeg_set_quality: libx264
codec vbr/crf/bit_rate: 25
[1:ml1:CAM3] [NTC] [EVT] [Feb 10 12:57:05] event_newfile: Writing movie
to file: /home/jack/motion-output/3-20220210-125704-001.mkv
[1:ml1:CAM3] [DBG] [EVT] [Feb 10 12:58:10] exec_command: Executing
external command '/home/jack/sync.sh
/home/jack/motion-output/3-20220210-125704-001.mkv'
[1:ml1:CAM3] [DBG] [EVT] [Feb 10 12:58:10] event_closefile: Saved movie
to file: /home/jack/motion-output/3-20220210-125704-001.mkv
[1:ml1:CAM3] [INF] [EVT] [Feb 10 12:58:10] event_ffmpeg_newfile: Source
FPS 4
[1:ml1:CAM3] [INF] [ENC] [Feb 10 12:58:10] ffmpeg_set_quality: libx264
codec vbr/crf/bit_rate: 25
[1:ml1:CAM3] [NTC] [EVT] [Feb 10 12:58:10] event_newfile: Writing movie
to file: /home/jack/motion-output/3-20220210-125809-001.mkv
[1:ml1:CAM3] [DBG] [EVT] [Feb 10 12:59:20] exec_command: Executing
external command '/home/jack/sync.sh
/home/jack/motion-output/3-20220210-125809-001.mkv'
[1:ml1:CAM3] [DBG] [EVT] [Feb 10 12:59:20] event_closefile: Saved movie
to file: /home/jack/motion-output/3-20220210-125809-001.mkv
[1:ml1:CAM3] [NTC] [ALL] [Feb 10 12:59:20] mlp_actions: End of event 1
On 2/10/22 02:41, tosiara wrote:
> movie_max_time 60 means that new movie file will be created for an
> event that lasts longer than 60 seconds. You should see new file
> created every 60 seconds. Not necessarily resulted movies will all be
> 60 seconds long, as if there was no motion gap during the event -
> frames are not recorded
>
> Maybe you could share a log file with -d 9 that contains at least two
> events each not less than 60 sec?
>
>
> On Thu, Feb 10, 2022 at 12:13 AM Jack Christensen
> <[email protected]> wrote:
>> Since installing 4.4.0 (on three Raspberry Pi ZeroW, from source), I am
>> seeing a new behavior; a single event will sometimes generate multiple
>> movie files. I guess this is not particularly an issue, but I wonder why
>> it occurs now when I didn't notice it before. Configuration file is the
>> same, I have movie_max_time 60. Wondering if anyone else has noticed this.
>>
>> For example, from the motion log. These four files were 22, 28, 9 and 15
>> seconds in length.
>>
>> [1:ml1:CAM2] [NTC] [ALL] [Feb 09 16:44:42] motion_detected: Motion
>> detected - starting event 117
>> [1:ml1:CAM2] [NTC] [EVT] [Feb 09 16:44:43] event_newfile: Writing movie
>> to file: /home/jack/motion-output/2-20220209-164442-117.mkv
>> [1:ml1:CAM2] [NTC] [EVT] [Feb 09 16:46:33] event_newfile: Writing movie
>> to file: /home/jack/motion-output/2-20220209-164633-117.mkv
>> [1:ml1:CAM2] [NTC] [EVT] [Feb 09 16:48:00] event_newfile: Writing movie
>> to file: /home/jack/motion-output/2-20220209-164759-117.mkv
>> [1:ml1:CAM2] [NTC] [EVT] [Feb 09 16:49:04] event_newfile: Writing movie
>> to file: /home/jack/motion-output/2-20220209-164903-117.mkv
>> [1:ml1:CAM2] [NTC] [ALL] [Feb 09 16:50:18] mlp_actions: End of event 117
>>
>
------------------------------
Message: 3
Date: Thu, 10 Feb 2022 20:35:38 +0200
From: tosiara <[email protected]>
To: Motion discussion list <[email protected]>
Subject: Re: [Motion-user] Multiple movie files per event
Message-ID:
<cachtdwqrosgcjgte5yvmvsgodclhe5ssqx7gkgpocqx1rlz...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Strange that the first movie was not exactly 1:00
And if you change movie_max_time to 30 - do you get more shorter movies?
On Thu, Feb 10, 2022 at 8:14 PM Jack Christensen
<[email protected]> wrote:
>
> Here is just the first example with -d 9. Let me know if that doesn't
> fit the criteria you wanted. The two files are 0:11 and 0:10 in length,
> but cover 1:05 and 0:11 elapsed time, respectively.
>
> [1:ml1:CAM3] [NTC] [ALL] [Feb 10 12:57:05] motion_detected: Motion
> detected - starting event 1
> [1:ml1:CAM3] [INF] [EVT] [Feb 10 12:57:05] event_ffmpeg_newfile: Source
> FPS 4
> [1:ml1:CAM3] [INF] [ENC] [Feb 10 12:57:05] ffmpeg_set_quality: libx264
> codec vbr/crf/bit_rate: 25
> [1:ml1:CAM3] [NTC] [EVT] [Feb 10 12:57:05] event_newfile: Writing movie
> to file: /home/jack/motion-output/3-20220210-125704-001.mkv
> [1:ml1:CAM3] [DBG] [EVT] [Feb 10 12:58:10] exec_command: Executing
> external command '/home/jack/sync.sh
> /home/jack/motion-output/3-20220210-125704-001.mkv'
> [1:ml1:CAM3] [DBG] [EVT] [Feb 10 12:58:10] event_closefile: Saved movie
> to file: /home/jack/motion-output/3-20220210-125704-001.mkv
> [1:ml1:CAM3] [INF] [EVT] [Feb 10 12:58:10] event_ffmpeg_newfile: Source
> FPS 4
> [1:ml1:CAM3] [INF] [ENC] [Feb 10 12:58:10] ffmpeg_set_quality: libx264
> codec vbr/crf/bit_rate: 25
> [1:ml1:CAM3] [NTC] [EVT] [Feb 10 12:58:10] event_newfile: Writing movie
> to file: /home/jack/motion-output/3-20220210-125809-001.mkv
> [1:ml1:CAM3] [DBG] [EVT] [Feb 10 12:59:20] exec_command: Executing
> external command '/home/jack/sync.sh
> /home/jack/motion-output/3-20220210-125809-001.mkv'
> [1:ml1:CAM3] [DBG] [EVT] [Feb 10 12:59:20] event_closefile: Saved movie
> to file: /home/jack/motion-output/3-20220210-125809-001.mkv
> [1:ml1:CAM3] [NTC] [ALL] [Feb 10 12:59:20] mlp_actions: End of event 1
>
> On 2/10/22 02:41, tosiara wrote:
> > movie_max_time 60 means that new movie file will be created for an
> > event that lasts longer than 60 seconds. You should see new file
> > created every 60 seconds. Not necessarily resulted movies will all be
> > 60 seconds long, as if there was no motion gap during the event -
> > frames are not recorded
> >
> > Maybe you could share a log file with -d 9 that contains at least two
> > events each not less than 60 sec?
> >
> >
> > On Thu, Feb 10, 2022 at 12:13 AM Jack Christensen
> > <[email protected]> wrote:
> >> Since installing 4.4.0 (on three Raspberry Pi ZeroW, from source), I am
> >> seeing a new behavior; a single event will sometimes generate multiple
> >> movie files. I guess this is not particularly an issue, but I wonder why
> >> it occurs now when I didn't notice it before. Configuration file is the
> >> same, I have movie_max_time 60. Wondering if anyone else has noticed this.
> >>
> >> For example, from the motion log. These four files were 22, 28, 9 and 15
> >> seconds in length.
> >>
> >> [1:ml1:CAM2] [NTC] [ALL] [Feb 09 16:44:42] motion_detected: Motion
> >> detected - starting event 117
> >> [1:ml1:CAM2] [NTC] [EVT] [Feb 09 16:44:43] event_newfile: Writing movie
> >> to file: /home/jack/motion-output/2-20220209-164442-117.mkv
> >> [1:ml1:CAM2] [NTC] [EVT] [Feb 09 16:46:33] event_newfile: Writing movie
> >> to file: /home/jack/motion-output/2-20220209-164633-117.mkv
> >> [1:ml1:CAM2] [NTC] [EVT] [Feb 09 16:48:00] event_newfile: Writing movie
> >> to file: /home/jack/motion-output/2-20220209-164759-117.mkv
> >> [1:ml1:CAM2] [NTC] [EVT] [Feb 09 16:49:04] event_newfile: Writing movie
> >> to file: /home/jack/motion-output/2-20220209-164903-117.mkv
> >> [1:ml1:CAM2] [NTC] [ALL] [Feb 09 16:50:18] mlp_actions: End of event 117
> >>
> >
>
>
> _______________________________________________
> Motion-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/motion-user
> https://motion-project.github.io/
>
> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
------------------------------
------------------------------
Subject: Digest Footer
_______________________________________________
Motion-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/motion-user
------------------------------
End of Motion-user Digest, Vol 188, Issue 11
********************************************
