MadMan007
500+ Head-Fier
- Joined
- Oct 17, 2008
- Posts
- 620
- Likes
- 18
Quote:
FYI on any halfway modern dual core CPU there is no slowdown due to encoding with EAC. Maybe that's because EAC is 'so slow' with ripping which ime it isn't compared to trial versions of dbPoweramp but whatever. You can set EAC to call as many external compressor threads as you want.
They are both fine programs, dbpoweramp is easier to use and set up with less fiddling, EAC has more indepth 'power user' options but they need to be set to get the most out of it. I felt like I learned a lot more about ripping with EAC which may not interest everyone, when I first started ripping my CDs I tried both. One thing I do like about EAC is that it's more open wrt the external encoder you want to call rather than the dbpoweramp add-ins for each codec. (I do my tagging through the encoder command line call, this is my external compressor command line in EAC for FLAC: -8 -V -T "artist=%a" -T "title=%t" -T "album=%g" -T "date=%y" -T "tracknumber=%n" -T "genre=%m" %s)
| Originally Posted by stokitw /img/forum/go_quote.gif dbpoweramp worths every penny of it.. Unless you want to stick with cue sheet, you should try dbpoweramp. It has better tagging, faster speed of ripping with same level of security. The new version utilize the multi-core processors pretty well. What happen in EAC if you rip track by track: you slowly rip one track and then the plugins starts to convert the file. in the meanwhile, the CD-ROM stop and restart the spinning after the conversion is done. I don't know if there are new plugins to address this issue. But the whole process would takes a very long time. Things get better if you rip the whole disk at once, but once again the ripping speed in EAC is slower. What dbpoweramp does is after you set up the offset, it always try to rip in high speed, and then it rips the same track multiple times to compare the result. If your CD has no error or can be directly matched with AccurateRip, the overall ripping process is much faster. Even if there are some frames is questionable, you won't be slow down in each pass like EAC. dbpoweramp goes back to the questionable frames after the ripping of rest of the track is done. This also saves you from waiting the ripping questionable frames and the spin-up time. I don't know how EAC utilizes the multi-core CPU. The way dbpoweramp does largely saves your time by using one core to rip and another to convert. This reduce the chance of CD-ROM spin down to wait for conversion. Overall, if you want to rip track by track, dbpoweramp worth every penny it asks. Not to mention it's convienent multi-format ready file converter. |
FYI on any halfway modern dual core CPU there is no slowdown due to encoding with EAC. Maybe that's because EAC is 'so slow' with ripping which ime it isn't compared to trial versions of dbPoweramp but whatever. You can set EAC to call as many external compressor threads as you want.
They are both fine programs, dbpoweramp is easier to use and set up with less fiddling, EAC has more indepth 'power user' options but they need to be set to get the most out of it. I felt like I learned a lot more about ripping with EAC which may not interest everyone, when I first started ripping my CDs I tried both. One thing I do like about EAC is that it's more open wrt the external encoder you want to call rather than the dbpoweramp add-ins for each codec. (I do my tagging through the encoder command line call, this is my external compressor command line in EAC for FLAC: -8 -V -T "artist=%a" -T "title=%t" -T "album=%g" -T "date=%y" -T "tracknumber=%n" -T "genre=%m" %s)
