I just started using grip to rip my cd's.
I have a BB King cd which has 21 tracks on it.
I select all 21 tracks to be ripped and encode to ogg. I start it up and it start ripping the tracks ok. It does tracks 1-16 ok, Then it come to track 17,
At this point is starts ripping the track then it shows it is ripping slower and slower and slower until it only at about 0.1x rate. Bascially it just stops ripping at this time, I have waited 30 minutes to an hour and it just can not get past half way into the song.
I have found other cds that do the same thing as mentioned above.

The track is ok if just played on a cd player be it linux or window or standalone.

I have taken the same cd and used cdex and it had no problem with ripping the track.

Any ideas as to what the problem might be.

Also I have read in other posts that I should be using scisc emulation. Why should I be doing this? What advantage is there in doing it that way?

I am by NO means an expert, but maybe you could try to run cdparanoia from a shell? I'm saying this because grip is a graphical user interface that hides the actual mechanics, and you're in a spot where you would want to look at the actual pipes and valves, right?

According to this cdparanoia FAQ there is clear feedback in case of errors - so try to get it running in a shell and see if you get any warnings that Grip hides/ignores.

Please note that playing a cd in an audio player is completely different than running it in a computer's cd drive -- commercial cd players can play rather deep scratches with minimal sound errors, cd ripping is a much more accurate process.

Psst! Here's how to run cdparanoia in a shell. :-D