If I understand you correctly:1. The normal mode does not create a correction file, and is lossless.2. I'm pretty sure that the correction file has to be in the same folder. I can see no switch that would let you specify the path.
Correction files may be in different folder from lossy ones if you use foobar for playback
Hybrid mode without correction file-is not lossless? Yes?
If the -c option is specified (in addition to the -b option), then WavPack will generate an additional file that will contain the information that was discarded to generate the lossy .wv file. This file will have the same name as the .wv file but will have the extension .wvc (the 'c' is for "correction"). When WvUnpack is used to restore the .wav file, it will attempt to find the .wvc file in the same directory as the .wv file. If it is found then the decompression will be lossless and will be reported as such, otherwise lossy decompression will be reported (assuming that any information was actually discarded during the original compression). If -c is specified but no actual information is discarded, the correction file will be deleted. The extra overhead involved with having these two files instead of a single pure lossless file is usually less than 1% of the original .WAV file and can be as low as 0.25% at high bitrates. Note that CRCs are stored for both the lossy and lossless versions, so error detection works correctly whether the .wvc file is used or not.
Ok. And why foobar display bitrate of lossy file wavpack as lossless file? I'm convert to 400 kbps+correction,but foobar display 1000 kbps. ......
Quote from: igor-tf on 14 July, 2010, 06:58:49 PMOk. And why foobar display bitrate of lossy file wavpack as lossless file? I'm convert to 400 kbps+correction,but foobar display 1000 kbps. ......Foobar shows the total bitrate being consumed, counting the lossy file and the correction file together.The idea is that when the correction file is present, it's just like lossless, and so it shows the lossless bitrate.