Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Kieran Kunhya <kierank@obe.tv>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] libavcodec/mpeg12: Remove "fast" mode
Date: Mon, 30 Oct 2023 10:31:24 +0000
Message-ID: <CAK+ULv7RsXXR1hVf8xNUtftwEXJku-QoLW-S4yzFtyC_EKXD2g@mail.gmail.com> (raw)
In-Reply-To: <d42cb307-2bcc-45a7-98ee-8205d98b28ff@deadcode.eu>

On Mon, 30 Oct 2023 at 06:41, Matthias Dressel <lists.ffmpeg@deadcode.eu>
wrote:

> On 29.10.23 16:43, Kieran Kunhya wrote:
> > $subj as discussed at VDD
> >
> > Kieran
>
> IMHO the commit message should have contained some reason as to *why*
> this was removed.
> Now, someone looking at the log needs to find this patch on the ML, then
> follow the reference to find VDD meeting notes where they finally
> find... nothing. Because all the notes say is:
>
>  > We should remove it
>
> Unfortunately, I'm too late and it's pushed now, but maybe you can at
> least give a short explanation here on the ML?
>

"Fast" mode did some kind of out-of-spec VLC reading and dequant of MPEG-2
to allow faster decoding. This isn't really relevant in 2023 as MPEG-2
decoding is very fast in the official spec-compliant mode.

Kieran
_______________________________________________
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-10-30 10:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-29 15:43 Kieran Kunhya
2023-10-29 15:48 ` Lynne
2023-10-30  0:02   ` Leo Izen
2023-10-30  1:22     ` Lynne
2023-10-30  1:29       ` Leo Izen
2023-10-29 21:33 ` Michael Niedermayer
2023-10-30  6:40 ` Matthias Dressel
2023-10-30 10:31   ` Kieran Kunhya [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=CAK+ULv7RsXXR1hVf8xNUtftwEXJku-QoLW-S4yzFtyC_EKXD2g@mail.gmail.com \
    --to=kierank@obe.tv \
    --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