Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] lavc: deprecate AV_CODEC_FLAG_DROPCHANGED
Date: Wed, 12 Jul 2023 10:21:30 -0300
Message-ID: <5c3d0fdd-eae3-5e94-34d1-2d44a63c521f@gmail.com> (raw)
In-Reply-To: <90db5f3d-d24f-3c13-ac17-90a540003438@gyani.pro>

On 7/12/2023 10:14 AM, Gyan Doshi wrote:
> 
> 
> On 2023-07-12 06:12 pm, James Almer wrote:
>> On 7/9/2023 9:57 AM, Anton Khirnov wrote:
>>> This decoding flag makes decoders drop all frames after a parameter
>>> change, but what exactly constitutes a parameter change is not well
>>> defined and will typically depend on the exact use case.
>>> This functionality then does not belong in libavcodec, but rather in
>>> user code
> 
> NAK.
> 
> The applicable parameters are well defined as set by the implementation.

The implementation defined its own interpretation of what constitutes a 
parameter change, yes, but callers may have their own interpretations 
too. The result is they either don't set this flag, or set it but still 
manually check every frame for other parameters.

> They are whatever leads to a change in the size of the decoded frame 
> payload or the layout/semantics of the elemental unit in a decoded 
> frame, so width, height, pixel format, sample format/size, 
> interleaving..etc

You give pixel format as an example, which would include a change from 
yuv to a yuvj pseudo format. What about decoders that export yuv + 
color_range mpeg and then yuv + color_range jpeg? This implementation 
will not consider that a parameter change, despite being practically the 
same scenario.
Once the yuvj formats are removed, this will be true for all decoders. 
And suddenly starting to check for color_range would be a change in 
implementation here.

This is definitely something that should be left to the caller. They get 
a frame out of the decoder, they decide if they want to drop it.

> 
> Regards,
> Gyan
> 
> _______________________________________________
> 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".

  reply	other threads:[~2023-07-12 13:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-09 12:57 Anton Khirnov
2023-07-12 12:42 ` James Almer
2023-07-12 13:14   ` Gyan Doshi
2023-07-12 13:21     ` James Almer [this message]
2023-07-12 13:31       ` Gyan Doshi
2023-07-12 13:44         ` Anton Khirnov
2023-07-13 19:20           ` Gyan Doshi
2023-07-13 20:57             ` Anton Khirnov
2023-07-13 10:56 ` Anton Khirnov

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=5c3d0fdd-eae3-5e94-34d1-2d44a63c521f@gmail.com \
    --to=jamrial@gmail.com \
    --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