Pre-emphasis + IBM PC audio differences

i've uploaded a small (200kb) track here:
http://www.mediafire.com/?ungg3vtyyzx

could somebody compare it with the same track from Vigi's versin, please?

I've added DCP and PRE support. Cuesheets so far are generated without flags, I'll fix this later.

I don't think any of my AITD discs have PRE (only wipeout and some others, and I mentioned it each time in the comments).. I compared my aitd2 start to your file and they are different.. your dump has some data in the pregap and mine doesn't (also the data after the pregap starts with different bytes etc).

On another note, my alone in the dark dumps also come from a square black trilogy box (I also had a separate copy of AITD1 and it was identical).. I don't think the naming that you used is appropriate, because they should be identical to the normal versions (strangely enough your dumps don't match mine).. so my box just contained 3 jewel cases with the normal games with normal covers etc.. I'm not sure about yours.

And I don't know why these 2 http://redump.org/disc/2883/ + http://redump.org/disc/1706/ don't match.. could you upload a sample (.bin compressed in rar plz) of one of the audio tracks so I can compare?

I think we will run into this problem more often with IBM (same data track crc + different audio track crc's).. so maybe an "intelligent checksum" that only calculates the checksum of the data start and end is a better method for comparing audio tracks after all.

Also, it's possible that IBM discs have a +0 write offset on the data track but a different write offset on the audio tracks, so plz be sure to use the classic offset detection method!

The difference between alone in the dark 1 appears to be an offset difference of 3604 bytes (or +901 samples).. also, in my dump, because the track data is shifted forward compared to your dump, each track starts with data from the previous track in the pregap

Maybe our current methods just aren't able to detect the real write offset of these older IBM discs that show +0 write offset?

ps. do your AITD1 tracks also start with a click?

Also, I noticed that your trilogy dump has the same audio sizes as your budget dump.. have you compared the 2? It looks like for the trilogy one they just took the complete track of the original release, including the gaps and then just mastered them without any extra gaps..

I'm wondering what the best way would be to deal with these differences.. the 'intelligent checksum' comes to mind again... the disadvantage would of course be that we wouldn't be able to identify the real reference point (the position of the data before any mastering, like in PSX), but I doubt my original edition discs are the ones providing the real reference point, because your budget discs don't have data entering into the next track's pregap.

Telstar compared to Trilogy
Track | Telstar offset diff from LBA | Click Tel / Tri | Data diff (ignoring $00)
03      |-3920    | click / don't  | first 16 bytes differ
10      |-3908    | click  / click  | first 16 bytes differ
11      |-3948    | don't / don't | match
12      |-3912    | don't / click  | first 16 bytes differ
13      |-3916    | don't / don't | first 20 bytes differ
14      |-3900    | click  / don't | first 16 bytes differ

i removed gaps and to align audio data Telstar had to be corrected by the opposite amount of bytes given in 2nd column (Telstar is closer to 0 offset; i guess it means that Trilogy is maybe more similar to yours). though close, it's still different for every track. and then, when binary compared, still some bytes would differ. it's strange.
i hoped, there would be some similar audio tracks for SegaCD/PCE but for the same games they were different - remastered and quite a lot. but this is different, only a few bytes do not match.
it's a good thing you noticed clicking, it looks like it's in those 16 bytes. maybe they were trying to remove it or something; but then they still failed sometimes.
to be hones, i don't know what to think. i hope, this may be an exception, and rare one also.
...
ya, i checked offsets on other drive, they're still the same.
...
and i thought at first that this offset difference is maybe because EAC can't position correctly. but it's not. when Alcohol's .img is sliced in tracks and then compared to EAC, the difference - it's always the drive's offset, always the same.

ok, no more budget from me

Well.. usually it's just a cheaper version of the game, rereleased by another label..

The problem with these budget releases is that they usually have a data track that's remastered.. essentially it contains the same data as the original version, but usually with some small modifications (if the filedates are newer than the release date of the original I think it's better to wait for the original version dump and see if it can be verified).. I also have some budget releases and I got mixed results.. Mortal Kombat 3 had exactly the same data as the original version, so I was able to verify it.