Added support for variable naming schemes Added GUI interface for write mode options Added support for writing CUE sheets that specify .wav files rather than .flac Added option for low priority encoding Added support for EAC's Test and Copy mode Added proper GUI for initial EAC binary selection (if needed) Added new AutoFLAC icon Fixed waiting for EAC to complete encoding of all tracks Fixed waiting for EAC to complete creating CUE sheet Fixed remembering location of EAC binary Fixed bug that may prevent converting FLACs to WAVs before writing Fixed names of some variables to prevent possible conflict Updated GUI button behavor to focus cursor on relevant field after selection
Just wanted to inform you that the screenshots do not display in Opera. They display fine in IE and Firefox.
I always enjoy feedback, so if you download it and try it out (or just have any questions), let me know!Thanks, and I hope you find this as useful as I have.
elmar3rd, no checksum is currently stored. Honestly, this has never occured to me. How do you create the checksum, and how do you verify it? I'll certainly consider this for the next release.
I'm always up for some constructive criticism, so don't be shy. I explained on the AutoFLAC web page why I chose to use individual FLACs rather than a separate image. My opinion on that subject still stands, for the reasons given. However, the hidden track issue that several people have mentioned is new to me. Can someone please explain that more thoroughly, or point me to a good reference? I'm assuming that you're not simply referring to the"bonus" track that many CDs include at the end, right?bhoar, you mentioned something about a metadata issue. Could you expand on that as well? What information would you get by creating a single disc image vs. separate tracks? Currently AutoFLAC will tag each track with Artist, Album, Genre, Year, Title, and Number. The .cue sheet saves most of this information as well as CD-TEXT, including the DISCID. What's missing?Since it looks like there are at least a few people interested in using it, though, I'll be happy to look into extending it. I'll post an update once I've had a chance to test out some ideas. In the meantime, I'd really appreciate it if you could answer my questions above. Thanks.
So you run md5 on the .flac file after it's already been extracted and converted? In that case it sounds like you're only verifying the integrity of the .flac file itself (if, for example, you copy your collection from one drive to another) rather than somehow verifying it based on the original CD track. Is this correct?
bhoar and Martin H, thanks for the excellent explanations of HTOA. I did some testing using the files at the link provided, but it turns out that my drive is apparently incapable of ripping audio from track 01 index 00. It seems to recognize that there is indeed audio there, as I get the appropriate amount of leading data, but it's just silence. After doing some additional searching through the forums it seems that if I get silence on the test CD then I'm pretty much SOL. Sigh, figures. To everyone else, I'm currently looking into supporting both flac images and WavePack. These will both take some time to implement, though, so please be patient.
Perhaps there's a better way of implementing such verification that's a little more robust and can handle tag updates. Any ideas?
If the FLACs are encoded with the -V switch, then there isn't any reason for verification IMHO, but to test the integrity of the file without concern for tag updates etc, then you can use the -t switch of flac.exe.
jbreland@showdog ~/test $ metaflac --show-md5sum 01-Intro.flac46e296291cfdb19f2ae8c6a36d6611a4jbreland@showdog ~/test $ flac -ds 01-Intro.flacjbreland@showdog ~/test $ md5sum 01-Intro.wavb655d4ba6eaddec49b0cb517304cac0f 01-Intro.wav
To everyone else, I'm currently looking into supporting both flac images and WavePack. These will both take some time to implement, though, so please be patient.