I hope I'm not veering too far off topic. Apologies if I am.
Sorry about the width of this post. I thought the CODEBOX elements would alleviate that, but it doesn't seem so.
@Dynamic
I tried losswav with the settings listed in the KB, but couldn't get it to work. Thanks for the suggestion.
For simplicity and avoiding spaces in path names specified on the commandline, I've copied lossywav.exe and wavpack.exe to a new folder called C:\audio
These settings work for lossyWAV version 1.1.0b, but not for 1.0 as I recall. I don't know if they work for 1.2 beta versions. Open a command prompt (Start\Run\cmd.exe) and type C:\audio\lossywav to see the version. I copied these pretty much from the EAC and Lossywav entry in the KB.
Note that the program you call is not lossywav directly, but the Command Prompt, cmd.exe, that comes with Windows! That's a little counterintuitive!
In EAC's compression options, I have
[b][Tick][/b] Use ext. prog. for compr.
Param pass. sch.: [b]User Defined Encoder[/b]
Use file extension: [b].wv[/b] (Note that EAC can't use a double extension like .lossy.wv in current versions)
Program, incl path, used for compression: [b]C:\WINDOWS\system32\cmd.exe[/b]
Additional command-line options:
[b]/d /c C:\audio\lossyWAV %s --silent --stdout|C:\audio\wavpack.exe -h --blocksize=512 --merge-blocks -i -w "Cuesheet=@*.cue" -w "Artist=%a" -w "Title=%t" -w "Album=%g" -w "Year=%y" -w "Track=%n" -w "Genre=%m" - %d[/b]
Bit rate: (irrelevant, but I set it to [b]512 kBit/s[/b] as a guide to final file size only)
[b][Tick] [/b]Delete WAV after compression
[b][blank][/b] Use CRC check
[b][blank][/b] Add ID3 tag
[b][Tick][/b] Check for external programs return code
I usually then go through the files created and change the filename extension to .lossy.wv, or I simply store them in my D:\My Music\_lossyWV-images folder, in which I assume they're all lossyWV rather than lossless) and in which my .log files reveal my full encoding commandline.
So far, I hadn't bothered setting it up in foobar2000, but I just did, as follows:
Encoder: c:\windows\system32\cmd.exe
Extension : lossy.wv
Parameters: /d /c c:\audio\lossywav - --standard --silent --stdout|c:\audio\wavpack -hm --blocksize=512 --merge-blocks -i - %d
Format is : lossless or hybrid
Highest BPS mode supported: 24
This worked in creating a playable 483kbps lossyWV file, though I had an error in fb2k v0.9.4.2 in writing the appropriate tags to the file:
CLI encoder: C:\WINDOWS\system32\cmd.exe
Destination file: D:\Peace Pipe - Cry of Love.lossy.wv
"C:\WINDOWS\system32\cmd.exe" /d /c c:\audio\lossywav - --standard --silent --stdout|c:\audio\wavpack -hm --blocksize=512 --merge-blocks -i - "Peace Pipe - Cry of Love.lossy.wv"
directory: D:\
Writing tags to encoded file failed (Unsupported format or corrupted file)
I haven't got to the bottom of that yet, and if it's problematic enough, I might upgrade fb2k or even change to lossyFLAC or lossyTAK to see if they work properly or change the filename extension to wv (without the "lossy." bit in front). So far, I haven't used fb2k to generate lossyWV files except for this test.