bukharin;207316 Wrote: > I'm not trying to be critical btw - I'm keenly interested in this topic, > because I'm quite anal about ripping correctly and I've been using > rubyripper in an attempt to get a "perfect" rip... :)
Don't have time for the full test now - however I unfortunately have to report that Rubyripper's "repair" strategy is flawed - comparing chunks again and again and again until they match. On damaged discs, you can get a match after 50 - 100 tries but it will still encode dropouts. At least it does specify where the problems were but it incorrectly reports the problems were repaired. They weren't, they just matched after X tries. It's just wording I guess - EAC will do the same thing but it reports a read/synch error then suspicious positions. -- Mark Lanctot 'Sean Adams' Response-O-Matic checklist, patent pending!' (http://forums.slimdevices.com/showpost.php?p=200910&postcount=2) ------------------------------------------------------------------------ Mark Lanctot's Profile: http://forums.slimdevices.com/member.php?userid=2071 View this thread: http://forums.slimdevices.com/showthread.php?t=35895 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/unix
