From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 1/2] lavu/tx: add real to real and real to imaginary RDFT transforms
Date: Thu, 3 Aug 2023 22:39:59 +0200
Message-ID: <GV1P250MB0737C2AB03962C5DD62ACF2D8F08A@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20230803203253.GP7802@pb2>
Michael Niedermayer:
> On Thu, Aug 03, 2023 at 06:26:16PM +0200, Lynne wrote:
>> These are in-place transforms, required for DCT-I and DST-I.
>>
>> Templated as the mod2 variant requires minor modifications, and is
>> required specifically for DCT-I/DST-I.
>>
>> Quite optimized, as there's no need for any additional buffer storage.
>>
>
>> doc/APIchanges | 3
>> libavutil/tx.c | 18 ++++
>> libavutil/tx.h | 10 ++
>> libavutil/tx_template.c | 175 +++++++++++++++++++++++++++++++++++++-----------
>> libavutil/version.h | 2
>> 5 files changed, 167 insertions(+), 41 deletions(-)
>> 6e6308365cd78a84c7db5800207e6b5977945079 0001-lavu-tx-add-real-to-real-and-real-to-imaginary-RDFT-.patch
>> From 2ea5e2541c2551bf1b56e967d35946289a85aa49 Mon Sep 17 00:00:00 2001
>> From: Lynne <dev@lynne.ee>
>> Date: Thu, 3 Aug 2023 18:21:23 +0200
>> Subject: [PATCH 1/2] lavu/tx: add real to real and real to imaginary RDFT
>> transforms
>>
>> These are in-place transforms, required for DCT-I and DST-I.
>>
>> Templated as the mod2 variant requires minor modifications, and is
>> required specifically for DCT-I/DST-I.
>
> not sure if i forgot some patch but
> this seems to break fate-binkaudio-dct
>
It's not just you; patchwork reported four failing tests:
make: *** [fate-filter-firequalizer] Error 218
make: *** [fate-binkaudio-rdft] Error 218
make: *** [fate-binkaudio-dct] Error 218
make: *** [fate-qdm2] Error 218
- Andreas
_______________________________________________
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-08-03 20:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 16:26 Lynne
[not found] ` <NawD9Lq--3-9@lynne.ee-NawDDOJ----9>
2023-08-03 16:31 ` [FFmpeg-devel] [PATCH 2/2] lavu/tx: add DCT-I and DST-I transforms Lynne
2023-08-03 16:42 ` [FFmpeg-devel] [PATCH 1/2] lavu/tx: add real to real and real to imaginary RDFT transforms Lynne
[not found] ` <NawGxLe--3-9@lynne.ee-NawH0-d----9>
2023-08-04 2:05 ` [FFmpeg-devel] [PATCH v2 " Lynne
2023-08-03 20:32 ` [FFmpeg-devel] [PATCH " Michael Niedermayer
2023-08-03 20:39 ` Andreas Rheinhardt [this message]
2023-08-04 2:04 ` Lynne
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=GV1P250MB0737C2AB03962C5DD62ACF2D8F08A@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM \
--to=andreas.rheinhardt@outlook.com \
--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