From: Michael Niedermayer <michael@niedermayer.cc>
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 16:45:01 +0100
Message-ID: <20230217154501.GA4538@pb2> (raw)
In-Reply-To: <NOUCxYe--3-9@lynne.ee>
[-- Attachment #1.1: Type: text/plain, Size: 1773 bytes --]
On Fri, Feb 17, 2023 at 12:52:21PM +0100, Lynne wrote:
> 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.
some of these patches are very simple, yes. Others probably not (i only looked at
the first few)
That said i was never a friend of large last minute patch-sets before releases.
I think the real deciding factor is the communities opinion and
3 Developers already are against this going in before the branching. So
unless theres a shift in oppinion i think there are more people for applying
this after branching release/6.0 than before.
Is it an issue if its only in 6.1 in 6months ?
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
In fact, the RIAA has been known to suggest that students drop out
of college or go to community college in order to be able to afford
settlements. -- The RIAA
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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".
next prev parent reply other threads:[~2023-02-17 15: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
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 [this message]
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=20230217154501.GA4538@pb2 \
--to=michael@niedermayer.cc \
--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