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 11:45:44 +0100 (CET)
Message-ID: <NOTyhjQ--3-9@lynne.ee> (raw)
In-Reply-To: <CA+anqdzm=tOcZnA--CGxBHCWpUjTy3B3ox5ejDOTO_zyzruF4g@mail.gmail.com>

Feb 17, 2023, 10:45 by h.leppkes@gmail.com:

> On Fri, Feb 17, 2023 at 10:09 AM 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 would agree, this set is too large to try to skirt it in just under
> the deadline of a new release, with the potential of needing to fix
> stuff later.
> Just have it land on master after the branch, and there is no time
> pressure to review it, or make numerous fixes on the release branch.
>

The code's been tested by a lot of folks already, and importantly,
passes the validation layers (with some warnings due to spec issues
that the workgroup agreed to fix).
The output is also conformant on all implementations.
All the code needs is some looking over to make sure I haven't done
something silly. Valgrind output is clean too.
It is a lot of code in terms of diff, but rather than reviewing each patch
individually, you should just try looking at the final files directly, that way,
you only have a few thousand lines to look at, rather than a few
thousand times twenty.
I've abstracted all the low-level Vulkan stuff from the decoding patchset,
so the output is high-level enough that anyone who's written hwaccels can
understand it.


> PS:
> Can you please send it as a proper patchset? Reviewing 72 patches off
> of one mail is not really fitting the workflow at all.
>

I'll do that.

_______________________________________________
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:[~2023-02-17 10:45 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 [this message]
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
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=NOTyhjQ--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