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 1/2] lavu/tx: add real to real and real to imaginary RDFT transforms
Date: Thu, 3 Aug 2023 18:42:51 +0200 (CEST)
Message-ID: <NawGxLe--3-9@lynne.ee> (raw)
In-Reply-To: <NawD9Lq--3-9@lynne.ee-NawDDOJ----9>

Aug 3, 2023, 18:26 by dev@lynne.ee:

> 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.
>

Specifically, for R2R, vs fftw
  26280 decicycles in           av_tx (r2c), 1048574 runs,      2 skips
  69940 decicycles in         fftwf_execute, 1048576 runs,      0 skips

And for R2I
  25856 decicycles in           av_tx (r2c), 1048571 runs,      5 skips
  65561 decicycles in         fftwf_execute, 1048576 runs,      0 skips
_______________________________________________
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-08-03 16:43 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   ` Lynne [this message]
     [not found]   ` <NawGxLe--3-9@lynne.ee-NawH0-d----9>
2023-08-04  2:05     ` [FFmpeg-devel] [PATCH v2 1/2] lavu/tx: add real to real and real to imaginary RDFT transforms Lynne
2023-08-03 20:32 ` [FFmpeg-devel] [PATCH " Michael Niedermayer
2023-08-03 20:39   ` Andreas Rheinhardt
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=NawGxLe--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