dbpoweramp says drive cannot read into lead out; different results with it on

[bhoar]

Re: dbpoweramp says drive cannot read into lead out; different results with it on

Noted, and thanks for your help :-)

If spoon/developers are reading, I suppose it's worth pointing out that EAC was working OK with the "Native Win32 Interface" option, which I guess is the same as dbPowerAmps "Windows Internal".

Actually, "Native Win32 Interface" is the same as "SCSI Pass Through", not "Windows Internal". So, you've set dbpoweramp to use the same method as EAC.

-brendan

[sjmac]

Re: dbpoweramp says drive cannot read into lead out; different results with it on

Noted, and thanks for your help :-)

If spoon/developers are reading, I suppose it's worth pointing out that EAC was working OK with the "Native Win32 Interface" option, which I guess is the same as dbPowerAmps "Windows Internal".

[bhoar]

Re: dbpoweramp says drive cannot read into lead out; different results with it on

Good to hear. SCSI Pass Through allows for the largest drive capability support and should be used whenever it is avaialble.

-brendan

[sjmac]

Re: dbpoweramp says drive cannot read into lead out; different results with it on

:blush:

Actually, not!

I had looked for that kind of option, but I'd been clicking the arrow next to the options button, not the actual button, so couldn't see most of the useful options.

HOWEVER - setting it made the problem "worse" - I got even more missing samples. Then I tried changing the Communication setting, and choosing "SCSI pass through" instead of "Windows Internal" has fixed my problem (tested in R13.1 beta).

[bhoar]

Re: dbpoweramp says drive cannot read into lead out; different results with it on

Is the checkbox "Read into Lead-in or Lead-out" checked for that particular drive in the dbpoweramp CD Ripper: Options dialog?

-brendan

[sjmac]

Re: dbpoweramp says drive cannot read into lead out; different results with it on

Hi,

I'm having this "missing samples" problem, tested with R13 and R13.1 - both reference versions, I think - I paid anyway ;-)

[edit:Solved my problem now; needed to click the Options button in dbPA CD Ripper (not the little arrow next to it!), choose Read in to Lead In or Lead Out option AND change the "Communication" option from Windows Internal [For Limited Accounts] to any of the other options except SCSI Pass Through Read(D8), which didn't work on my machine.

The screen grab below shows the issue. The windows on the left show a close up of two .wavs extracted using Exact Audio Copy from CD on two different computers. On the right is the same track extracted using dbPowerAmp R13. Top right is extracted from a Daemon virtual drive with an image from EAC mounted (looks fine, identical to EAC extracted data), and the bottom right is extracted using dbPowerAmp from the CD disk itself. Looks like 102 missing samples padded with zeros, even though EAC managed to read in to the lead out to get the actual data.



CD ROM Technical Details:
Manufacturer: HL-DT-ST
CD Drive: DVDRRW GSA-H30L
Firmware: S856
Serial: 07/02/08
Maximum Speed: 7056 KB/sec (x40)
Current Speed: 7056 KB/sec (x40)
Spin-down After: 32 seconds
Buffer Size: 2 MB
Accurate Stream: Yes
C2 Error Pointers: No
Reads ISRC: Yes
Reads UPC: Yes

OS is Vista Ulitmate x64 (64 bit)

[Porcus]

Re: dbpoweramp says drive cannot read into lead out; different results with it on

A maybe related problem, the Sony mediachanger, identifies as Matshita DVD-RAM SW-9584 B104, offset +102 -- dBpoweramp says it can read into lead out, but:

... but I don't think it can, I think this phenomenon is drive-dependent. Not able to reproduce it to the same extent elsewhere.

[Porcus]

Re: dbpoweramp says drive cannot read into lead out; different results with it on

A maybe related problem, the Sony mediachanger, identifies as Matshita DVD-RAM SW-9584 B104, offset +102 -- dBpoweramp says it can read into lead out, but:

I ripped all with lead in/out checked, and without. Removing those without AR entry or with all tracks inaccurate (different pressings), I were down to 115 discs.

-> Burst rip, lead i/o UNchecked: 97 discs clean, 18 discs with inaccuracies, of which 6 only in the last track.

-> Ultra-secure, lead i/o ON: These 6 inaccurate last tracks have now increased to 50. That is about half of the discs.

-> Tried these 50 discs with EAC, testing only the last track with lead i/o ON: The vast majority (say, 45 of those 50) were still inaccurate. Only a few were tested with lead i/o UNchecked, all of them accurate. Did not try EAC on the remaining fifty-something to see whether EAC produces inaccurates that dBp does not.


So it seems that on this particular drive, checking lead i/o will produce Inaccurate last track in about half the discs -- regardless of application.

Oh, and there are some noteable discrepancies in the AR numbers. A couple of discs have quite a lot higher Inaccurate confidence on the last track than Accurate on the rest -- I suspect coming from re-rips with different software, setting, or CD-drive -- but also a few discs with lower number on the last track. What is, plausibly, the explanation? Among the latter are
Audioslave - s/t - 13 tracks Accurate (131 to 134), 14th track Inaccurate (38).
Tori Amos - Scarlet's Walk - 17 tracks Accurate (62 to 65), 18th track Inaccurate (15).

[bhoar]

Re: dbpoweramp says drive cannot read into lead out; different results with it on

2 drives which cannot overread (with different offsets), even if the option is on or off, will always produce different CRCs on the last track.

Ah.

Addendum: in all cases with pristine and non-defective discs, the AccurateRip will continue to match, because the last 5 frames of the last track are never included in AccurateRip calculation.

This discarding of the last 5 frames is done specifically to work around issues such as those above that can never be resolved via software.

-brendan

[Spoon]

Re: dbpoweramp says drive cannot read into lead out; different results with it on

2 drives which cannot overread (with different offsets), even if the option is on or off, will always produce different CRCs on the last track.

[bhoar]

Re: dbpoweramp says drive cannot read into lead out; different results with it on

If spoon could write a concise summary of the cause of the problematic checksums related to the end of tracks on these special discs, that would be great.

-brendan

[pls1]

Re: dbpoweramp says drive cannot read into lead out; different results with it on

I did a perfunctory compare on a few of the other "last track different checksums" discs. As per EAC WAV compare, the discrepancy errors are all at the very end of the track.

Therefore, since all the drives continue to match accurate rip on popular discs, it seems from the various other posts here and at HA, that this is a known problem.

Unless Spoons has some other suggestions or requests, from my point of view, this is resolved as a known problem.

If I detect any consistent errors NOT at the very end of the track (as has been discussed here and elsewhere) I'll post them.

Thanks to everyone who contributed to my understanding of how this stuff works.

Phil

[LtData]

Re: dbpoweramp says drive cannot read into lead out; different results with it on

There, I edited the typo, now it is correct.

[pls1]

Re: dbpoweramp says drive cannot read into lead out; different results with it on

The differences occur in the EAC WAV compares between drive models are at:
4.25.316-220 for the 900 to 230 model compare

4.26.331-343 for the 900 to 755 model compare

4.26.316-332 for the 755 to 230 model compare

Typo in the first compare, obviously it should be
4.25.316-320

[pls1]

Re: dbpoweramp says drive cannot read into lead out; different results with it on

4.26.25

Hold the mouse over the file and dBpoweramp will tell the number of audio samples, is it the same for all files, what is it?

The 4.6.25 is what EAC showed.

I needed to re-run these tests because the default for meta-data ID tags in dbpoweramp does not have the attribute "length" checked.

When I re-ripped all three drives show the same: "Length: 266333"

The EAC wave compare show identical file for the same drive "Secure" and "Burst"

The differences occur in the EAC WAV compares between drive models are at:
4.25.316-320 for the 900 to 230 model compare

4.26.331-343 for the 900 to 755 model compare

4.26.316-332 for the 755 to 230 model compare

Phil