You are right, the images contain the first pregap when extracting
with newer versions of BlindRead.
I didn't know that. Thanks for the info!
Unfortunately they don't give you any hints, why they changed that image generation (or have I missed something?).
Because not all drives can read out the first 150 sectors [-150..-1]
properly (or am I wrong?) I suspect, BR generates the data.
But what's the advantage then?
Truman, have you already tried to modify the 1st pregap data (BWI)?
Is it used by BlindWrite when recording?
Maybe they prepare BR to be 'PSX ready' (just kidding ).
However - I was using the old BlindRead v 18.104.22.168b, which introduced the alternative read method, as far as I know.
But even I had used the new version, I would have had an offset of 352800 bytes (I hope this is still an English sentence :)).
This would mean thousands of differences when comparing with FC.EXE.
But only the critical parts of the images (the bad sectors) differ.
So I wonder why you have got the same results with your FIFA-CDs.
The VSO team claims that the alternative read method would use a 'vendor specific read command'. If they read the disc as audio, why does this depend on the vendor? I far as I have heard here, there aren't different types of read commands. So why are there drives, not supporting BR's mode? Do they realize that it is illegal to extract data as audio?
A long time ago I e-mailed VSO because I wanted to know if they plan the implemention of an audio offset correction (just like EAC, but working with Mixed-Mode-CDs). Maybe I expressed myself not clear enough because they replied the following (general sense):
'Of course, BR is correcting the offsets, this is so important like tyres at a car.'
That time I was confused but meanwhile I suspect they meant the offset correction, performed on their special audio extraction.
Probable, they use the sync pattern "00 FF FF FF FF FF FF FF FF FF FF 00" to determine the offset value automatically.
If my presumption is true that would mean, drives which cannot overead either into the lead-in or into the lead-out, won't work in this mode (Otherwise BR wouldn't be able to retrieve some 'samples' (actually binary data), depending on the used drive).
My tool has code to automatically adjusts the way this command is sent to the drive, which is a reason (maybe) why it works regardless of the firmware change
Wow, really impressive. If the one way fails, your tool tries the next one until any method works? In the case of the UltraPlex, probable also the last try fails then :).
Btw: It is also very strange that the UltraPlex' subchannel extraction works only in combination with the alternate read method, otherwise BR claims 'unsupported' :confuse:.