Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Gyan Doshi <ffmpeg@gyani.pro>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v2] ffmpeg: add per-stream input option drop_changed
Date: Sun, 16 Mar 2025 23:39:49 +0530
Message-ID: <1ec268e9-4b2f-4d4a-97d8-fd7fa164612b@gyani.pro> (raw)
In-Reply-To: <b6b91339-c6b5-467e-8466-baed59553f84@gmail.com>



On 2025-03-16 11:12 pm, James Almer wrote:
> On 3/16/2025 4:18 AM, Gyan Doshi wrote:
>> This is a replacement in ffmpeg for the deprecated avcodec flag 
>> AV_CODEC_FLAG_DROPCHANGED.
>>
>> This option is meant to be used when the filtergraph should not be
>> reinited upon input parameter changes as that leads to loss of state
>> in the filtergraph potentially leading to broken or aborted output,
>> e.g. inserting of silence with first_pts specified in aresample.
>>
>> Generally useful to avoid corrupted yet decodable packets in live
>> streaming inputs.
>>
>> This option when enabled takes precedence over reinit_filters
>
> How does this differ from simply setting reinit_filter to false, if 
> what you want is the filtergraph to not be reinitialized?

av_buffersrc_add_frame_flags will return an error for all audio frames 
with differing parameters, as no filters are yet capable of handling 
them. ultimately leading to program exit.
Same is true for video frames barring a handful of filters like scale or 
idet ..etc

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

      reply	other threads:[~2025-03-16 18:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-16  7:18 Gyan Doshi
2025-03-16 17:42 ` James Almer
2025-03-16 18:09   ` Gyan Doshi [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=1ec268e9-4b2f-4d4a-97d8-fd7fa164612b@gyani.pro \
    --to=ffmpeg@gyani.pro \
    --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