From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] v2: lavu/pixdesc: favour formats where depth and subsampling exactly match Date: Thu, 15 Sep 2022 20:00:07 +0200 Message-ID: <20220915180007.GR2088045@pb2> (raw) In-Reply-To: <20220914154304.64a99103@fido7> [-- Attachment #1.1: Type: text/plain, Size: 1257 bytes --] On Wed, Sep 14, 2022 at 03:43:04PM -0700, Philip Langdale wrote: > On Wed, 14 Sep 2022 23:08:16 +0200 > Michael Niedermayer <michael@niedermayer.cc> wrote: [...] > > > + // Favour formats where bit depth exactly matches. If > > > all other > > > + // scoring is equal, we'd rather use the bit depth > > > that most closely > > > + // matches the source. > > > > ok > > > > > > > + loss |= FF_LOSS_EXCESS_DEPTH; > > > + score -= 1 << -depth_delta; > > > > but does that do that ? > > a 1bpp -> 16bpp has a considerable -depth_delta > > > > do we need the << at all ? > > The idea here is to have the scoring reflect the gap. Are you saying > you'd just apply the depth_delta as-is (just a small number 1 <= n <= > 15)? yes it makes this less constrained with the shifts there are only 32 distinct values with a int I presume the shifts where there to give the loss some material sense as in PSNR or SAD or something like that, 8 bits output having 4 times worse precission than 10 bit for example. thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB It is what and why we do it that matters, not just one of them. [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 195 bytes --] [-- Attachment #2: 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".
prev parent reply other threads:[~2022-09-15 18:00 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-10 19:23 Philip Langdale 2022-09-14 21:08 ` Michael Niedermayer 2022-09-14 22:43 ` Philip Langdale 2022-09-15 18:00 ` Michael Niedermayer [this message]
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=20220915180007.GR2088045@pb2 \ --to=michael@niedermayer.cc \ --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