INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: EAC offset creates error in MC  (Read 1355 times)

JONCAT

  • Guest
EAC offset creates error in MC
« on: July 06, 2004, 10:39:20 am »

I haven't done enough testing yet but initial observation:

I have an EAC test CD that tells me my Lite-On 811 DVD writer is +6 read offset. When I used that for ripping with MC I got a hard error and the rip cancelled; ASPI error. I kept getting errors on the last track after 16 re-reads. Once I removed the offset my rips complete 100% percent @ 10x on Secure.

Any thoughts?

thanks
JC

Logged

Roar

  • Regular Member
  • Recent member
  • *
  • Posts: 42
Re:EAC offset creates error in MC
« Reply #1 on: July 06, 2004, 11:51:32 am »

I believe that the EAC offset is measured in samples while the MC offset is measured in sectors a.k.a. frames - each sector consists of 588 samples or 2352 bytes (2 channels at 16 bits equals 4 bytes).

When you use a +6 sectors offset in MC it corresponds to using a +3528 offset in EAC; this is clearly not what you want and is prpbably the source of your problem, since MC is trying to read 3522 (3528 - 6) non-exisiting samples from the end of the last track.

My personal opinion is that the read offset setting in MC should either be removed, or changed to be samples instead of sectors, in order to be actually useful - otherwise problems such as this will arise for people who assume that the offset is measured the same way as in EAC or PlexTools.

BTW I also got bitten by this assumption, but since my Plextor drive has a +99 read offset, the 99*588 samples offset used by MC amounted to 1.3 seconds, so I could hear that the start of some tracks were appended to the end of the previous track! ...so I changed the offset back to 0, and I suggest that you do the same.

- Roar
Logged
Pages: [1]   Go Up