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: movie_passthrough- how does that interact with streams,
encoding, etc (Matt Grob)
2. movie_passthrough: Possible on RPI camera? (Matt Grob)
3. Re: movie_passthrough- how does that interact with streams,
encoding, etc (Matt Grob)
----------------------------------------------------------------------
Message: 1
Date: Sun, 8 Sep 2019 10:02:52 -0700
From: Matt Grob <mg...@grobfamily.org>
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] movie_passthrough- how does that interact
with streams, encoding, etc
Message-ID: <fb0f773e-a7a1-4790-b91b-9bc60e0c6...@grobfamily.org>
Content-Type: text/plain; charset="utf-8"
I?m also interested in the movie_passthrough feature.
I believe the answer to Ted?s question below is high res capture does not use
the movie_codec parameter. That?s I think part of the idea - free the CPU from
having to do the encoding of the higher res stream. Instead the captured movie
is created directly from the frames sent from the camera.
Disclaimer: just starting to learn this feature. Please correct/clarify as
needed :)
Here is the documentation on the feature:
https://motion-project.github.io/motion_config.html#movie_passthrough
<https://motion-project.github.io/motion_config.html#movie_passthrough>
> On Mar 8, 2019, at 12:31 PM, Ted Timmons <t...@perljam.net> wrote:
>
> Hello, long time user (2003ish). I'm just starting to play with the
> movie_passthrough option, using a rtsp source.
>
> Does this ignore/bypass "movie_codec"? I see that the "shape" of the
> saved file looks different than if I use "ffmpeg -i" to grab it
> straight off the rtsp stream.
>
> Here's a file out of motion:
> Duration: 00:00:17.31, start: 0.066000, bitrate: 869 kb/s
> Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p,
> 1280x720, 868 kb/s, 15.49 fps, 17.92 tbr, 90k tbn, 180k tbc (default)
> Metadata:
> handler_name : VideoHandler
>
> Here's the rtsp stream:
> Input #0, rtsp, from 'rtsp://192.168.0.31:554/live/ch0':
> Duration: N/A, start: 0.467000, bitrate: N/A
> Stream #0:0: Video: h264 (High), yuv420p(progressive), 1280x720,
> 15.17 tbr, 90k tbn, 180k tbc
> Stream #0:1: Audio: aac (LC), 16000 Hz, mono, fltp
> Stream #0:2: Data: none
>
> It looks like perhaps it is directly saving that first stream but
> discarding my other two streams.
>
>
> _______________________________________________
> 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...
------------------------------
Message: 2
Date: Sun, 8 Sep 2019 10:06:27 -0700
From: Matt Grob <mg...@grobfamily.org>
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: [Motion-user] movie_passthrough: Possible on RPI camera?
Message-ID: <6f2f6a7c-aeeb-463a-ab2c-80df04fc3...@grobfamily.org>
Content-Type: text/plain; charset="utf-8"
Wondering if it?s possible to use the motion_passthrough feature on a raspberry
pi camera? (Meaning the actual RPI camera, not just any camera attached to an
RPI)
The documentation says it works with ?some V4L2 cameras? and the netcam_url
parameter must be used - so that makes me feel it?s not possible - but not
really sure.
Here?s the documentation:
https://motion-project.github.io/motion_config.html#movie_passthrough
<https://motion-project.github.io/motion_config.html#movie_passthrough>
Thanks for any info
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 3
Date: Sun, 8 Sep 2019 10:08:24 -0700
From: Matt Grob <mg...@grobfamily.org>
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] movie_passthrough- how does that interact
with streams, encoding, etc
Message-ID: <82ace280-f7a5-474d-87ca-2fc72a14c...@grobfamily.org>
Content-Type: text/plain; charset="utf-8"
I believe here is the answer to Ted?s question from the feature documentation:
?..when motion is detected, the high resolution images will be captured and
processed into the movie file without going through the decode/encode
processing."
> On Sep 8, 2019, at 10:02 AM, Matt Grob <mg...@grobfamily.org> wrote:
>
>
> I?m also interested in the movie_passthrough feature.
>
> I believe the answer to Ted?s question below is high res capture does not use
> the movie_codec parameter. That?s I think part of the idea - free the CPU
> from having to do the encoding of the higher res stream. Instead the
> captured movie is created directly from the frames sent from the camera.
>
> Disclaimer: just starting to learn this feature. Please correct/clarify as
> needed :)
>
> Here is the documentation on the feature:
> https://motion-project.github.io/motion_config.html#movie_passthrough
> <https://motion-project.github.io/motion_config.html#movie_passthrough>
>
>
>
>
>
>
>
>> On Mar 8, 2019, at 12:31 PM, Ted Timmons <t...@perljam.net
>> <mailto:t...@perljam.net>> wrote:
>>
>> Hello, long time user (2003ish). I'm just starting to play with the
>> movie_passthrough option, using a rtsp source.
>>
>> Does this ignore/bypass "movie_codec"? I see that the "shape" of the
>> saved file looks different than if I use "ffmpeg -i" to grab it
>> straight off the rtsp stream.
>>
>> Here's a file out of motion:
>> Duration: 00:00:17.31, start: 0.066000, bitrate: 869 kb/s
>> Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p,
>> 1280x720, 868 kb/s, 15.49 fps, 17.92 tbr, 90k tbn, 180k tbc (default)
>> Metadata:
>> handler_name : VideoHandler
>>
>> Here's the rtsp stream:
>> Input #0, rtsp, from 'rtsp://192.168.0.31:554/live/ch0':
>> <rtsp://192.168.0.31:554/live/ch0':>
>> Duration: N/A, start: 0.467000, bitrate: N/A
>> Stream #0:0: Video: h264 (High), yuv420p(progressive), 1280x720,
>> 15.17 tbr, 90k tbn, 180k tbc
>> Stream #0:1: Audio: aac (LC), 16000 Hz, mono, fltp
>> Stream #0:2: Data: none
>>
>> It looks like perhaps it is directly saving that first stream but
>> discarding my other two streams.
>>
>>
>> _______________________________________________
>> Motion-user mailing list
>> Motion-user@lists.sourceforge.net <mailto: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...
------------------------------
------------------------------
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 159, Issue 8
*******************************************
