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: Sun, 19 Feb 2023 17:53:45 +0100 (CET)
Message-ID: <NOea74V--3-9@lynne.ee> (raw)
In-Reply-To: <20230219154014.GG1949656@pb2>
Feb 19, 2023, 16:40 by michael@niedermayer.cc:
> Hi
>
>
> On Sun, Feb 19, 2023 at 01:08:02AM +0100, Lynne wrote:
>
>>
>> Feb 18, 2023, 20:03 by michael@niedermayer.cc:
>>
>> > On Fri, Feb 17, 2023 at 04:43:50AM +0100, Lynne wrote:
>> >
>> >> This small patchset mostly rewrites Vulkan to enable using multiplane images,
>> >> and implements video decode support. Also, many numerous bugs and issues
>> >> were fixed, as well as having quite a lot of performance improvements.
>> >>
>> >> The patchset can be viewed here as well:
>> >> https://github.com/cyanreg/FFmpeg/tree/vulkan_staging
>> >>
>> >> Patches attached.
>> >>
>> >
>> > [...]
>> >
>> >
>> >> av1dec.c | 3 +++
>> >> avcodec.h | 5 +++++
>> >> h264dec.c | 3 +++
>> >> hevcdec.c | 3 +++
>> >> vp8.c | 3 +++
>> >> vp9.c | 3 +++
>> >> 6 files changed, 20 insertions(+)
>> >> 122f9df511e4680d0027afae5d4f9f2f1880874e 0065-avcodec-add-AVHWAccel.flush-callback.patch
>> >> From 93223fa95389c60c015cfcee22784a1bf0fdb05b Mon Sep 17 00:00:00 2001
>> >> From: Lynne <dev@lynne.ee>
>> >> Date: Fri, 6 Jan 2023 03:32:56 +0100
>> >> Subject: [PATCH 65/72] avcodec: add AVHWAccel.flush callback
>> >>
>> >
>> > this patch seems to break fate-vp8-size-change
>> >
>>
>> Thanks, philipl also reported this, fixed in my branch
>>
>> https://github.com/cyanreg/FFmpeg/tree/vulkan_staging
>>
>
> ok that works, that said
> is there consensus that i should create the release branch "now"?
> It seems no review is going on in public of these patches and we should do
> the release "soon", i am asking as i dont want to just surprise anyone with
> making the branch before giving a final call
>
We need a few more days, folks are reviewing the patches
mainly on IRC and on github, since they're large.
Functionality is on-par with the current code, and it fixes
so much, apart from adding new features, I really don't want
anyone to use the old code.
The old code is so bad, even if this patchset is broken in
some ways, it would still be a big improvement over the old code.
Most of the code is code I maintain, and has been tested and
partially reviewed already by two developers who know Vulkan
and GPU code in general. I'd still like to have this in 6.0, so
I think what I should ask is if there are any objections to merging
this as-is, and fixing any issues during the testing period.
Otherwise, I'd like for 6.1 to be released no later than April.
_______________________________________________
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-19 16:53 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 [this message]
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=NOea74V--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