Turn on suggestions

Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.

Showing results for

- Intel Community
- Software
- Software Development SDKs and Libraries
- Intel® oneAPI Math Kernel Library
- very basic fft question

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page

madir

Beginner

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

03-16-2012
10:21 AM

112 Views

very basic fft question

Hello,

I would like to perform a basic fft of audio data:

N real samples -----> N/2+1 complex numbers (No need to obtain the conjugate symmetric other half...)

Furthermore I would like the complex numbers to be in the MKL_Complex format, not separate arrays for real and complex.

How do I set up such an fft using the dfti interface?

I must say the documentation is annoyingly confusing! Can someone spare me the pain?

Thanks in advance!

Link Copied

8 Replies

mecej4

Black Belt

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

03-16-2012
11:18 AM

112 Views

madir

Beginner

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

03-16-2012
11:50 AM

112 Views

Thanks, but I have yet to find an example that covers what I want to do.

Todd_R_Intel

Employee

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

03-16-2012
01:30 PM

112 Views

basic_sp_real_dft_1d.c

for single-precision floating point or

basic_dp_real_dft_1d.c

for double-precision floating point in the examples\dftc sub-directory of Intel MKL look like the closest to what you want. Maybe you could take a look and tell us how what you want is different.

Todd

madir

Beginner

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

03-17-2012
05:45 AM

112 Views

Thank you very much for your help! Unfortunately those files do not exist anywhere in ..\Intel\ComposerXE-2011\mkl\examples

Maybe I don't have the most recent version of MKL. I got it a year ago or so. Have those examples been added recently?

mecej4

Black Belt

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

03-17-2012
07:03 AM

112 Views

The examples have been there for quite a while, even in earlier versions of MKL 10.3.

madir

Beginner

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

03-17-2012
08:04 AM

112 Views

163 files, but none of those mentioned above.

Dmitry_B_Intel

Employee

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

03-18-2012
08:11 PM

112 Views

Looks like you use MKL 10.3.4 or earlier.

I attach the source code of basic_sp_real_dft_1d.c for your convenience.

The sequence of steps needed to compute FFT is described on the first page of FFT documentation.

We would appreciate if you shared what in the documentation caused your confusion, for we could improve it.

Thanks

Dima

madir

Beginner

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

03-26-2012
01:54 AM

112 Views

Thanks for the code, I'll check it out. Sorry for my late reply, I have been overwhelmed with work:)

One thing struck me, the example uses malloc() rateher than mkl_malloc. Surely 16 byte aligned allocation using mkl_malloc must be required for maxiumum performance, am I wrong?

Topic Options

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page

For more complete information about compiler optimizations, see our Optimization Notice.