How about a link somewhere to http://www.fftw.org/download.html to make the lib easy to find (and avoid a lot of asking)?

actually, I can't find where to download libfftw3-3.dll either...

Use the link I gave, on this page you find links for Windows (there's 64bits too), OS-X, Linux and so on.

The current version is FFTW 3.2.1 in the zip file you find libfftw3-3.dll

BTW. At the beginning of this thread Nick says "Use of FFTW requires the presence of "libfftw3-3.dll" on the host", I tell you it needs that lib always with version 1.1.4c whether used or not.

Meh - I think that I'll have to compile a separate version without FFTW support.

I tell you it needs that lib always with version 1.1.4c whether used or not.

I think that I'll have to compile a separate version without FFTW support.

//init
if(fftw_switch)
{
    hinstLib = LoadLibrary("libfftw3-3.dll");
    if(hinstLib == NULL)
    {
        print_error("...");
        exit(-1);
    }
    proc1 = GetProcAddress(hinstLib, "_fftw_execute");
    if(proc1 == NULL)
    {
        print_error("...");
        exit(-1);
    }

    //here we can call proc1
}


//cleanup
if(fftw_switch)
{
    FreeLibrary(hinstLib);
}

I'm unwilling to add circa 500kiB to the download as it will eat into HA's bandwidth, so I do not intend to add the DLL to the distribution.

I am searching for error trapping principles to allow the program to continue in the event that the DLL is missing.

Thanks for the offer of hosting. I think that I have cracked the running without 'libfftw3-3.dll' problem (thanks for the pointer lvqcl!!). Still testing - will try to post beta 1.1.4d and source later.

[edit] Should lossyWAV terminate with an error if --fftw is included in the command line and 'libfftw3-3.dll' cannot be found? The alternative would be to continue using the existing FFT routines. [/edit]

If I understand correctly, the only difference is the speed and not the quality, right? In that case, I think it would be the best if it just printed out a warning that it can't use FFTW because the libfftw3-3.dll is not present and continue "encoding" using the existing FFT routines.

Quote from: doccolinni on 2009-06-07 21:38:03

If I understand correctly, the only difference is the speed and not the quality, right? In that case, I think it would be the best if it just printed out a warning that it can't use FFTW because the libfftw3-3.dll is not present and continue "encoding" using the existing FFT routines.

We're certainly thinking on the same wavelength....

lossyWAV beta 1.1.4d attached to post #1 in this thread.

lossyWAV doesn't support wild cards in the input filename.

I don't know if batch files are of any use to you using WINE, but there was a drag-n-drop batch file somewhere in one of these threads which also copied the tags from the source file.