1. Because I'm on 64bit Linux I'm using Rubyripper. Because of this I haven't found an exact way to check my read offset.
The drive is a HL-DT-ST DVDRAM GSA-H44N RB01

I've read the accuraterip database and didn't find the exact drive. But it seems that an read offset of 667 would be correct?

2. Since space is an issue I ripp all of my cds to ogg. So far I've choosen quality 6 but thinking about using quality 7 instead. I personaly don't hear any difference (though I don't have a good soundsystem or hearing =) ). But some of those I share my ripps with may. I would like to know if there are anyone that hears any difference (preferably with a good soundsystem)?

Thanks in advance!

Why exactly do you care about the read offset?

The short answer would be because it can be set in Rubyripper, so why not use it?

I don't consider that sufficient reason. There are very few valid reasons for wanting to set the read offset and I wondered which, if any, was yours.

So you say that there are no advantages in setting the read offset?
If so I thank you, because it would be one less thing to worry about =)

Is this is a 64-bit flavor an Ubuntu distro? just curious. If you read the Rubyripper website on Google code Accuraterip was accepted as a possible feature in the near future. The lead developer who has posted on this forum several times has not got around to implementing it though yet possible due to time constraints. Secondly the only way to determine what -q setting to use it perform an ABX test if you aren't sure. I personally think anything over -q 5 maybe over kill as that's what we recommend on Hydrogenaudio here. I personally use between -q 6 and -q 8 due to the fact that I can't ABX at those settings and I have a very large HD so space is not a constraint.

As HotshotGG said, Rubyripper may some day add support for AccurateRip. When that happens it will be important to have the correct offset, and at that time Rubyripper will also set the offset for you. Until then, don't worry about offsets.