According to the band's website, that album was released in Canada/US on 2008-03-27, but every retailer I find has it listed as 2008-03-25, 27th is a Thursday, 25th is a Tuesday.
2009-01-30 03034, 2009
navap
Who do I believe :p
2009-01-30 03051, 2009
warp
bands are not generally involved much in getting cds into stores, i'd trust the retailers.
2009-01-30 03008, 2009
navap
Okay
2009-01-30 03025, 2009
warp
(personally, i wouldn't be bothered by the two day difference :)
2009-01-30 03029, 2009
aCiD2
warp: with dnb, releases are usually on mondays, so it's simple for me, when in doubt, round down :)
2009-01-30 03033, 2009
warp
:)
2009-01-30 03006, 2009
nikki
I usually go with the usual day of release for that country if I have to choose, it's quite easy to be off by a couple of days
2009-01-30 03009, 2009
Milosz joined the channel
2009-01-30 03024, 2009
Milosz
hmm hibernate is broken too
2009-01-30 03025, 2009
rjmunro has quit
2009-01-30 03048, 2009
aCiD2
pronik: ya there?
2009-01-30 03029, 2009
navap
If a doc is part of the OfficialStyleGuideline s, does that not mean it should be reviwed?
2009-01-30 03021, 2009
pbryan
warp: so, my detailed analysis of cdparanoia is complete.
2009-01-30 03049, 2009
warp
pbryan: ah, did you find anything interesting?
2009-01-30 03054, 2009
pbryan
I did indeed.
2009-01-30 03031, 2009
pbryan
So, cdparanoia < 10.2 should probably be avoided. It seems to be easily fooled by caching drives.
2009-01-30 03003, 2009
pbryan
With scratched discs, I have seen both cdparanoia and EAC get different results, even with repeated reads.
2009-01-30 03029, 2009
pbryan
For 99% of cases, cdparanoia and EAC read tracks identically.
2009-01-30 03030, 2009
ojnkpjg
were they consistent on a per app basis?
2009-01-30 03047, 2009
pbryan
Per app basis?
2009-01-30 03049, 2009
pbryan
Yes.
2009-01-30 03054, 2009
ojnkpjg
that's interesting
2009-01-30 03009, 2009
pbryan
But what I found the most interesting is this 1%.
2009-01-30 03015, 2009
ojnkpjg
there's one track on one cd i have where there are consisently differences
2009-01-30 03017, 2009
ojnkpjg
really weird
2009-01-30 03019, 2009
ojnkpjg
i can't work out why
2009-01-30 03034, 2009
pbryan
In 1% of the cases, where there is near silence, cdparanoia and EAC act differently.
2009-01-30 03036, 2009
pbryan
Example:
2009-01-30 03048, 2009
ojnkpjg
cdparanoia and dbpoweramp produce the same rip
2009-01-30 03049, 2009
pbryan
08 00 08 00 09 00 09 00 08 00 09 00 ...
2009-01-30 03053, 2009
ojnkpjg
eac and plextools pro produce the same rip
2009-01-30 03059, 2009
ojnkpjg
all rip the track the same way consistently
2009-01-30 03031, 2009
pbryan
In all cases, we're talking about samples that are 0x08 or 0x09.
2009-01-30 03037, 2009
ojnkpjg
hm, i should check mine
2009-01-30 03040, 2009
ojnkpjg
that seems familiar
2009-01-30 03051, 2009
pbryan
And, EAC and cdparanoia either add or remove the value 0x01 randomly from these.
2009-01-30 03028, 2009
pbryan
When there's true signal, it's always identical.
2009-01-30 03036, 2009
pbryan
(between EAC and cdparanoia).
2009-01-30 03001, 2009
pbryan
BTW, I've been testing with a bank of 6 separate drives from different drive manufacturers.
2009-01-30 03025, 2009
pbryan
My conclusion is with a single drive, you can't trust EAC or cdparanoia to get a secure extraction.
2009-01-30 03026, 2009
warp
haha, wow
2009-01-30 03037, 2009
pbryan
You need multiple drives to conclusively get a result.
2009-01-30 03009, 2009
pbryan
I've already internally modified my script to not only extract, but then allow me to cascade a disc down the chain of drives to verify.
