From: Mark Thompson <sw@jkqxz.net>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avcodec/mfenc: expose more properties of the media foundation encoder
Date: Mon, 1 Apr 2024 19:55:55 +0100
Message-ID: <52799ab5-74f5-469b-a866-bbd94ba332dd@jkqxz.net> (raw)
In-Reply-To: <CAGk+fLE6dQQNJBMbUxE+=YvtgDQ1TJ-WBm7jco6yvvtebwzRug@mail.gmail.com>
On 01/04/2024 17:25, Mark Samuelson wrote:
> On Mon, Apr 1, 2024 at 10:06 AM Mark Thompson <sw@jkqxz.net> wrote:
>
>>> On 28/03/2024 12:34, Mark Samuelson wrote:
>>>> Thank you for the notes, here is a new patch that incorporates your
>> suggestions. You are right, the default value of 12 for gop_size is
>> suprising, I didn't know about it before now.
>>>>
>>>> ---
>>>> libavcodec/mf_utils.h | 5 +++++
>>>> libavcodec/mfenc.c | 33 +++++++++++++++++++++++++++------
>>>> 2 files changed, 32 insertions(+), 6 deletions(-)
>>>
>>> Patch looks good.
>>>
>>> I did a bit of testing with the Microsoft H.264 MFT: GOP size and
>> compression level work as expected, and VBV parameters seem to be doing
>> something sensible.
>>>
>>> Under what conditions are you expecting global_quality ->
>> AVEncVideoEncodeQP to do anything, though? When I set it alone the output
>> was always identical regardless of what value I set > it to. (Including
>> with "-rate_control quality".)
>>>
>>> Thanks,
>>>
>>> - Mark
>>
>
> I have also had issues making the Media Foundation encoder respect that
> value. I put it in there so that I could easily test it, because I was
> having issues with the existing opt_enc_quality -> AVEncCommonQuality. I
> figured it was better to leave it in so people can experiment with it.
Fair, these options are not particularly consistent between different encoder MFT implementations.
I will apply this patch tomorrow unless there are any more comments on it.
Thanks,
- Mark
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2024-04-01 18:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 19:25 Mark Samuelson
2024-03-26 20:57 ` Mark Thompson
2024-03-28 12:34 ` Mark Samuelson
2024-04-01 15:06 ` Mark Thompson
2024-04-01 16:25 ` Mark Samuelson
2024-04-01 18:55 ` Mark Thompson [this message]
2024-04-02 20:54 ` Mark Thompson
2024-03-27 11:30 ` Stefano Sabatini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52799ab5-74f5-469b-a866-bbd94ba332dd@jkqxz.net \
--to=sw@jkqxz.net \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git