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] [FFmpeg-cvslog] ffmpeg: add per-stream input option drop_changed
Date: Mon, 24 Mar 2025 10:31:17 -0300
Message-ID: <b3d78f48-7f8b-4b8c-9361-ae5407fb09b6@gmail.com> (raw)
In-Reply-To: <e8c1f28c-0117-4fe4-ab67-2d5e92482062@gyani.pro>


[-- Attachment #1.1.1: Type: text/plain, Size: 2197 bytes --]

On 3/24/2025 10:29 AM, Gyan Doshi wrote:
> 
> 
> On 2025-03-24 06:42 pm, James Almer wrote:
>> On 3/24/2025 9:31 AM, Martin Storsjö wrote:
>>> On Mon, 24 Mar 2025, Gyan Doshi wrote:
>>>
>>>> ffmpeg | branch: master | Gyan Doshi <ffmpeg@gyani.pro> | Sat Mar 15 
>>>> 16:51:05 2025 +0530| [cbbc927a67f142a02bfc5d047c03587599ee5b55] | 
>>>> committer: Gyan Doshi
>>>>
>>>> ffmpeg: add per-stream input option drop_changed
>>>>
>>>> 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
>>>>
>>>>> http://git.videolan.org/gitweb.cgi/ffmpeg.git/? 
>>>>> a=commit;h=cbbc927a67f142a02bfc5d047c03587599ee5b55
>>>> ---
>>>
>>> This change is causing failed fate tests in many different 
>>> configurations; I'm seeing null pointer dereferences and similar, on 
>>> both msvc/arm, msvc/x86_32, macos/aarch64. Please investigate.
>>
>> I pushed a quick fix, but nonetheless, the log message in question is 
>> being printed for one stream (the last one handled by the scheduler) 
>> rather than every stream where the option was the for, so it needs to 
>> be properly done still.
> 
> Thanks. FATE passed here and on Patchwork as well.
> 
> If ifp can be NULL, how come this pre-existing line above,
> 
>            if (ifp->type_src == AVMEDIA_TYPE_SUBTITLE) {
> 
> didn't lead to FATE failures?

The goto read_frames before ifp is ever set.

> 
> Re: log, the final log is printed for each stream:
> 
> e.g., from the log of a command with option applied to aud and vid,
> 
> [af#0:1 @ 000001b4af668380] Total changed input frames dropped : 234
> [vf#0:0 @ 000001b4af3e0540] Total changed input frames dropped : 149

Oh, i see.


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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-24 13:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250324105110.35B08412755@natalya.videolan.org>
2025-03-24 12:31 ` Martin Storsjö
2025-03-24 12:40   ` softworkz .
2025-03-24 13:12   ` James Almer
2025-03-24 13:29     ` Gyan Doshi
2025-03-24 13:31       ` 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=b3d78f48-7f8b-4b8c-9361-ae5407fb09b6@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