Re: [Motion-user] movie_passthrough- how does that interact with streams, encoding, etc

[Matt G. <mg...@gr...>]

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...@gr...> 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 <te...@pe... <mailto:te...@pe...>> 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
>> Mot...@li... <mailto:Mot...@li...>
>> https://lists.sourceforge.net/lists/listinfo/motion-user
>> https://motion-project.github.io/
>> 
>> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
>