Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: DAEMON mounted image -> EAC OR Straight CD -> EAC? (Read 6133 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

DAEMON mounted image -> EAC OR Straight CD -> EAC?

Hello everyone!

Although this is my first post, I have been a long time reader here on this forum. This place has been a great help to me and is the source for most of my audio encoding knowledge. So thanks to you all. 

Now for my question:

I have been randomly converting some of my CD collection to MP3 and there are two methods I have been doing it by. Basically all I want to know is which ripping method of mine is better and why.

:::METHOD ONE:::
1) Insert Audio CD into DVDrom drive
2) Rip directly from DVDrom drive to wav files with EAC using all the best settings.

:::METHOD TWO:::
1) Insert Audio CD into DVDrom drive
2) Create an Image with any burning program (I use Alcohol)
3) Mount the image to a virtual drive with DAEMON Tools
4) Rip from virtual drive to wav files with EAC using all the best settings.

Can anyone shed some light on which method of mine is better? Or are they exactly the same and therefore produce the same results?

All I know is that with method two it seems to run alot smoother since it is reading from the hard drive instead of the CD. But i'm not sure is thats a good thing, bad thing, or doesn't make any difference... 

DAEMON mounted image -> EAC OR Straight CD -> EAC?

Reply #1
Method two is not secure. Once the image has been ripped with Alcohol (which does no error checking), there's no way to detect/correct any errors. If you want to benefit from EAC's secure ripping features, it has to rip directly from the CD drive. http://www.hydrogenaudio.org/forums/index....showtopic=33727

DAEMON mounted image -> EAC OR Straight CD -> EAC?

Reply #2
uhm, what's the point? Once you have the disc imaged on your drive you don't have to "rip" again with EAC... EAC's job is already done (poorly - by Alcohol). The conversion from disc image to wave is not the problematic part, its the reading of the image OFF the physical media that is a problem because of the inherent lack of error correction in CD-audio. Once you have a good image, you could mount with daemon tools and rip with freaking Windows Media Player if you want - hard to screw up at that point!

DAEMON mounted image -> EAC OR Straight CD -> EAC?

Reply #3
I don't think CD-Audio has worse error tolerance than than any other CD format just that software/hardware implementation are poor & mostly not even present.

DAEMON mounted image -> EAC OR Straight CD -> EAC?

Reply #4
Quote
I don't think CD-Audio has worse error tolerance than than any other CD format just that software/hardware implementation are poor & mostly not even present.
[a href="index.php?act=findpost&pid=300622"][{POST_SNAPBACK}][/a]

The error correction mode of Audio CD is very limited. It's a well-known weakness of RedBook format, and it have nothing to do with software or hardware readers. Otherwise, software like EAC Secure Mode, CD Paranoia routine or Test & Copy mode would be totally useless (i.e. explorer should be enough to rip unprotected audio tracks).

DAEMON mounted image -> EAC OR Straight CD -> EAC?

Reply #5
Quote
Quote
I don't think CD-Audio has worse error tolerance than than any other CD format just that software/hardware implementation are poor & mostly not even present.
[a href="index.php?act=findpost&pid=300622"][{POST_SNAPBACK}][/a]

The error correction mode of Audio CD is very limited. It's a well-known weakness of RedBook format, and it have nothing to do with software or hardware readers. Otherwise, software like EAC Secure Mode, CD Paranoia routine or Test & Copy mode would be totally useless (i.e. explorer should be enough to rip unprotected audio tracks).
[a href="index.php?act=findpost&pid=300638"][{POST_SNAPBACK}][/a]

The reason explorer doesn't detect errors is because it doesn't perform CIRC processing if it did like say PlexTools it could tell you exactly where an error occurred, that's my point.

DAEMON mounted image -> EAC OR Straight CD -> EAC?

Reply #6
If I'm not wrong, RedBook uses ~20 bytes per sector to insure data correction. CD-Rom uses more than ~200 bytes per sector (i.e. 15% of total block size) to do it. I suppose that people who choose to increase the total amunt of space dedicated to error correction didn't have in mind to waste space, and therefore that RedBook is clearly less robust than ISO9660 — PlexTools or not.

But I'm maybe wrong. We should ask to Pio2001, which is a real specialist

DAEMON mounted image -> EAC OR Straight CD -> EAC?

Reply #7
Quote
If I'm not wrong, RedBook uses ~20 bytes per sector to insure data correction. CD-Rom uses more than ~200 bytes per sector (i.e. 15% of total block size) to do it. I suppose that people who choose to increase the total amunt of space dedicated to error correction didn't have in mind to waste space, and therefore that RedBook is clearly less robust than ISO9660 — PlexTools or not.

But I'm maybe wrong. We should ask to Pio2001, which is a real specialist
[a href="index.php?act=findpost&pid=300648"][{POST_SNAPBACK}][/a]

You are not wrong and you know that very well

DAEMON mounted image -> EAC OR Straight CD -> EAC?

Reply #8
Quote
If I'm not wrong, RedBook uses ~20 bytes per sector to insure data correction. CD-Rom uses more than ~200 bytes per sector (i.e. 15% of total block size) to do it. I suppose that people who choose to increase the total amunt of space dedicated to error correction didn't have in mind to waste space, and therefore that RedBook is clearly less robust than ISO9660 — PlexTools or not.

But I'm maybe wrong. We should ask to Pio2001, which is a real specialist
[a href="index.php?act=findpost&pid=300648"][{POST_SNAPBACK}][/a]

But even with 20 bytes don't you agree that errors should be noticable?

My understanding is that CD-Audio data is encoded using Cross Interleaved Reed-Solomon Code, to perform error processing you need to decode this data in the correct fashion either by hardware or software then output to the user or application the status.

I would like to hear from Spoon or another developer who really understands how this works.

DAEMON mounted image -> EAC OR Straight CD -> EAC?

Reply #9
Quote
its the reading of the image OFF the physical media that is a problem because of the inherent lack of error correction in CD-audio.[a href="index.php?act=findpost&pid=300613"][{POST_SNAPBACK}][/a]

I have to disagree. To say that CD audio lacks error detection or correction is plain wrong.

If you think it's not adequate, just look at how well EAC is able to deal with most scratched CDs.

DAEMON mounted image -> EAC OR Straight CD -> EAC?

Reply #10
Quote
If you think it's not adequate, just look at how well EAC is able to deal with most scratched CDs.
[a href="index.php?act=findpost&pid=300654"][{POST_SNAPBACK}][/a]

EAC Secure and scratched CD is not necessary a good thing. Many users have noticed it. Extraction takes hours, and audible glitches could be more annoying that a simple burst extraction. I've also noticed it, with various drives.
Even when scratchs are not excessive, EAC let audible glitches. I have various damaged CD-Rom (even CD-R) and my datas are all readable (and quickly readble), without corruption.

In short:
scratched CD-Rom -> fast extraction and no corruption
scratched CD-A -> slow extraction and damaged audio data.

I suppose that a better error correction of data CD could easily explain that. No?

DAEMON mounted image -> EAC OR Straight CD -> EAC?

Reply #11
I agree that error detection and correction is better with CD-ROMs rather than with CDDA discs. No doubt about it.

Still, I have only one CD out of 130 or so that fails audibly with EAC. It works well enough for me, I guess.

DAEMON mounted image -> EAC OR Straight CD -> EAC?

Reply #12
20 bytes error correction per sector and 2352 bytes of audio data per sector.

Each of those bytes of error correction corressponds with over 100 bytes of audio data...

Put another way, even if you had 2352 bytes of error correction (for example an exact duplicate of the audio data), it is still possible for the exact error to be present on the two (audio data and correction), although this possiblilty will be tiny.

When people are testing cds, some will scratch or drill holes (or scratch off the data foil), the scratches will be harder for the cd drive to spot rather than holes as it is obvious when a hole is there there is no error correction.

DAEMON mounted image -> EAC OR Straight CD -> EAC?

Reply #13
The issue is, CD-audio discs weren't designed to be bit-perfect on an error, they were designed so that the error could be smoothed-over (made inaudible). That of course wouldn't work for data, where every bit is vital, so thats why CD-ROM has more (of a different kind of) error correcting code.

Don't forget that CD-audio is far older than computers with CD players, so the idea of a "bit-perfect rip" was't realy on the agenda at the time. And also because of that, this "smoothing-over" type of error-correction is also performed by most CD-ROM drives before they even let the system see the result! So that is why bit-perfect rips are difficult.

DAEMON mounted image -> EAC OR Straight CD -> EAC?

Reply #14
The CD-ROM (data) spec is governed by Yellow Book and is actually an extension to the Red Book standard for CD-Audio. The extension, among other things, covers additional ECC space that Jebus and Guruboolez mention. As far as extracting to an image and then using EAC, you have lost your ability to extract using a secure process from an unsecure medium (ie. Red Book).

In essence, to get a secure rip, you must perform the secure extraction from the actual CD-Audio disc, not from an unsecure, possibly not bit-perfect image of the disc. Red Book media + Secure Extraction = Secure Rip.

The following link clarifies the differences between Red Book and Yellow Book nicely...

http://www.samsungodd.com/eng/Information/...&no=8&type_no=3

Edit: typo