What about Unicode support for lossyWAV?http://www.mediafire.com/file/cwyb3wf9dm23...eSupport-v1.zip
Thanks. The C++ version should have unicode support as well.
Quote from: tycho on 30 August, 2012, 04:07:02 AMThanks. The C++ version should have unicode support as well.Haven't looked at the C++ port yet. Is it "ready for production" yet?Also: With "should have" you mean it does have Unicode support (for Win32) or adding Unicode support (for Win32) is on the TODO list?In the latter case, I could add Unicode support to the C++ port, if that is desired...
No surprise here. It's known that there are some kind of signals which FLAC itself compresses very efficiently (i.e. solo piano music). Those signals can actually have a worse compression ratio when preprocessed with lossyWAV, because it forces FLAC to use a very small block size of 512 samples, thus decreasing it's efficiency (while lossyWAV can't always make up for the loss in those cases, see the small correction file).
Maybe there's some place to mention this caveat in the wiki article?
--stdout|C:\"Program Files"\bin\flac - -b 512 -5 -f -o%d --ignore-chunk-sizes
-C --stdinname "%d"
"input.wav" -q H
" " "input.wav" -q H
1 out of 1 tracks converted with major problems.Source: "E:\Zenek\Metal\Epica - Discography\Albums\2003 - The Phantom Agony\05. Illusive Consensus.flac" An error occurred while writing to file (The encoder has terminated prematurely with code 1 (0x00000001); please re-check parameters) : "C:\Users\Bull\Desktop\05. Illusive Consensus.lossy.flac" Additional information: Encoder stream format: 44100Hz / 2ch / 16bps Command line: "C:\Windows\System32\cmd.exe" /d /c F:\Dropbox\fb2k\lossyWAV\lossywav - -q X --silent --stdout|F:\Dropbox\fb2k\Flac\flac - -b 512 -5 -f -o"05. Illusive Consensus.lossy.flac" --ignore-chunk-sizes Working folder: C:\Users\Bull\Desktop\ Conversion failed: The encoder has terminated prematurely with code 1 (0x00000001); please re-check parameters
Just the first thing I saw, but try adding the missing space between “-o” and the output filename.
Hi Mardel,Could Drive C: be full? foobar2000 sometimes (especially when tagging a lot of data) creates temporary files which effectively double the disk space required to create the output file.
Hmmm.... Could you please try removing the FLAC portion of the command so that a ".lossy.wav" file is produced?If that fails, could you please add "--adaptive off" to the lossyWAV command?