Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avcodec/mpegvideo: Remove spec-incompliant inverse quantisation
Date: Thu, 9 Nov 2023 23:16:39 +0100
Message-ID: <20231109221639.GH3543730@pb2> (raw)
In-Reply-To: <15041633.235GFhGzie@basile.remlab.net>


[-- Attachment #1.1: Type: text/plain, Size: 1801 bytes --]

On Thu, Nov 09, 2023 at 10:52:19PM +0200, Rémi Denis-Courmont wrote:
> Le torstaina 9. marraskuuta 2023, 22.45.35 EET Alexander Strasser a écrit :
> > I can't see how the reason for the presence of code can be ultimately
> > defined objectively and non-arbitrary.
> 
> Ultimately, this was discussed and decided in a meeting, which Michael 
> attended (albeit remotely) and for which meeting notes were published.

maybe i misremember as i was a bit sick that day
but there are 2 pieces of code
there was the "fast mode code" that i thought was discussed this is
disabled by default and we aggreed to remove it

the change here is about the default code path so this is very different
it will affect users with default options.

I do not remember this was discussed but its quite possible people
had a different interpretation what the words meant that where said.

This definitly should be tested before its applied. Whoever the burden falls
on is not my argument but ATM i have many things to do so i will not be able
to test this in the next days


> 
> That being the case, I don't see why Andreas should have to perform extensive 
> testing and write extensive justification. He could have done and that would 
> have been nice, but that is all.

I never meant that there should be extensive testing
but teh removal of a optimization from the default codepath should be
tested.
Also about spec non compliance, if this was so bad, being in the default
path there would be bug reports so iam a bit sceptic. not saying it
shouldnt be removed just saying we should look before removing it

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

I have often repented speaking, but never of holding my tongue.
-- Xenocrates

[-- 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".

      reply	other threads:[~2023-11-09 22:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-30 13:11 Andreas Rheinhardt
2023-10-30 18:40 ` Kieran Kunhya
2023-10-31  8:40 ` Michael Niedermayer
2023-11-08 11:40   ` Anton Khirnov
2023-11-08 20:55     ` Alexander Strasser
2023-11-08 22:58       ` Vittorio Giovara
2023-11-09 20:55         ` Alexander Strasser
2023-11-09 10:13       ` Anton Khirnov
2023-11-09 20:45         ` Alexander Strasser
2023-11-09 20:52           ` Rémi Denis-Courmont
2023-11-09 22:16             ` 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=20231109221639.GH3543730@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