Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "J. Dekker" <jdek@itanimul.li>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avcodec/er: remove check for fields
Date: Thu, 23 Mar 2023 12:15:04 +0100
Message-ID: <9FA8D55E-504A-40FA-9B8E-8E3514517A54@itanimul.li> (raw)
In-Reply-To: <20230323100555.GM375355@pb2>

On 23 Mar 2023, at 11:05, Michael Niedermayer wrote:
> On Thu, Mar 23, 2023 at 10:18:29AM +0100, J. Dekker wrote:
>> This change on its own is almost certainly not correct; however, in
>> testing many samples show notable improvement.
>> ---
>
> do you plan to implement support for field based error concealment ?
> field based content was rare in what i watched when i wrote this so
> i didnt bother originally implementing it IIRC

I can send you interlaced samples if you would like. I had planned on doing improvements for field/mbaff error concealment myself in the future. There still seems to be a lot of field based content in the wild whilst it is being phased out.

Here's the comparison of the change above:
https://0x1.st/f0.mp4
https://0x1.st/fe.mp4
https://0x1.st/fZ.mp4
https://0x1.st/fv.mp4

-- 
J. Dekker
_______________________________________________
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-03-23 11:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-23  9:18 J. Dekker
2023-03-23 10:05 ` Michael Niedermayer
2023-03-23 11:15   ` J. Dekker [this message]
2023-03-23 11:55     ` Michael Niedermayer
2023-03-27  6:56 ` J. Dekker
2023-04-02 23:53   ` Michael Niedermayer

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=9FA8D55E-504A-40FA-9B8E-8E3514517A54@itanimul.li \
    --to=jdek@itanimul.li \
    --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