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 1/2] lavc/internal: add skip_samples2 field
Date: Thu, 19 Oct 2023 09:50:39 -0300
Message-ID: <c45391a8-f8fa-466b-ace0-9d16c5afb64a@gmail.com> (raw)
In-Reply-To: <169770476600.32606.17075970689497459215@lain.khirnov.net>

On 10/19/2023 5:39 AM, Anton Khirnov wrote:
> Current interaction between AV_FRAME_DATA_SKIP_SAMPLES and
> AVCodecContext.skip_samples seems unncecessarily complicated to me and
> you're just making it worse.
> 
> Is there any reason we can't drop AVCodecContext.skip_samples entirely
> and signal it purely through side data? Then decoders could fully
> control everything they wish by modifying side data on output frames.

Given that now coded_side_data is fully implemented for decoding and 
encoding, including getting elements from the container, it's probably a 
good idea to do that.
_______________________________________________
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".

      parent reply	other threads:[~2023-10-19 12:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-19  2:37 Lynne
     [not found] ` <Nh4mqjI--3-9@lynne.ee-Nh4muoe----9>
2023-10-19  2:38   ` [FFmpeg-devel] [PATCH 2/2] aacdec: padding skip improvements Lynne
2023-10-19  8:40     ` Anton Khirnov
2023-10-19 12:48       ` Lynne
2023-10-19 15:48         ` Anton Khirnov
     [not found]   ` <Nh4nBk8--3-9@lynne.ee-Nh4nEdF----9>
2023-10-19  2:39     ` Lynne
2023-10-19  8:39 ` [FFmpeg-devel] [PATCH 1/2] lavc/internal: add skip_samples2 field Anton Khirnov
2023-10-19 12:49   ` Lynne
2023-10-19 15:50     ` Anton Khirnov
2023-10-19 12:50   ` James Almer [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=c45391a8-f8fa-466b-ace0-9d16c5afb64a@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