Send Motion-user mailing list submissions to
motion-user@lists.sourceforge.net
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
motion-user-requ...@lists.sourceforge.net
You can reach the person managing the list at
motion-user-ow...@lists.sourceforge.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Motion-user digest..."
Today's Topics:
1. Re: Using ffmpeg via extpipe (S?bastien Delafond)
2. Re: Using ffmpeg via extpipe (tosiara)
3. Re: Using ffmpeg via extpipe (S?bastien Delafond)
4. h.264 pass through (Brian Mengel)
5. Re: h.264 pass through (MrDave)
----------------------------------------------------------------------
Message: 1
Date: Wed, 24 Jan 2018 13:57:08 +0000 (UTC)
From: S?bastien Delafond <s...@debian.org>
To: motion-user@lists.sourceforge.net
Subject: Re: [Motion-user] Using ffmpeg via extpipe
Message-ID: <20180124145650....@usenet.piggo.com>
Content-Type: text/plain; charset=utf-8
On 2018-01-24, S?bastien Delafond <s...@debian.org> wrote:
> Here they are:
> [...]
So this capture worked: I could have sworn my previous tests proved the
contrary, but it's irrelevant now: the default extpipe example shipped
in motion.conf is functional. My problem with trying to encode to webm
therefore lies somewhere else. Sorry for wasting your time.
Cheers,
--Seb
------------------------------
Message: 2
Date: Wed, 24 Jan 2018 16:25:08 +0200
From: tosiara <tosi...@gmail.com>
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] Using ffmpeg via extpipe
Message-ID:
<cachtdwsjpxhehkbgny7gyd8qtbmdcd+ec2kwvv2359hjpsm...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Great to know that it works now
If you would like to get webm, you can use this extpipe command:
extpipe ffmpeg -y -f rawvideo -pix_fmt yuv420p -video_size %wx%h
-framerate %fps -i pipe:0 -vcodec libvpx %f.webm
On Wed, Jan 24, 2018 at 3:57 PM, S?bastien Delafond <s...@debian.org> wrote:
> On 2018-01-24, S?bastien Delafond <s...@debian.org> wrote:
>> Here they are:
>> [...]
>
> So this capture worked: I could have sworn my previous tests proved the
> contrary, but it's irrelevant now: the default extpipe example shipped
> in motion.conf is functional. My problem with trying to encode to webm
> therefore lies somewhere else. Sorry for wasting your time.
>
> Cheers,
>
> --Seb
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Motion-user mailing list
> Motion-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/motion-user
> https://motion-project.github.io/
>
> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
------------------------------
Message: 3
Date: Wed, 24 Jan 2018 16:41:45 +0000 (UTC)
From: S?bastien Delafond <s...@debian.org>
To: motion-user@lists.sourceforge.net
Subject: Re: [Motion-user] Using ffmpeg via extpipe
Message-ID: <20180124174113....@usenet.piggo.com>
On 2018-01-24, tosiara <tosi...@gmail.com> wrote:
> Great to know that it works now
> If you would like to get webm, you can use this extpipe command:
>
> extpipe ffmpeg -y -f rawvideo -pix_fmt yuv420p -video_size %wx%h
> -framerate %fps -i pipe:0 -vcodec libvpx %f.webm
And this is where I get the error:
,----
| [1:ml1] [NTC] [EVT] [Jan 24 16:37:04] event_new_video Source FPS 30
| [1:ml1] [NTC] [EVT] [Jan 24 16:37:04] event_create_extpipe: pipe: ffmpeg -y
-f rawvideo -pix_fmt yuv420p -video_size 1280x720 -framerate 30 -i pipe:0
-vcodec libvpx /var/lib/motion/2018-01-24/2018-01-24T16-37-04_01_23.webm
| [1:ml1] [NTC] [EVT] [Jan 24 16:37:04] event_create_extpipe: cnt->moviefps: 30
| [1:ml1] [NTC] [EVT] [Jan 24 16:37:04] event_newfile: File of type 8 saved to:
/var/lib/motion/2018-01-24/2018-01-24T16-37-04_01_23
| [1:ml1] [NTC] [ALL] [Jan 24 16:37:04] motion_detected: Motion detected -
starting event 1
| [1:ml1] [NTC] [EVT] [Jan 24 16:38:17] event_newfile: File of type 1 saved to:
/var/lib/motion/2018-01-24/2018-01-24T16-37-04_01_23.jpg
| [1:ml1] [NTC] [EVT] [Jan 24 16:38:17] event_extpipe_end: CLOSING: extpipe
file desc 9, error state 0
| [1:ml1] [NTC] [EVT] [Jan 24 16:38:17] event_extpipe_end: pclose return: -1
| [1:ml1] [NTC] [ALL] [Jan 24 16:38:17] motion_loop: End of event 1
`----
I guess at this point, since extpipe+ffmpeg->mp4 works fine, but
extpipe+ffmpeg->webm doesn't, there is something not quite right with my
versions of ffmpeg/libavcodec ?
Cheers,
--Seb
------------------------------
Message: 4
Date: Wed, 24 Jan 2018 17:27:26 -0500
From: Brian Mengel <bmen...@gmail.com>
To: motion-user@lists.sourceforge.net
Subject: [Motion-user] h.264 pass through
Message-ID:
<caav0nwcepwvxcxi0mekjn-bthcfwtkhmb942dysmkf_kke6...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Greetings,
I'm getting familiar with motion using an old Raspberry Pi Model B Rev 2
and a Logitech C920 web cam connected via a USB hub. This is obviously not
the ideal solution for high resolution/high frame rate video capture but
it's what I had laying around. The C920 offers a h.264 video steam
natively:
pi@raspberrypi:/etc/motion $ v4l2-ctl --list-formats
ioctl: VIDIOC_ENUM_FMT
Index : 0
Type : Video Capture
Pixel Format: 'YUYV'
Name : YUYV 4:2:2
Index : 1
Type : Video Capture
Pixel Format: 'H264' (compressed)
Name : H.264
Index : 2
Type : Video Capture
Pixel Format: 'MJPG' (compressed)
Name : Motion-JPEG
After reading over the issues on git (#124 and #591) concerning h.264 pass
through I wanted to confirm that I understood things correctly before I
worked on compiling from source in git. If I work out of the master branch
(assuming I can compile and run it) is there functionality there to perform
motion detection and store the compressed h.264 video that the camera
creates?
I just want to make sure I understand what can be done with pass through
before I really get going on this.
TIA!
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 5
Date: Wed, 24 Jan 2018 21:41:13 -0700
From: MrDave <motionmrd...@gmail.com>
To: motion-user@lists.sourceforge.net
Subject: Re: [Motion-user] h.264 pass through
Message-ID: <5cf0a432-3502-dbb9-7b32-2695c23dc...@gmail.com>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
The passthrough option
(https://rawgit.com/Motion-Project/motion/master/motion_config.html#ffmpeg_passthrough)
was really designed for rtsp/rtmp cameras that have a dual stream so
users can do the motion detection on the low resolution stream and
record events from the high resolution.
With a v4l2 device, the operating system is only going to allow one
stream at a time unless you get really creative which pretty much
eliminates the possibility of doing a dual stream.
You can of course try the v4l2 via the netcam option without the dual
streams and with passthrough, but I believe that there will be a high
degree of overhead associated with decoding the image which would negate
any benefit on the encoding size.
Assuming for the moment that you are not encountering USB bandwidth
limitations, I believe that the best performance would be obtained with
the 422 format, then mjpg and finally H264.? If you do have bandwidth
issues with the hub, then I'd recommend going with mjpg and only as a
last resort choosing the H264.
MrDave
On 1/24/2018 3:27 PM, Brian Mengel wrote:
> Greetings,
>
> I'm getting familiar with motion using an old Raspberry Pi Model B Rev
> 2 and a Logitech C920 web cam connected via a USB hub.? This is
> obviously not the ideal solution for high resolution/high frame rate
> video capture but it's what I had laying around. The C920 offers a
> h.264 video steam natively:
>
> pi@raspberrypi:/etc/motion $ v4l2-ctl --list-formats
> ioctl: VIDIOC_ENUM_FMT
> Index : 0
> Type : Video Capture
> Pixel Format: 'YUYV'
> Name : YUYV 4:2:2
>
> Index : 1
> Type : Video Capture
> Pixel Format: 'H264' (compressed)
> Name : H.264
>
> Index : 2
> Type : Video Capture
> Pixel Format: 'MJPG' (compressed)
> Name : Motion-JPEG
>
> After reading over the issues on git (#124 and #591) concerning h.264
> pass through I wanted to confirm that I understood things correctly
> before I worked on compiling from source in git.? If I work out of the
> master branch (assuming I can compile and run it) is there
> functionality there to perform motion detection and store the
> compressed h.264 video that the camera creates?
>
> I just want to make sure I understand what can be done with pass
> through before I really get going on this.
>
> TIA!
>
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>
>
> _______________________________________________
> Motion-user mailing list
> Motion-user@lists.sourceforge.net
> 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...
------------------------------
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
------------------------------
Subject: Digest Footer
_______________________________________________
Motion-user mailing list
Motion-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/motion-user
------------------------------
End of Motion-user Digest, Vol 139, Issue 9
*******************************************
