On Fri, Mar 25, 2022 at 10:40 PM wrote:
>
> Oops, accidentally submitted with the wrong title so not in the right thread.
> Is submitted with the right one now.
>
> A re-submit of a re-base of a formerly proposed patch to align with ffmpeg
> github
> commit 8ae15b565533944d042d3caf25f7262e002e895
Oops, accidentally submitted with the wrong title so not in the right thread.
Is submitted with the right one now.
A re-submit of a re-base of a formerly proposed patch to align with ffmpeg
github
commit 8ae15b565533944d042d3caf25f7262e002e8953
as at 2022.03.26 ACST, after ffmpeg changes overl
Hello.
A re-submit of a re-base of a formerly proposed patch to align with ffmpeg
github
commit 8ae15b565533944d042d3caf25f7262e002e8953
at 2022.03.26 ACST, after changes overlapped the formerly proposed patch.
Add commandline options to v4l2_m2m_enc (h264_v4l2m2m only)
and use those to config
On Sun, 13 Mar 2022 at 18:34, wrote:
> Well, let's try to submit a patch and see how it fares.
>
>
> Add commandline options to v4l2_m2m_enc (h264_v4l2m2m only)
> and use those to configure options for the h264_v4l2m2m encoder.
> Uses AVOption options to filter for valid options per v4l2 spec.
>
Well, let's try to submit a patch and see how it fares.
Add commandline options to v4l2_m2m_enc (h264_v4l2m2m only)
and use those to configure options for the h264_v4l2m2m encoder.
Uses AVOption options to filter for valid options per v4l2 spec.
For h264 it adds spec-compliant:
-profile (high is
