Well, when that happened, I was using
Drive has 'accurate stream'
drive caches
drive is capable of C2 retrieval
'Use c2 error info for error correction' was not checked.
I understand that I'm already taking some risks by checking 'drive is capable of C2 retrieval' as few drives that claim this actually manage to produce accurate C2 info (so I've heard). But I figured that I have nothing to lose now, and checked 'use c2 error info' as well. Now EAC seems to be making some progress, going to 73% of the track and still using only two lines of EC (whereas in the last rip it had already got 'read error' and 'sync error' and I gave before 70%)
Do I stand a chance of getting vaguely accurate rips this way? Or am I screwed and should be just using fast / burst mode?
What bugs me is that in fast / burst mode, you don't even get a report saying which part of the track is flawed, so you have to look through the whole track when doing glitch removal. Any way around this?