lossyWAV Development
Reply #918 – 2008-03-05 19:17:12
I'm 2 inches from releasing an updated version of the batch file and the front end. So far, the changelog looks like this, but it's not guaranteed final yet. lFLCDrop Change Log: v1.2.0.5 - presets updated to -1 through -7 - all presets create correction files, except custom lFLC.bat Change Log: v1.0.0.7 - added automatic functionality for the -merge option - new variable in custom preset to enable/disable automatic merging - custom preset defaults match normal -2 preset functionality I'm just dealing with a possible bug (or screw up on my part) for the automatic -merge function, and then merging that code into the custom preset section, and it should be fully updated and synced with current lossyWAV "goings-on". re: the automatic merge function, if the FLAC file to decode has custom metadata, will check the decoded WAV file for the lossyWAV "tag". If it's a lossyWAV, then it will see if a .lwcdf.flac exists and decode to .lwcdf.wav, or if no .lwcdf.flac exists, it will check for a .lwcdf.wav, or else exit. And in the first two cases of lossyWAV correction file existing, it will ultimately run the -merge option, and delete the two lossyWAV files. (the .wav files, not the source .flac files) [edit] yep, already thought of a needed change to the changelog... to add a custom preset variable to toggle the deleting of the pre-merged .lossy.wav files. and i also realized that i'm not handling the encoding of a .lwcdf.wav file to .lwcdf.flac file (if it exists) when encoding an already lossy .wav file. wowzahs. now i'm more than 2 inches away. [/edit]