[progo]

Sorry if this has been answered already. I did quite a search with the keyword "accuraterip" and none was near my problem.

I'm using Linux so the offset reading test by EAC is not possible at the moment so I wonder if a value from this database is good enough? I've been ripping my cds with offset = 0 as I don't know the ill effects of incorrect offset. But might as well try to get the correct numbers in!

My player is by the way LG's USB DVD+/-RW / RAM. GSA-5169D. And I quite like it. And I rip my cds with rubyripper (it uses cdparanoia as back-end).

 

[ogewo]

accuraterip is very commonly used for determining a drive's read offset. your write offset, however, will require you to burn a cd that is listed in the accuraterip "key disc" database, and then have a program analyze it. feel free to skip that step if burning cds is not a priority, at least relative to ripping them.

 

[progo]

Oh, so it's two-way mechanism. I don't burn much anything so I'll cope with the read offset. Thanks for clearing this out.