by ehart » Tue Aug 11, 2009 4:45 pm
I haven't been able to get EAC running on my machine. I'm sure it's possible, but it's a confusing, powerful piece of hacker-ware in my opinion, way beyond what most of normal users like me want to think about. For that reason, I think implementing a small subset of EAC functionality in MM is very worthwhile.
The simplest answer would be to offer two checkboxes in MM. One that just reports/logs errors (including the track and time offset of the error), with a further option to continue or stop on errors. That way the person would know they need to listen to a bad track and decide what is needed (the error log could even give a click box to listen to 10 seconds before and after the error - simple). Maybe nothing is needed - most errors aren't audible. If they later want to run EAC to try to recover the CD, go for it. But the first task in MM is just to let the user know that the copy wasn't perfect.
To go a step further, MM could also implement a checkbox that turns on "secure" ripping. This would implement an EAC-like functionality using common defaults. If people want lots of settings and tweaking, let them use EAC. If a CD can't be ripped error-free - eject it with a message, and again, let the user try EAC if they so desire.
So my thought is -- let the user know if there are errors, and even possibly implement basic "secure ripping" functionality. This prevents a user from wasting hundreds of hours ripping CDs that later turn out to have errors. For advanced functionality, let the user use EAC.
Cordially,
Eric Hart
I haven't been able to get EAC running on my machine. I'm sure it's possible, but it's a confusing, powerful piece of hacker-ware in my opinion, way beyond what most of normal users like me want to think about. For that reason, I think implementing a small subset of EAC functionality in MM is very worthwhile.
The simplest answer would be to offer two checkboxes in MM. One that just reports/logs errors (including the track and time offset of the error), with a further option to continue or stop on errors. That way the person would know they need to listen to a bad track and decide what is needed (the error log could even give a click box to listen to 10 seconds before and after the error - simple). Maybe nothing is needed - most errors aren't audible. If they later want to run EAC to try to recover the CD, go for it. But the first task in MM is just to let the user know that the copy wasn't perfect.
To go a step further, MM could also implement a checkbox that turns on "secure" ripping. This would implement an EAC-like functionality using common defaults. If people want lots of settings and tweaking, let them use EAC. If a CD can't be ripped error-free - eject it with a message, and again, let the user try EAC if they so desire.
So my thought is -- let the user know if there are errors, and even possibly implement basic "secure ripping" functionality. This prevents a user from wasting hundreds of hours ripping CDs that later turn out to have errors. For advanced functionality, let the user use EAC.
Cordially,
Eric Hart