From: "\"zhilizhao(赵志立)\"" <quinkblack@foxmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH v3 3/7] avcodec/mediacodecenc: use bsf to handle crop Date: Tue, 13 Dec 2022 11:20:23 +0800 Message-ID: <tencent_014DB0CF94D55DA710B890967D4D06A02507@qq.com> (raw) In-Reply-To: <93eb698946ae061c84db8ec9fce7f34a073c11b9.camel@haerdin.se> > On Dec 12, 2022, at 23:27, Tomas Härdin <git@haerdin.se> wrote: > > lör 2022-12-10 klockan 01:22 +0800 skrev Zhao Zhili: >> From: Zhao Zhili <zhilizhao@tencent.com> >> >> It's well known that mediacodec encoder requires 16x16 alignment. >> Use our bsf to fix the crop info. >> --- >> v3: don't change the dimension for AV_PIX_FMT_MEDIACODEC. It can have >> side effect. > > Looks like this silently crops? Is that really a good idea? We usually > don't do stuff like that. For example codecs that require even > dimensions complain loudly then fail. It’s reasonable to require even dimensions. Require dimensions aligned to 16 is uncommon. Everyone will complain why 1080x1920 doesn’t work. A lot of apps just use aligned dimensions. Users have no control on these apps. It’s not the same with FFmpeg, users (developer or not) can specify the dimension directly. If we don’t fix it, either: 1. Reject and fail directly. User complain why. 2. Accept and keep going. Sometimes it works, sometimes don’t. It depends on the device and get into a confused situation. I know there are getWidthAlignment()/getHeightAlignment() to get alignment info of codecs. The results are unreliable. The only reliable way I can find is don’t depends on those API and fix it by ourself. I’d like to know if there are better choices. > > /Tomas > > _______________________________________________ > 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". _______________________________________________ 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-12-13 3:20 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20221207093122.553668-1-quinkblack@foxmail.com> 2022-12-07 9:31 ` [FFmpeg-devel] [PATCH v2 1/7] avcodec/mediacodecenc: make each encoder has its own option Zhao Zhili 2022-12-07 9:31 ` [FFmpeg-devel] [PATCH v2 2/7] avcodec/mediacodecenc: add bitrate_mode option Zhao Zhili 2022-12-07 9:31 ` [FFmpeg-devel] [PATCH v2 3/7] avcodec/mediacodecenc: add level option Zhao Zhili 2022-12-07 9:31 ` [FFmpeg-devel] [PATCH v2 4/7] avcodec/mediacodecenc: use bsf to handle crop Zhao Zhili 2022-12-09 17:22 ` [FFmpeg-devel] [PATCH v3 3/7] " Zhao Zhili 2022-12-12 15:27 ` Tomas Härdin 2022-12-13 3:20 ` "zhilizhao(赵志立)" [this message] 2022-12-14 17:08 ` Tomas Härdin 2022-12-14 17:19 ` Tomas Härdin 2022-12-14 17:37 ` Zhao Zhili 2022-12-14 17:43 ` Zhao Zhili 2022-12-20 18:24 ` Tomas Härdin 2022-12-21 7:17 ` "zhilizhao(赵志立)" 2022-12-21 10:06 ` Tomas Härdin 2022-12-07 9:31 ` [FFmpeg-devel] [PATCH v2 5/7] avcodec/mediacodecenc: remove the strategy to create DTS Zhao Zhili 2022-12-12 15:28 ` Tomas Härdin 2022-12-13 2:55 ` "zhilizhao(赵志立)" 2022-12-14 17:31 ` Tomas Härdin 2023-01-04 10:16 ` Anton Khirnov 2023-01-04 11:31 ` [FFmpeg-devel] [Internet]Re: " "zhilizhao(赵志立)" 2023-01-04 13:59 ` Tomas Härdin 2023-01-04 14:46 ` Zhao Zhili 2023-01-04 15:15 ` Anton Khirnov 2023-01-04 16:12 ` Zhao Zhili 2023-01-05 8:07 ` Anton Khirnov 2022-12-07 9:31 ` [FFmpeg-devel] [PATCH v2 6/7] avcodec/mediacodecenc: add max-bframes support Zhao Zhili 2022-12-07 9:31 ` [FFmpeg-devel] [PATCH v2 7/7] avcodec/mediacodecenc: add pts_as_dts option Zhao Zhili
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=tencent_014DB0CF94D55DA710B890967D4D06A02507@qq.com \ --to=quinkblack@foxmail.com \ --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