Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Anton Khirnov <anton@khirnov.net>
To: Ffmpeg Devel <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 00/72] Implement support for Vulkan multiplane images and video decoding
Date: Mon, 20 Feb 2023 17:51:54 +0100
Message-ID: <167691191405.10789.11851144916124493591@lain.khirnov.net> (raw)
In-Reply-To: <NOST85t--3-9@lynne.ee>

Quoting Lynne (2023-02-17 04:43:50)
> From a9ae85816dfaa8791f974348825fc8ba9209423d Mon Sep 17 00:00:00 2001
> From: Lynne <dev@lynne.ee>
> Date: Thu, 10 Mar 2022 18:08:53 +0100
> Subject: [PATCH 05/72] h264_parser: expose idr_pic_id
> 
> Vulkan needs it.
> ---
>  libavcodec/h264_parse.h  | 1 +
>  libavcodec/h264_parser.c | 2 +-
>  2 files changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/libavcodec/h264_parse.h b/libavcodec/h264_parse.h
> index 4ee863df66..4ba0add4f2 100644
> --- a/libavcodec/h264_parse.h
> +++ b/libavcodec/h264_parse.h
> @@ -85,6 +85,7 @@ typedef struct H264POCContext {
>      int delta_poc_bottom;
>      int delta_poc[2];
>      int frame_num;
> +    int idr_pic_id;
>      int prev_poc_msb;           ///< poc_msb of the last reference pic for POC type 0
>      int prev_poc_lsb;           ///< poc_lsb of the last reference pic for POC type 0
>      int frame_num_offset;       ///< for POC type 2
> diff --git a/libavcodec/h264_parser.c b/libavcodec/h264_parser.c
> index 46134a1c48..1c330484c1 100644
> --- a/libavcodec/h264_parser.c
> +++ b/libavcodec/h264_parser.c
> @@ -432,7 +432,7 @@ static inline int parse_nal_units(AVCodecParserContext *s,
>              }
>  
>              if (nal.type == H264_NAL_IDR_SLICE)
> -                get_ue_golomb_long(&nal.gb); /* idr_pic_id */
> +                p->poc.idr_pic_id = get_ue_golomb_long(&nal.gb); /* idr_pic_id */

I don't see how a parser change can be related to anything vulkan.

-- 
Anton Khirnov
_______________________________________________
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-02-20 16:52 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-17  3:43 Lynne
2023-02-17  9:08 ` Jean-Baptiste Kempf
2023-02-17  9:45   ` Hendrik Leppkes
2023-02-17 10:45     ` Lynne
2023-02-17 11:04   ` Kieran Kunhya
     [not found]   ` <CAK+ULv780c=z_dig_FAhPJ2poZ8u2_QOnnPUmV3SSiYoaQZ+tw@mail.gmail.com-NOU29aV----9>
2023-02-17 11:52     ` Lynne
2023-02-17 15:45       ` Michael Niedermayer
2023-02-17 16:35         ` Lynne
2023-02-18 19:02 ` Michael Niedermayer
2023-02-19  0:08   ` Lynne
2023-02-19 15:40     ` Michael Niedermayer
2023-02-19 15:44       ` Kieran Kunhya
2023-02-19 16:53       ` Lynne
2023-02-19 16:56         ` Jean-Baptiste Kempf
2023-02-19 16:58           ` Lynne
2023-02-19 17:02             ` Jean-Baptiste Kempf
2023-02-19 19:32           ` Niklas Haas
2023-02-19 18:50         ` Michael Niedermayer
2023-02-19 19:02           ` Lynne
2023-02-19 19:44             ` Michael Niedermayer
2023-02-19 20:00               ` Lynne
2023-02-19 20:14                 ` Michael Niedermayer
     [not found]       ` <NOea74V--3-9@lynne.ee-NOeaB9K--R-9>
2023-02-19 16:57         ` Lynne
2023-02-19 17:36           ` Kieran Kunhya
2023-02-19 17:42             ` Kieran Kunhya
2023-02-19 18:46               ` Lynne
2023-02-19 21:59                 ` Kieran Kunhya
2023-02-19 23:50                   ` Neal Gompa
2023-02-20  5:13                     ` Jean-Baptiste Kempf
2023-02-20  9:18                     ` Hendrik Leppkes
2023-02-20 16:51 ` Anton Khirnov [this message]
2023-02-20 16:56 ` Anton Khirnov
2023-02-20 17:21 ` Anton Khirnov
2023-02-20 17:40 ` Anton Khirnov

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=167691191405.10789.11851144916124493591@lain.khirnov.net \
    --to=anton@khirnov.net \
    --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