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. Timelapse video with inter-frame compression? (Thomas Rogenmoser)
2. Motion 4.4.0 on Raspberry Pi Buster (Andrew Conway)
----------------------------------------------------------------------
Message: 1
Date: Thu, 6 Jan 2022 11:36:04 +0100
From: "Thomas Rogenmoser" <[email protected]>
To: <[email protected]>
Subject: [Motion-user] Timelapse video with inter-frame compression?
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
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: Thu, 6 Jan 2022 11:06:46 +0000
From: Andrew Conway <[email protected]>
To: [email protected]
Subject: [Motion-user] Motion 4.4.0 on Raspberry Pi Buster
Message-ID:
<CAJRa=rhjyug4mgnpjbk9got6zqgomadrbexttrmarebjjq6...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
I've been using 4.2.2 on a Raspberry Pi with Raspbian Stretch for a
couple years with no problems but have hit an issue trying to get
4.4.0 working on Raspberry OS Buster. I did on a fresh full install of
the OS, then installed gdebi and then installed motion like this:
sudo gdebi pi_buster_motion_4.4.0-1_armhf.deb
Under "Run as service" in the docs
(https://motion-project.github.io/motion_config.html) it says:
"Motion now uses the systemctl and when running as a service, the
option daemon must be set as off."
I did this but starting motion with
sudo systemctl start motion
failed to start motion and
sudo systemctl status motion
told me
...motion[3592]: Not starting motion daemon, disabled via
/etc/default/motion ...
So I changed /etc/default/motion to contain
start_motion_daemon=yes
and then motion started and was working normally.
The settings in /etc/motion/motion.conf and /etc/default/motion seem
to contradict each other. Is it worth updating the docs on this point
or is this just peculiar to how I'm using it on the Raspberry Pi? I
noticed the amd64 deb includes a motion.service file included whereas
the raspberry pi version for buster does not.
Andrew
------------------------------
------------------------------
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 3
*******************************************
