From: Richard Kern <kernrj@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] libavcodec/videotoolboxenc.c: add option to hevc encoder to prioritize speed. Date: Sun, 1 May 2022 14:25:50 -0400 Message-ID: <4D6BE20A-02C3-420E-B666-D8F92B7EE6ED@gmail.com> (raw) In-Reply-To: <ACD711DC-42AF-44F7-ADB1-C7EB2935BF86@lisanet.de> [-- Attachment #1: Type: text/plain, Size: 1193 bytes --] > On May 1, 2022, at 1:31 PM, Simone Karin Lehmann <simone@lisanet.de> wrote: > > Hi, > > may I kindly ask you to check, if this patch could now be applied? I’ll look at it today. > > Regards > Simone > > Von meinem iPad gesendet > >> Am 25.04.2022 um 22:33 schrieb Simone Karin Lehmann <simone@lisanet.de>: >> >> >> >>>>> Am 25.04.2022 um 21:14 schrieb Rick Kern <kernrj@gmail.com>: >>>>> >>>>> >>>>> { "a53cc", "Use A53 Closed Captions (if available)", OFFSET(a53_cc), >>>>> AV_OPT_TYPE_BOOL, {.i64 = 1}, 0, 1, VE }, >>>>> + { "prio_speed", "prioritize encoding speed", OFFSET(prio_speed), >>>>> AV_OPT_TYPE_BOOL, { .i64 = 0 }, 0, 1, VE }, >>>>> >>> It might be simpler to make the default value of prio_speed -1, and set >>> this property on the encoder session only when it's non-negative. Then we >>> won't need to worry about the default value changing for different codecs >>> or different OS versions. It could also be moved into COMMON_OPTIONS in >>> this case. >> >> oh yes, that’s way better. I didn’t think of that in the first place. Thanks for the hint. >> >> Here’s the modified patch >> >> Simone >> [-- Attachment #2: 0001-add-options-to-h264-hevc-and-prores-encoders-to-prio.patch --] [-- Type: application/octet-stream, Size: 3289 bytes --] [-- Attachment #3: Type: text/plain, Size: 541 bytes --] >> >> _______________________________________________ >> 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". [-- Attachment #4: Type: text/plain, Size: 251 bytes --] _______________________________________________ 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-05-01 18:26 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <80886934-2099-4FE0-A95D-F9B6658F777F@lisanet.de> 2022-04-14 6:48 ` Simone Karin Lehmann 2022-04-14 8:13 ` Thilo Borgmann 2022-04-21 15:42 ` Simone Karin Lehmann 2022-04-22 16:24 ` Andreas Rheinhardt 2022-04-22 16:52 ` Thilo Borgmann 2022-04-23 12:31 ` Simone Karin Lehmann 2022-04-23 15:07 ` Thilo Borgmann 2022-04-23 15:42 ` Simone Karin Lehmann 2022-04-23 19:56 ` Thilo Borgmann 2022-04-23 20:51 ` Simone Karin Lehmann 2022-04-24 10:10 ` Thilo Borgmann 2022-04-25 19:14 ` Rick Kern 2022-04-25 20:33 ` Simone Karin Lehmann 2022-05-01 17:31 ` Simone Karin Lehmann 2022-05-01 18:25 ` Richard Kern [this message] 2022-05-01 19:11 ` Simone Karin Lehmann 2022-05-02 15:18 ` Rick Kern
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=4D6BE20A-02C3-420E-B666-D8F92B7EE6ED@gmail.com \ --to=kernrj@gmail.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