From: Gyan Doshi <ffmpeg@gyani.pro>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avcodec/mfenc: set frame size for audio encoders.
Date: Sat, 18 Jun 2022 13:58:38 +0530
Message-ID: <e7f2ee0d-dce4-59a5-8fd7-40cc6ce6b0f3@gyani.pro> (raw)
In-Reply-To: <DB6PR0101MB22145AC25F237B265D8DAEDE8FAE9@DB6PR0101MB2214.eurprd01.prod.exchangelabs.com>
On 2022-06-18 12:19 pm, Andreas Rheinhardt wrote:
> Gyan Doshi:
>> Default avctx->frame_size is 0 which leads to init failure for
>> audio MediaFoundation encoders.
>> ---
>> libavcodec/mfenc.c | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/libavcodec/mfenc.c b/libavcodec/mfenc.c
>> index 13ed7b3e11..ff9ffe4827 100644
>> --- a/libavcodec/mfenc.c
>> +++ b/libavcodec/mfenc.c
>> @@ -1066,6 +1066,9 @@ static int mf_init_encoder(AVCodecContext *avctx)
>>
>> c->main_subtype = *subtype;
>>
>> + if (c->is_audio && !avctx->frame_size)
>> + avctx->frame_size = 1024;
>> +
>> if ((ret = mf_create(avctx, &c->functions, &c->mft, avctx->codec, use_hw)) < 0)
>> return ret;
>>
> 1. You forgot to mention the ticket that this is supposed to fix; you
> should also add that this a regression and the commit
> (827d6fe73d2f5472c1c2128eb14fab6a4db29032) that supposedly introduced
> the regression (if this is indeed true).
I initially became aware due to a user query. Saw ticket later. Will
add details.
> 2. Where does this number come from (apart from the user-provided error
> message)? How did it work before said commit?
> (It seems that frame_size was unset before this commit, but did it
> somehow just not matter?)
The MF encoders accept any number of samples per frame. They reframe as
necessary for DSP.
I choose 1024 as its the most common frame size emitted (PCM/AAC decoders).
Regards,
Gyan
_______________________________________________
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:[~2022-06-18 8:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 5:44 Gyan Doshi
2022-06-18 4:01 ` Gyan Doshi
2022-06-18 6:49 ` Andreas Rheinhardt
2022-06-18 8:28 ` Gyan Doshi [this message]
2022-06-18 15:05 ` Anton Khirnov
2022-06-19 9:02 ` [FFmpeg-devel] [PATCH v2] avcodec/mfenc: set variable frame size flag Gyan Doshi
2022-06-19 9:18 ` Andreas Rheinhardt
2022-06-19 9:24 ` Andreas Rheinhardt
2022-06-19 10:06 ` Gyan Doshi
2022-06-19 10:10 ` Gyan Doshi
2022-06-19 10:12 ` Andreas Rheinhardt
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=e7f2ee0d-dce4-59a5-8fd7-40cc6ce6b0f3@gyani.pro \
--to=ffmpeg@gyani.pro \
--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