Quote from: Nick.C on 2008-05-08 18:56:15

A progress bar in what sense and to what purpose? I suppose I could append a line to a log file with a "-l <filepath\filename>" type parameter but what would you want it to contain? When running from the command line there is a progress output of sorts which doesn't include the %age complete, rather amount of data processed (duration of WAV file processed) and number of bits removed so far.
A bit more detail as to what you would want to see would be nice.

A progress %age would be more convenient to me while working with dos-screen-output and batchfiles than the up- and downcounting to just 256 MB. When processing a disc image of say 771 MB, it's useless to see the up and downcounting not knowing where it ends. The percentage like flac does is fine.
And while processing I see an 'average' line with info that I would like to save. I'm a list and reports man. Especially in the testperiods it's nice to see what lossywav did with my files. I know most people us xp and foobar, but I'm with win98 on a slower and older computer, which is sufficient for playing my music and surfing.

A progress %age would be more convenient to me while working with dos-screen-output and batchfiles than the up- and downcounting to just 256 MB. When processing a disc image of say 771 MB, it's useless to see the up and downcounting not knowing where it ends. The percentage like flac does is fine.
And while processing I see an 'average' line with info that I would like to save. I'm a list and reports man. Especially in the testperiods it's nice to see what lossywav did with my files. I know most people us xp and foobar, but I'm with win98 on a slower and older computer, which is sufficient for playing my music and surfing.

Okay, I've modified the MB counter and it shouldn't overflow - I'll test a large WAV file tonight.
A %age counter (x.xx%) has been added which should be enough resolution to see progress on an older computer / large file.

I was toying with a "time already taken / total time to process completion" predictor - any use to anyone?

lossyWAV v1.0.0, Copyright (C) 2007,2008 Nick Currie. Copyleft.
Issued as free software; License: GNU GPL; Issued with NO WARRANTY WHATSOEVER.

Usage   : lossyWAV <input wav file> <options>

Example : lossyWAV musicfile.wav

Quality Options:

-q <n>        quality preset (10 = highest quality, 0 = lowest bitrate;
              -q 5 is generally accepted to be transparent) default = -q 5.

Standard Options:

-check        check if WAV file has already been processed; default=off.
              errorlevel=16 if already processed, 0 if not.
-correction   write correction file while processing WAV file; default=off.
-force        forcibly over-write output file if it exists; default=off.
-help         display help.
-longhelp     display extended help.
-merge        merge existing lossy.wav and lwcdf.wav files.
-noclips      set allowable number of clips per channel per codec block to 0;
              default: -q 0 to 3 = 3; -q 4 = 2; -q 5 = 1; -q 6 to 10 = 0.
-o <folder>   destination folder for the output file(s).

Special thanks:

David Robinson for the method itself and motivation to implement it.
Don Cross for the original Pascal source for the FFT algorithm used.
Horst Albrecht for valuable tuning input and feedback.

lossyWAV v1.0.0, Copyright (C) 2007,2008 Nick Currie. Copyleft.
Issued as free software; License: GNU GPL; Issued with NO WARRANTY WHATSOEVER.

Usage   : lossyWAV <input wav file> <options>

Example : lossyWAV musicfile.wav

Quality Options:

-q <n>        quality preset (10 = highest quality, 0 = lowest bitrate;
              -q 5 is generally accepted to be transparent) default = -q 5.

Standard Options:

-check        check if WAV file has already been processed; default=off.
              errorlevel=16 if already processed, 0 if not.
-correction   write correction file while processing WAV file; default=off.
-force        forcibly over-write output file if it exists; default=off.
-help         display help.
-longhelp     display extended help.
-merge        merge existing lossy.wav and lwcdf.wav files.
-noclips      set allowable number of clips per channel per codec block to 0;
              default: -q 0 to 3 = 3; -q 4 = 2; -q 5 = 1; -q 6 to 10 = 0.
-o <folder>   destination folder for the output file(s).

Advanced Options:

-analyses <n> select number of FFT analysis lengths to use; (2<=n<=5);
              default=2, i.e. 64 sample and 1024 sample FFT analyses;
              (3=2+128 sample FFT; 4=3+256 sample FFT; 5=4+512 sample FFT).
-fft32        enable 32 sample FFT for improved impulse detection;
              defaults: -q 0 to 2 = off; -q 3 to 10 = on.
-minbits <n>  select minimum bits to keep (0.0<=n<=8.0, resolution = 0.01);
              default = (2.9,2.95,3,3.125,3.25,3.375,3.5,3.625,3.75,3.875,4)
-scale <n>    scaling factor from WaveGain / etc; default = 1.000000; n<>0!

System Options:

-detail       enable detailed output mode
-nowarn       suppress lossyWAV warnings.
-quiet        significantly reduce screen output.

-below        set process priority to below normal.
-low          set process priority to low.

Special thanks:

David Robinson for the method itself and motivation to implement it.
Don Cross for the original Pascal source for the FFT algorithm used.
Horst Albrecht for valuable tuning input and feedback.

C:\Data_NIC\_WAV\WAV\tmp>lossywav ..\_swavyy\"Jean Michel Jarre - [1976] Oxygene.wav" -q 0 -force
lossyWAV v1.0.0, Copyright (C) 2007,2008 Nick Currie. Copyleft.
Issued as free software; License: GNU GPL; Issued with NO WARRANTY WHATSOEVER.
Processing : Jean Michel Jarre - [1976] Oxygene.wav
Format     : 44.10kHz; 2 ch.; 16 bit.
Progress   : 2.25%, 9.00MB, 4.7743 bits; 9.94x; 5.38s/239.56s;

C:\Data_NIC\_WAV\WAV\tmp>lossywav ..\_swavyy\"Jean Michel Jarre - [1976] Oxygene.wav" -q 0 -force
lossyWAV v1.0.0, Copyright (C) 2007,2008 Nick Currie. Copyleft.
Issued as free software; License: GNU GPL; Issued with NO WARRANTY WHATSOEVER.
Processing : Jean Michel Jarre - [1976] Oxygene.wav
Format     : 44.10kHz; 2 ch.; 16 bit.
Average    : 400.56MB; 6.3596 bits; 24.46x; 97.34s;
%lossyWAV Warning% : 6 sample(s) clipped to limiting amplitude.

C:\Data_NIC\_WAV\WAV\tmp>lossywav ..\_swavyy\"Jean Michel Jarre - [1976] Oxygene.wav" -q 0 -force -quiet -nowarn
Jean Michel Jarre - [1976] Oxygene.wav; 400.56MB; 6.3596; 23.24x; 102.47s; C:6;

It looks alright to me.

lossyWAV 1.0.0, Copyright (C) 2007,2008 Nick Currie. Copyleft.
Issued as free software; License: GNU GPL; Issued with NO WARRANTY WHATSOEVER.

Usage   : lossyWAV <input wav file> <options>

Example : lossyWAV musicfile.wav

Quality Options:

-q, --quality <n>   quality preset (10=highest quality, 0=lowest bitrate;
                    -q 5 is generally accepted to be transparent)
                    default=-q 5.

Standard Options:

-c, --check         check if WAV file has already been processed; default=off.
                    errorlevel=16 if already processed, 0 if not.
-C, --correction    write correction file for processed WAV file; default=off.
-f, --force         forcibly over-write output file if it exists; default=off.
-h, --help          display help.
-L, --longhelp      display extended help.
-M, --merge         merge existing lossy.wav and lwcdf.wav files.
-N, --noclips       set allowable number of clips / channel / codec block to 0;
                    default=3,3,3,3,2,1,0,0,0,0,0 (-q 0 to -q 10)
-o, --outdir <dir>  destination directory for the output file(s).
-v, --version       display the lossyWAV version number.

Advanced Options:

-a, --analyses <n>  select number of FFT analysis lengths to use; (2<=n<=5);
                    default=2, i.e. 64 sample and 1024 sample FFT analyses;
                    (3=+128 sample FFT; 4=+256 sample FFT; 5=+512 sample FFT).
-F, --fft32         enable 32 sample FFT for improved impulse detection;
                    defaults: -q 0 to 2=off; -q 3 to 10=on.
-m, --minbits <n>   select minimum bits to keep (0.00<=n<=8.00);
                    default=2.9,2.95,3,3.125,3.25,3.375,3.5,3.625,3.75,3.875,4.
-s, --scale <n>     scaling factor from WaveGain, etc; default=1.000000; n<>0!

System Options:

-d, --detail        enable detailed output mode
-n, --nowarnings    suppress lossyWAV warnings.
-Q, --quiet         significantly reduce screen output.

-b, --below         set process priority to below normal.
-l, --low           set process priority to low.

Special thanks:

David Robinson for the method itself and motivation to implement it.
Don Cross for the original Pascal source for the FFT algorithm used.
Horst Albrecht for valuable tuning input and feedback.

lossyWAV 1.0.0

Is stdin for encoding technically impossible? It would be great if one could live without these temporary files 
Everything else is soo great! Thanks a lot!

well, since it's gpl'ed now, can you please make the sourcecode available to me? I want to look into an stdin 'hack' 

thanks

Of course I will do that 
But I can't promise anything... I'm still quite a beginner (but I own Delphi 6 because we need it at school), so please don't depend on it too much.

[...] GNU Coding Standards documentation.

I think issuing lossyWAV under the GNU GPL and Copyleft will be better in the long run for the project, so that is my plan.

• I don't know Windows very well (in fact, I don't even have a Windows machine).
• I use primarily Unix systems, including Linux and FreeBSD.
• I do know C reasonably well.
• I have only a modicum of knowledge of Pascal, from my freshman years at the University.
• I don't know ia-32 ASM (well, I used to, but I forgot almost everything, since I've been working with higher level languages and algorithms, mostly).
• I don't know signal processing.
• I want to use lossyWAV on systems that are not even related to Win32. For instance, I would love to have it working on the 11 architectures that are supported by Debian and, once the code is platform agnostic, I can package it and upload it to Debian's repository, since I will soon be a Debian Maintainer (which sould be real soon now, really).

Quote from: Nick.C on 2008-05-12 11:05:19

I think issuing lossyWAV under the GNU GPL and Copyleft will be better in the long run for the project, so that is my plan.

This was a nice and welcome choice, I think. BTW, what about putting the code in a public repository, so that you can manage the changes? If you want some help with repositories, I think that I can help. This would ease a lot the development and release of the files and also allow the project to gain momentum.
(...)

Thanks for your enthusiasm and offer of transcoding skills - v1.1.0b would be the best to start from. There is already a sourceforge project created, it is just empty.

I can revert the IA-32 / x87 assembler to Delphi (though don't hold your breath - I've modified the implementation since it was Delphi, so it will be a transcode back to Delphi rather than a copy and paste).

Also, you may be able to replace the nFFTdouble unit with an existing library.

fftw-dev - library for computing Fast Fourier Transforms
fftw-docs - documentation for fftw
fftw2 - library for computing Fast Fourier Transforms
libfftw3-3 - library for computing Fast Fourier Transforms
libfftw3-dev - library for computing Fast Fourier Transforms
libfftw3-doc - documentation for fftw version 3
libgsl0ldbl - GNU Scientific Library (GSL) -- library package
mffm-fftw-dev - A C++ wrapper for the fftw.org C library (version 3)
mffm-fftw1c2 - A C++ wrapper for the fftw.org C library (version 3)
sfftw-dev - library for computing Fast Fourier Transforms
sfftw2 - library for computing Fast Fourier Transforms

If you wish to take over the management of the sourceforge project, let me know and it's yours....

Quote

Also, you may be able to replace the nFFTdouble unit with an existing library.

It seems that we have a lot of choices regarding FFT... I just checked the repository on Debian and came up with this:
(...)