Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] Flushing while decoding , but need already decoded frames
Date: Fri, 24 May 2024 15:35:55 +0200
Message-ID: <GV1P250MB07379C7CB13729B43A091E1E8FF52@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <AM9PR02MB685053B47A4F8AB6EC6BA9CFBCF52@AM9PR02MB6850.eurprd02.prod.outlook.com>

Michael Henrik Bodenhoff via ffmpeg-devel:
> Hi Andrey ,
> 
> "when the decoder is set up to ignore B frames"
> 
> How do you do that ? 😲
> 
> We must have missed something while we tried using FFmpeg, because we couldn't find a way of telling the decoder to ignore B frames, we actually got so desperate that we considered if it was possible to modify the incoming encoded stream to make FFmpeg believe that the stream doesn't contain B frames ☹
> 

There is AVCodecContext.skip_frame; some decoders (not all, but e.g.
H.264) will skip frames based upon this value. But it does not affect
the decoder delay.
(There is also AV_CODEC_FLAG_LOW_DELAY, but this is honored by even less
decoders (only some old ones).)

- Andreas

_______________________________________________
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:[~2024-05-24 13:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-24  9:35 Michael Henrik Bodenhoff via ffmpeg-devel
2024-05-24 10:02 ` Andreas Rheinhardt
2024-05-24 11:39   ` Andrey Turkin
2024-05-24 12:20     ` Ronald S. Bultje
2024-05-24 12:52     ` Anton Khirnov
2024-05-24 13:16     ` Michael Henrik Bodenhoff via ffmpeg-devel
2024-05-24 13:35       ` Andreas Rheinhardt [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=GV1P250MB07379C7CB13729B43A091E1E8FF52@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM \
    --to=andreas.rheinhardt@outlook.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