I seem to be having issues with ALAC encoded with DB Poweramp. Every track fails the Foobar Foo_Verifier test, it says the track lengths are a mismatch. The newest Foo_Verifier will check Accurate rips data base. DB Poweramp encoded ALAC albums all come up "not a proper gapless album". Also when I do a Bit Compare test against the Flac files that were transcoded, they all come back bad! BTW, I'm using the Ref 13.3 version of DB with all the latest plug ins.Conversely, when I use Cue Tools with the latest ffmpeg ALAC encoder, every track passes the Foo_Verifier test, the Bit Compare, and the Accurate Rip (within Foobar). Everyone keeps telling me that FFmpeg is NOT archive ready. I beg to differ. Even if 1/1000 tracks is bad, the other 999 pass Foobars tests where DB fails every time. itunes encoded ALAC pass all those Foobar tests too. I see no reason not to use ffmpeg with Cue Tools. I like it better anyway because it creates an accurate rip log and it copies over the EAC log to the new folder. It makes a cue sheet with .m4a extensions but they can always be edited to work with .wav down the road. I would like to know why DB Poweramps ALAC encoder has so many problems with Foobar though.
I love the iPod Touch but man I wish it just played FLAC
ok, I have some really stupid questions here:first, how does flac store gapless playback info? second, if I convert flac to alac, will the gapless info make it into the pgap atom? and will it be "proper"?third, if I rip direct to alac using this guide:http://wiki.hydrogenaudio.org/index.php?title=EAC_and_ALACwill the resulting files have the proper pgap info in them?thx!