Please add support for LossyWAV

[amalgam]

Just discovered about this lossy codec. Seems like an interesting alternative (to me) for converting my FLAC collection when syncing audio to my PMP as an alternative to MP3 (V0/V2): It can achieve similar bit-rates while avoiding MP3's audio artifacts by first running the LossyWAV pre-process then encode with FLAC creating a lossyFLAC file (.lossy.flac).
The resulting .lossy.flac can be played by any player supporting FLAC.

This could be used with other lossless codecs, obviously.

What do you think?

More info/details: http://wiki.hydrogenaudio.org/index.php?title=LossyWAV

[JII]

Hi,

Indeed, LossyWAV seems a very interesting approach that would deserve to be included in codec central. Combine with flac (or other lossless encoders), it can make "near lossless" file generally half the lossless size and manage some hybrid encoding (with a second file that let retransform the lossy file to lossless).

I tried to "implement" it in dbpoweramp with the CLI encoder but I failed. Here is my encoder.txt

[codec]
.lossy.wav
lossyWAV.exe

[msgifnoencoder]
Before using this encoder a seperate component must first be installed from http://www.hydrogenaud.io/forums/index.php?showtopic=107081&st=0 . Separate component can be installed to increase processing speed from http://www.fftw.org/install/windows.html .

[slider]
4
24
292
4
Extraportable (lowest quality output, not fully transparent)
-q X
Portable (good quality output for DAP use, may not be transparent)
-q P
Economic (intermediate quality output, likely to be transparent)
-q C
Standard (default quality output, considered to be transparent)

High (high quality output, suitable for transcoding)
-q H
Extreme (higher quality output, suitable for transcoding)
-q E
Insane (highest quality output, suitable for transcoding)
-q I

[label]
10
44
low quality (smaller file)
808080

[label]
216
44
high quality (larger file)
808080

[combo]
60
66
190
1
No correction file for lossless encoding 
 
Write correction file for lossless encoding (lwcdf.wav)
-C

[clistring]
- -o "[outfile]" --stdinname "[outfile]" -f -S

[highestqualitydecode]

I think it's "just" a naming problem. In order to possibly create two files (lossy.wav and lwcdf.wav when asked), LossyWAV seems to need to know the folder (-o setting) and the file name (--stdinname setting or "[infile]" if we don't use stdin but there is the same problem) separately. I don't know how manage that with CLI encoder where "[outfile]" seems to give the complete path.

Thank you very much for your kind help.