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: Timelapse video with inter-frame compression? (Arrow22)
2. Re: Problem with recording when a there is a "big" moving
object (tosiara)
----------------------------------------------------------------------
Message: 1
Date: Sat, 8 Jan 2022 09:03:02 -0800
From: "Arrow22" <[email protected]>
To: "'Motion discussion list'" <[email protected]>
Subject: Re: [Motion-user] Timelapse video with inter-frame
compression?
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
So, more like a time lapse?
I think Motion has that built in
Xeoma definitely does - not in the freeware version
From: Thomas Rogenmoser [mailto:[email protected]]
Sent: Thursday, January 6, 2022 2:36 AM
To: [email protected]
Subject: [Motion-user] Timelapse video with inter-frame compression?
Hi.
My question is from me researching how to create a webcam with minimal data
needs (to save mobile data costs).
It basically is, does motion support inter-frame compression on timelapse
videos?
Background:
The cam will need to send a few pics per hour to a server. Pics will have
minimal visual difference (observe a river's waterlevel).
So the idea is to save data by using inter-frame video compression.
The basic setup would be: on- camera (raspi), append every new pic. as a
new frame to an eg. daily video.
Send only the diff of the video file to the server, which will present the
regularly updated file to users, extracts the last frame if only a pic. is
needed, etc.
I am happy about any kind of input to my idea, namely towards any roadblocks
I am not aware of yet.
I first found motionEyeOS, which has it's own way to do timelapse videos,
that seems not suitable for my idea.
Not sure if this question should be asked even deeper down the stack, in an
ffmpeg related forum. Just tell me if I am off-topic here.
Thanks,
toro
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 2
Date: Sun, 9 Jan 2022 08:13:07 +0200
From: tosiara <[email protected]>
To: Motion discussion list <[email protected]>
Subject: Re: [Motion-user] Problem with recording when a there is a
"big" moving object
Message-ID:
<cachtdwtdzf+2kscvx4sh75cwnawdnfuffdrdfdufk-slurm...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Could you send the new movie file and a log with -d 9?
On Sat, Jan 8, 2022, 13:34 Entmatix <[email protected]> wrote:
> Tried it. Nothing has changed.
>
> 6 ???. 2022 ?., ? 11:02, tosiara <[email protected]> ???????(?):
>
> And also comment out this line:
>
> #movie_quality 45
>
> On Thu, Jan 6, 2022 at 10:01 AM tosiara <[email protected]> wrote:
>
>> Could you try to increase the bitrate to something bigger and also try
>> different codec, like:
>>
>> movie_bps 9000000
>> movie_codec mp4
>>
>> Does that change anything?
>>
>> On Mon, Dec 13, 2021 at 8:39 AM Entmatix <[email protected]> wrote:
>>
>>> Sorry, I can?t give you full or non-cropped version of recording. Hope
>>> the example video I attached shows what I?m talking about. From 00s to 03s
>>> there is no motion, from 04s to 07s there is motion. Thats how the full
>>> video looks like - pixel puzzle. Log is also attached.
>>>
>>> > 8 ???. 2021 ?., ? 15:46, tosiara <[email protected]> ???????(?):
>>> >
>>> > Could you please reproduce the issue once again with the 4.4 version
>>> > and collect -d 9 log for us? And if possible, please provide a sample
>>> > video with issue and without issue.
>>> >
>>> > On Thu, Dec 2, 2021 at 4:36 PM Entmatix <[email protected]> wrote:
>>> >>
>>> >> I managed to switch back to version 4.2.1 from 2018 and it works like
>>> a charm. Seems like some kind of regression in after 4.2.1 version(s).
>>> >>
>>> >> 27 ????. 2021 ?., ? 20:47, Harlan Daneker <[email protected]>
>>> ???????(?):
>>> >>
>>> >> The other thing that comes to mind is the keyframe setting on the
>>> camera.
>>> >>
>>> https://support.restream.io/en/articles/1668135-wrong-keyframe-warning
>>> >>
>>> >> On Sat, Nov 27, 2021 at 12:34 PM Harlan Daneker <[email protected]>
>>> wrote:
>>> >>>
>>> >>> ffmpeg_output_movies off
>>> >>> movie_extpipe_use on
>>> >>> movie_extpipe x264 - --input-res %wx%h --fps %fps --bitrate 2000
>>> --preset ultrafast --quiet -o %f.mp4
>>> >>>
>>> >>>
>>> >>> On Sat, Nov 27, 2021 at 12:24 PM Harlan Daneker <[email protected]>
>>> wrote:
>>> >>>>
>>> >>>> You could try this, but you may have to install x264. This is what
>>> I'm using. I'm just guessing.
>>> >>>>
>>> >>>> movie_extpipe x264 - --input-res %wx%h --fps %fps --bitrate 2000
>>> --preset ultrafast --quiet -o %f.mp4
>>> >>>>
>>> >>>> On Sat, Nov 27, 2021 at 12:16 PM Entmatix <[email protected]>
>>> wrote:
>>> >>>>>
>>> >>>>> Camera is using hevc (h265). I?ve tried to switch both camera and
>>> motion to same h264 format (camera to h264, motion to mkv). Still have
>>> problems. It?s kinda strange because 2-3 years ago with similar camera I
>>> haven?t experience any troubles.
>>> >>>>>
>>> >>>>> 27 ????. 2021 ?., ? 20:08, Harlan Daneker <[email protected]>
>>> ???????(?):
>>> >>>>>
>>> >>>>> What is the camera using, not the computer?
>>> >>>>>
>>> >>>>> On Sat, Nov 27, 2021 at 12:04 PM Entmatix <[email protected]>
>>> wrote:
>>> >>>>>>
>>> >>>>>> Just tried mkv. Unfortunately, no success. Same low fps with
>>> glitches.
>>> >>>>>>
>>> >>>>>> 27 ????. 2021 ?., ? 19:35, Harlan Daneker <[email protected]>
>>> ???????(?):
>>> >>>>>>
>>> >>>>>> I've had some issues with cameras using the H265 codec.
>>> >>>>>>
>>> >>>>>> On Sat, Nov 27, 2021 at 11:14 AM Entmatix <[email protected]>
>>> wrote:
>>> >>>>>>>
>>> >>>>>>>
>>> >>>>>>> Hello all.
>>> >>>>>>>
>>> >>>>>>> Sorry if I do something wrong, it?s my first time asking help in
>>> mailing list.
>>> >>>>>>>
>>> >>>>>>> Motion 4.3.2 from Debian 11 official repo. ffmpeg version
>>> 4.3.2-0+deb11u2. Motion settings:
>>> >>>>>>>
>>> >>>>>>> daemon on
>>> >>>>>>> setup_mode off
>>> >>>>>>> log_level 6
>>> >>>>>>> target_dir /mnt/hdd/motion-records
>>> >>>>>>> emulate_motion off
>>> >>>>>>> threshold 2000
>>> >>>>>>> noise_level 40
>>> >>>>>>> minimum_motion_frames 3
>>> >>>>>>> event_gap 5
>>> >>>>>>> pre_capture 5
>>> >>>>>>> post_capture 50
>>> >>>>>>> picture_output off
>>> >>>>>>> picture_filename %Y%m%d%H%M%S-%q
>>> >>>>>>> movie_output on
>>> >>>>>>> movie_output_motion off
>>> >>>>>>> movie_max_time 600
>>> >>>>>>> movie_quality 80
>>> >>>>>>> movie_codec hevc
>>> >>>>>>> movie_filename %t-%v-%Y-%m-%d--%H-%M-%S
>>> >>>>>>> webcontrol_port 8080
>>> >>>>>>> webcontrol_localhost on
>>> >>>>>>> webcontrol_parms 0
>>> >>>>>>> stream_port 8081
>>> >>>>>>> stream_localhost on
>>> >>>>>>> movie_passthrough yes
>>> >>>>>>> camera_dir /etc/motion/camera.d
>>> >>>>>>>
>>> >>>>>>> Camera settings:
>>> >>>>>>>
>>> >>>>>>> camera_name MyCam1
>>> >>>>>>> camera_id 101
>>> >>>>>>> netcam_url 'rtsp://...'
>>> >>>>>>> width 1280
>>> >>>>>>> height 720
>>> >>>>>>> text_left CAMERA 1
>>> >>>>>>> movie_filename %H-%M-%S
>>> >>>>>>>
>>> >>>>>>> The problem: if there any small changes in frames (little moving
>>> object) then record is fine, but if something is more than 5% of space that
>>> is being recorded then I get 1 fps or even worse (1 fp few seconds) in
>>> recording and a lot of glitches (pixel puzzle, gray regions). Live mode is
>>> ok. Hardware is quite good: ryzen 2600x, 16 Gb RAM, WD Gold. Don?t see any
>>> performance issues. CPU always stays below 5%, RAM below 10%. Connection is
>>> also fine (100 Mbps with 10-15 ms ping).
>>> >>>>>>>
>>> >>>>>>> I?ve tried to tweak options like event gap, pre/post capture,
>>> minimum motion frames, etc. Nothing works. Don?t know what?s the reason.
>>> Log shows nothing wrong. Any ideas?
>>> >>>>>>> _______________________________________________
>>> >>>>>>> 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
>>> >>>>>>
>>> >>>>>>
>>> >>>>>> _______________________________________________
>>> >>>>>> 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
>>> >>>>>
>>> >>>>>
>>> >>>>> _______________________________________________
>>> >>>>> 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
>>> >>
>>> >>
>>> >> _______________________________________________
>>> >> 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
>>>
>>> _______________________________________________
>>> 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
>
>
> _______________________________________________
> 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...
------------------------------
------------------------------
Subject: Digest Footer
_______________________________________________
Motion-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/motion-user
------------------------------
End of Motion-user Digest, Vol 187, Issue 5
*******************************************