You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According the Nvidia GPU matrix the Quadro P620 has one NVENC unit and supports 8 concurrent streams. It also supports everything except AV1.
Do I need to use a different version/build of FFMPEG? Is there an issue with the way MotionEye/Motion is invoking it? Is this a known issue, and if so, is there a fix?
The text was updated successfully, but these errors were encountered:
It sounds like the format for the presets was changed some time ago and 'ultrafast' is no longer a thing (in trying to look at ffmpeg's git logs, it seems like it was removed some time ago).
Is there a way for MotionEye to override the options Motion uses when it calls ffmpeg?
If so, can that be handled automatically int he future for the h.264 nvenc option?
The root cause of the problem is motion. It's not set up to work with nvenc.
I've been hacking on Motion with a local build to get it working and have acceptable quality.
I'll go raise the issue over in the Motion repo.
Motion and MotionEyeversion info:
Here is the output from my nvidia-smi command:
FFMPEG version:
More info from FFMPEG:
And here is a log snippet from MotionEye when motion is triggered:
According the Nvidia GPU matrix the Quadro P620 has one NVENC unit and supports 8 concurrent streams. It also supports everything except AV1.
Do I need to use a different version/build of FFMPEG? Is there an issue with the way MotionEye/Motion is invoking it? Is this a known issue, and if so, is there a fix?
The text was updated successfully, but these errors were encountered: