Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Tomas Härdin" <git@haerdin.se>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 3/3] lavc/speedhqdec: Set AV_PICTURE_TYPE_I
Date: Fri, 10 May 2024 14:31:12 +0200
Message-ID: <25d6c9a8ea00cbb2e9a2d1e8544f84ebd4a45d7a.camel@haerdin.se> (raw)
In-Reply-To: <4ba31c2b-2a25-4b98-8569-51eae38cbade@gmail.com>

ons 2024-05-08 klockan 17:06 -0300 skrev James Almer:
> On 5/8/2024 5:01 PM, Marton Balint wrote:
> > 
> > 
> > On Wed, 8 May 2024, Tomas Härdin wrote:
> > 
> > > 
> > > 
> > 
> > What suprises me is that pict_type and the keyframe flag is not set
> > already for decoding codecs with AV_CODEC_PROP_INTRA_ONLY flag. Is
> > this 
> > intentional or just nobody had the time to set it up to work
> > automatically?
> 
> For audio it's not always the case (See MLP/TrueHD). For video it
> might 
> with intra-only codecs, but at least with non intra-only codecs, an I
> frame is not necessarily a keyframe (See AV1).

Yes, IDR frames exist. We're talking about intra-only though.

I'll push this on Monday if there are no objections. We can adds some
logic for always setting key_frame and/or pict_type in the appropriate
place for intra-only codecs as a separate patch. That would allow us to
simplify all intra-only codecs as well, which would be nice

/Tomas
_______________________________________________
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-10 12:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-08 12:42 [FFmpeg-devel] [PATCH 1/3] lavc/speedhqdec: Add AV_CODEC_CAP_FRAME_THREADS Tomas Härdin
2024-05-08 12:42 ` [FFmpeg-devel] [PATCH 2/3] lavc/speedhqdec: Obey AVDISCARD_ALL Tomas Härdin
2024-05-08 12:43 ` [FFmpeg-devel] [PATCH 3/3] lavc/speedhqdec: Set AV_PICTURE_TYPE_I Tomas Härdin
2024-05-08 20:01   ` Marton Balint
2024-05-08 20:06     ` James Almer
2024-05-10 12:31       ` Tomas Härdin [this message]
2024-05-10 12:48         ` Andreas Rheinhardt
2024-05-11 23:07           ` Tomas Härdin
2024-05-13  6:57             ` Tomas Härdin
2024-05-08 12:46 ` [FFmpeg-devel] [PATCH 1/3] lavc/speedhqdec: Add AV_CODEC_CAP_FRAME_THREADS James Almer
2024-05-08 12:48   ` Tomas Härdin

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=25d6c9a8ea00cbb2e9a2d1e8544f84ebd4a45d7a.camel@haerdin.se \
    --to=git@haerdin.se \
    --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