From: Niklas Haas <ffmpeg@haasn.xyz> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [RFC]] swscale modernization proposal Date: Sat, 6 Jul 2024 14:32:32 +0200 Message-ID: <20240706143232.GD4446@haasn.xyz> (raw) In-Reply-To: <CA+anqdzqmHVQ9hHjnMXK-WHELVT7DqwTFZr_6j+yiwvFB+iSoQ@mail.gmail.com> On Sat, 06 Jul 2024 02:11:30 +0200 Hendrik Leppkes <h.leppkes@gmail.com> wrote: > On Fri, Jul 5, 2024 at 11:34 PM Michael Niedermayer > <michael@niedermayer.cc> wrote: > > > /** > > > * The exact interpretation of these quality presets depends on the backend > > > * used, but the backend-invariant common settings are derived as follows: > > > */ > > > enum AVScaleQuality { > > > AV_SCALE_ULTRAFAST = 1, /* no dither, nearest+nearest */ > > > AV_SCALE_SUPERFAST = 2, /* no dither, bilinear+nearest */ > > > AV_SCALE_VERYFAST = 3, /* no dither, bilinear+bilinear */ > > > AV_SCALE_FASTER = 4, /* bayer dither, bilinear+bilinear */ > > > AV_SCALE_FAST = 5, /* bayer dither, bicubic+bilinear */ > > > AV_SCALE_MEDIUM = 6, /* bayer dither, bicubic+bicubic */ > > > AV_SCALE_SLOW = 7, /* bayer dither, lanczos+bicubic */ > > > AV_SCALE_SLOWER = 8, /* full dither, lanczos+bicubic */ > > > AV_SCALE_VERYSLOW = 9, /* full dither, lanczos+lanczos */ > > > AV_SCALE_PLACEBO = 10, /* full dither, lanczos+lanczos */ > > > > I dont think its a good idea to hardcode dither and the "FIR" filter to the quality level in the API > > > > The entire point of presets is to have them provide a predefined set > of parameters, easy for users to pick one value, rather than a bunch. > And what a preset actually means should be documented. > How do you define "presets" if they don't hardcode a list of choices > for all the relevant options? > > Advanced settings exist for a user to select any particular detail, if > they so desire. One thought I had is to make the presets mechanism something separate, e.g. /* Explicitly defaults all options left as AVSCALE_*_AUTO */ avscale_default_options(AVScaleContext *ctx, int preset); But I think this would just represent an extra burden on the typical API user, who now needs to manually define this "int preset" with all available options, and call this function at init time, rather than getting it for free as part of the AVOptions exposed by AVScaleContext. > > - Hendrik > _______________________________________________ > 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:[~2024-07-06 12:32 UTC|newest] Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-22 13:13 Niklas Haas 2024-06-22 14:23 ` Andrew Sayers 2024-06-22 15:10 ` Niklas Haas 2024-06-22 19:52 ` Michael Niedermayer 2024-06-22 22:24 ` Niklas Haas 2024-06-23 17:27 ` Michael Niedermayer 2024-06-22 22:19 ` Vittorio Giovara 2024-06-22 22:39 ` Niklas Haas 2024-06-23 17:46 ` Michael Niedermayer 2024-06-23 19:00 ` Paul B Mahol 2024-06-23 17:57 ` James Almer 2024-06-23 18:40 ` Andrew Sayers 2024-06-24 14:33 ` Niklas Haas 2024-06-24 14:44 ` Vittorio Giovara 2024-06-25 15:31 ` Niklas Haas 2024-07-01 21:10 ` Stefano Sabatini 2024-06-29 7:41 ` Zhao Zhili 2024-06-29 10:58 ` Niklas Haas 2024-06-29 11:47 ` Niklas Haas 2024-06-29 12:35 ` Michael Niedermayer 2024-06-29 14:05 ` Niklas Haas 2024-06-29 14:11 ` James Almer 2024-06-30 6:25 ` Vittorio Giovara 2024-07-02 13:27 ` Niklas Haas 2024-07-03 13:25 ` Niklas Haas 2024-07-05 18:31 ` Niklas Haas 2024-07-05 21:34 ` Michael Niedermayer 2024-07-06 0:11 ` Hendrik Leppkes 2024-07-06 12:32 ` Niklas Haas [this message] 2024-07-06 16:42 ` Michael Niedermayer 2024-07-06 17:29 ` Hendrik Leppkes 2024-07-08 11:58 ` Ronald S. Bultje 2024-07-08 12:33 ` Andrew Sayers 2024-07-08 13:25 ` Ronald S. Bultje 2024-07-06 11:36 ` Andrew Sayers 2024-07-06 12:27 ` Niklas Haas
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=20240706143232.GD4446@haasn.xyz \ --to=ffmpeg@haasn.xyz \ --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