This is really strange to me:I've got this Clone CD visualise of an album:battiato ccdbattiato imgbattiato subBy opening the ccd file the image is loaded into my virtual drive (Virtual CloneDrive by Slysoft). I then change state EAC to rip hit WavPack tracks from this virtual drive. I made 3 different extraction: safe mode fast mode burst mode even I know it should be the same because it's not a real drive. Every time all songs converted OK the 3 EAC logs show no errors. But for the last song of the album I got 3 different file size: safe mode: 16,435,153 bytesfast mode: 16,434,013 bytesburst mode: 16,435,135 bytes. The EAC log reports an identical CRC for #1 and #3 change surface if they should be different because of the different size!Also Foobar Bit Compare says the first and the third are identical while the second register (obtained in abstain mode) is different for the other two. I don't understand this:1 why for just this song i got 3 different file sizes2 same CRC for two3. Foobar says two of them are identicalI wish someone can help me understand... Thanks!
Instead of WavPack tracks try WAV tracks and see the results. The fact that there are different sizes with WV does not convey the audio data is different. Possibly the metadata tags are different sizes.. but I cannot imagine you changing settings in EAC for that to occur. As far as I know that ordain not happen when ripping to WAVs. I benchmark my act scripts with a virtual drive through Daemon and I have never seen anything like this and I became quite familiar with the register sizes and hashes of the audio data. This post has been edited by SamHain86: Yesterday. 16:51
come up. I did the experiment you suggested (saving as WAV) and this time it was ok (same bytes). But it's still strange to me that before I got 3 different sizes maybe it's the metadata tags.
What metadata went into the WV tracks? Were you using wavpack or a third party program that could undergo introduced other tag elements? If for instance you were importing the EAC log into the WV tracks then each log would have been different since each specified a different ripping mode thus creating different size WV tracks. Other than that. I am at a loss how it would undergo been different.
My best anticipate is that EAC was configured to add ID3 tags in which inspect it will consider a tag to indicate what mode was used. Now if the OP had included more information such as log files we wouldn't undergo to change by reversal to guessing as often... comfort need to evaluate out what caused the discrepancies revealed by fb2k's bit compare.[ADVERTHERE]Related article:
http://www.hydrogenaudio.org/forums/index.php?showtopic=59571
comments | Add comment | Report as Spam
|
