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: Can motion use GPU? (MrDave)
----------------------------------------------------------------------
Message: 1
Date: Sun, 13 Sep 2020 00:50:20 -0600
From: MrDave <[email protected]>
To: [email protected]
Subject: Re: [Motion-user] Can motion use GPU?
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Its an easy question but the answer is a bit complicated....
Generally, the answer to the question is "no" there isn't any direct
support for hardware decoding.? However, for certain cameras and
platforms, there is an option to specify a specific decoder and encoder
that could be built into ffmpeg.? Its been observed however that this is
primarily only a benefit for those with PI's and allows them to specify
the ffmpeg hardware OMX encoders/decoders.? The other HW decoders for
regular desktop platforms such as VAAPI, QSV, VDPAU, etc, all seem to
require unique coding that the regular Motion program does not have
built in.? (There is at least one fork that illustrates how to implement
VAAPI but those revisions are not in the main Motion code/releases).
Previous discussions on the mailing list indicated possible workarounds
to get it implemented using a v4l2 loopback device. This is virtually
identical to the example in the Motion guide at
https://motion-project.github.io/motion_config.html#basic_setup_static
but instead of just a static file, specify the IP camera and HW decoding.
For each of the above options, it will usually be required to build
ffmpeg from source and specify all the HW options that are applicable to
your computer.
Finally, I'd comment that the "standard" option to reduce CPU for your
situation is use the netcam_url, netcam_highres and movie_passthrough
options.? I believe that generally this method is going to result in
lower CPU usage than just using the higher resolution streams alone with
HW decoding.
MrDave
On 9/12/2020 6:41 PM, rmbusy wrote:
> Supposedly if you can get ffmpeg to use the GPU, then yes, as motion
> uses ffmpeg.? You need to research for your hardware, how to build
> ffmpeg for that.
>
>
> --
> Rob.
>
>
> On 9/12/20 5:15 PM, Harlan Daneker wrote:
>> I'm not an expert, but are you using extpipe, if not I believe motion
>> only uses 1 thread.
>>
>> On Sat, Sep 12, 2020 at 2:59 PM Amos Shapira <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>> Hi,
>>
>> I have Motion (with MotionEye) installed on Ubuntu?connected to 4
>> 6MP IP cameras and it can't handle the load.
>>
>> I'm thinking of buying stronger hardware for it and was wondering
>> whether it could take advantage of a GPU.
>>
>> Can it?
>> What would be required to make it do that?
>>
>> Thanks
>>
>> --Amos
>>
>> _______________________________________________
>> Motion-user mailing list
>> [email protected]
>> <mailto:[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 171, Issue 2
*******************************************
