Quote:
Originally Posted by scottder
He wasn't really asking about the merits of the codec, but weather ther was a clear advantage to using EAC over foobar for encoding. EAC will shine when there are issues with the disc (sometimes even light scratcing can cause encoding issues). but foobar will encode them faster.
Scott
|
You're misunderstanding.
There is no difference whatsoever between using EAC and foobar to
encode files. Either way, the MPC .dll or .exe or whatever it is that encodes .wav files into Musepack format is put into play -- and it's the same regardless of whether EAC or Foobar calls for it.
What you're doing, Scott, is making the assumption that Foobar can rip CDs. I don't think it can, but I haven't updated in a while, so maybe this feature was added in a recent build? If it was, then yes, you definitely should use EAC as opposed to Foobar to
rip your CDs (in Secure Mode). However, if you choose to have EAC encode them after ripping -- or if you choose to wait and encode a directory full of .wavs all at once in Foobar -- makes no difference.
To clarify, there's two steps involved in the "encoding" process, no matter into which format you wish to encode:
1) Ripping audio off a CD into a resulting .wav PCM file. This is done best by EAC. I don't think Foobar even has this capability, but perhaps it does now.
2) Encoding said .wav PCM files into whatever format you choose -- MPC, in this case. You can do this within EAC, within Foobar, or even with the Monkey's Audio front-end program. Whichever you choose, the result is the same because all three programs (EAC, Foobar, Monkey's) are just acting as a "controller" for the MPC encoder .dll to do its job. Of course, differences arise in the way that these "controller" programs can
tag the resulting files -- Foobar probably wins in this respect.
- Chris