Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Lynne <dev@lynne.ee>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 00/72] Implement support for Vulkan multiplane images and video decoding
Date: Fri, 17 Feb 2023 12:52:21 +0100 (CET)
Message-ID: <NOUCxYe--3-9@lynne.ee> (raw)
In-Reply-To: <CAK+ULv780c=z_dig_FAhPJ2poZ8u2_QOnnPUmV3SSiYoaQZ+tw@mail.gmail.com-NOU29aV----9>

Feb 17, 2023, 12:05 by kierank@obe.tv:

> On Fri, 17 Feb 2023 at 09:09, Jean-Baptiste Kempf <jb@videolan.org> wrote:
>
>> Hello,
>>
>> On Fri, 17 Feb 2023, at 04:43, Lynne wrote:
>> > This small patchset mostly rewrites Vulkan to enable using multiplane
>> images,
>>
>> This is not small. We're talking about thousands of lines of code;
>>
>> And this changes numerous h264 and hevc headers, and adds callback to the
>> make AVHWAccel.
>>
>> And that is besides the full rewrite of some Vulkan files...
>>
>> This will take a long time to review.
>>
>
> I agree.
>

The codec changes are simple and separate, so it's not that bad to read.
There's no more than a 100 lines or so added to the H264 parser.
The 72 patch figure may be scary, but that's because I didn't want to
squash my vulkan changes behind large rewrite commits. Otherwise,
this would be a 30-commit patchset.

_______________________________________________
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-17 11: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 [this message]
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
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=NOUCxYe--3-9@lynne.ee \
    --to=dev@lynne.ee \
    --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