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: Secure Ripper Test (part 2 concise results) (Read 143013 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Secure Ripper Test (part 2 concise results)

Reply #1
can dMC be configured as to what consitutes an AccurateRip match? Is a match of 1 good enough for dMC to stop the ripping process? I would like to be able to configure this option personaly.

BTW, the ripper is working wonderfully Spoon. Im sure its going to replace EAC, especially with AMG metadata support.

 

Secure Ripper Test (part 2 concise results)

Reply #2
Is R12 released or is this just more propaganda? 

Latest news on dbpoweramp.com is about m4a codec pack.

Secure Ripper Test (part 2 concise results)

Reply #3
Is R12 released or is this just more propaganda? 

It is not officially released yet, dMC r12 is available in alpha-version. Just follow this link that Spoon provided in post #1 of this thread.

Secure Ripper Test (part 2 concise results)

Reply #4
My initial tests give me mixed results when compared to EAC with my various drives.

One thing I can say is that it can't touch the performance that I get from Plextools with my PX-716A with the discs I have tested that are defective enough to give errors but not too much that an accurate rip isn't possible.  It seems that EAC does a better job with this drive also.

I have a rebadged Plextor that EAC does not report as providing C2 information yet R12 says it does though using it gives bad results.  I have another drive that provides C2 pointers to EAC but gives in returns an error when checking the option in R12.

If I could get a detailed explanation of how Ultra Secure Ripping and the various options work, I may be able to perform more efficient tests.

EDIT: I think the performance of R12a4 is very encouraging.  Also, I'd like to know exactly what the program is doing when dealing with bad frames.



Secure Ripper Test (part 2 concise results)

Reply #7

EDIT: I think the performance of R12a4 is very encouraging.  Also, I'd like to know exactly what the program is doing when dealing with bad frames.


http://www.dbpoweramp.com/secure-ripper.htm

XX (user configurable) tries on bad frames or until 10 match. 

Secure Ripper Test (part 2 concise results)

Reply #8
Sorry for the delay I was away.

The re-ripping of bad frames should be the same in EAC as dbpoweramp, and even plextor - there is only one show stopper there and that is the CD cache - you have it configured correctly?

Unlike EAC with dBpowerAMP R12 if the drive supports c2 pointers then have the c2 pointer option checked, it will help identify bad frames. If your drive has a good c2 implementation and you are happy with it then have no ultra passes (it will be just like plextools then), for a poor c2 implemented drive have atleast 2 ultra passes.

What settings are you using?

Secure Ripper Test (part 2 concise results)

Reply #9
there are not any differences in r12 and eac when using accuraterip without c2 correction right??

based on the flowcharts they seem to be doing the same thing or am i missing something?

Secure Ripper Test (part 2 concise results)

Reply #10
hey spoon I have what appears to be a qsi bw242u cdrw/dvd drive in my dell 5150 inspiron laptop and eac detecs c2 error correction and i havn't been able to get R12 to detect it at all.  Does anyone know if theres a sure fire way to test or find this information out? thanks.

Secure Ripper Test (part 2 concise results)

Reply #11
Hey Spoon,

The AccurateRip results look very promising. My concern, however, is what does dMC do with regard to gap detection and what is in the gaps? Half my reasoning for using EAC is I can get a perfect copy of a CD in FLAC, including all the gaps between tracks: can dMC do this too?

Thanks,
smiler

Secure Ripper Test (part 2 concise results)

Reply #12
gaillard

>based on the flowcharts they seem to be doing the same thing or am i missing something?

They are fundamentally different, in that dBpowerAMP works on complete passes where EAC works on small chunks.

If a drive supports C2 then you need a CD with scratches and a c2 error pointer should be flagged when doing the test. Your windows log on needs admin rights to read c2 from the cd drive.

smiler

Every CD ripper includes the gaps, that is how they work, you need special code to detect and remove the gaps.

Secure Ripper Test (part 2 concise results)

Reply #13
Is there any reason eac, cdspeed, and nero info detect c2 from the same cd but R12 doesn't?  does that mean if i were to rip that cd with r12 it isn't using c2 correction (anyway to test that?)

Also spoon i posted on your forums about the wavpack command line in r12. I can't get it to work with "-h - [outfile]"
"-h [infile] [outfile]" rips and encodes to 99% and then freezes.  wavpack_debug just says the three arguments like this.

arg 1: -h
arg 2: C:\DOCUME~1\JONATH~1\Desktop\SARAHB~1\SARAHB~3.WAV
arg 3: C:\DOCUME~1\JONATH~1\Desktop\SARAHB~1\SARAHB~1.WV

thanks spoon, your a great help

Secure Ripper Test (part 2 concise results)

Reply #14
can dMC be configured as to what consitutes an AccurateRip match? Is a match of 1 good enough for dMC to stop the ripping process?


I would love the answer to this question too if you don't mind spoon. I believe in your specs you said a confidence of 5 could be a good start but what is the program set on?

Secure Ripper Test (part 2 concise results)

Reply #15
Is it possible to rip the CD as an image+cue? I think AccurateRip doesn't support it.
I have all my CDs as images+cue and would like to keep it that way, though.

Secure Ripper Test (part 2 concise results)

Reply #16
Wavpack command line is:

-i -y -w "artist=[artist]" -w "title=[title]" -w "genre=[genre]" -w "album=[album]" -w "year=[year]" -w "track=[track]" - [outfile]

----
Images are currently not supported, but when they are they will work with AccurateRip.
----
Currently ripping will finish with a single confidence match with AccurateRip (unless C2 pointers are enabled and there is a C2 error)

>qsi bw242u cdrw/dvd

You know I hate that drive  it is purged from AccurateRip for having different offsets with either firmware versions or drive revisions.

About C2, dBpowerAMP uses a cd read call using MSF rather than LBA, it could be the firmware of that drive does not support c2 and MSF addressing.

Secure Ripper Test (part 2 concise results)

Reply #17
hey spoon,

I just updated the firmware to u27 from u25 on that qsi 242 drive and now pretty much every cd the program reads just says can't read cd.  But it will now detect c2....

do i just need a new drive?


Secure Ripper Test (part 2 concise results)

Reply #19
If I get the plexor 230A (any reason i shouldn't? or better for that price range?) will it give that error the same as my qsi 242 does now? that the cd can't be read.  I understand if it finds the errors, and i want it to if there are there but shouldn't it still be able to read all cd's???

Secure Ripper Test (part 2 concise results)

Reply #20
ok i got the plexor 708a dvd drive for this new software.  I don't see why people on hydrogenaudio are not making a bigger deal of this.  With Eac, if there is an error on the disk that repeats on the re-reads then your files will have errors in them! and if you enable c2 with eac then its soley reliant on c2.  This software will use c2 and then re-reads for things that c2 misses.  Thats as good as it gets right?

maybe there is just something i don't know...

Secure Ripper Test (part 2 concise results)

Reply #21
With Eac, if there is an error on the disk that repeats on the re-reads then your files will have errors in them! and if you enable c2 with eac then its soley reliant on c2.  This software will use c2 and then re-reads for things that c2 misses.

If EAC detects the error from a C2 pointer and the error is consistent (it repeats), your file is still going to have an error because C2 is not used during re-reads.

If EAC's using C2 pointers and an error is missed it will be passed along since no re-reads will take place since EAC's detection of errors is, like you said, solely reliant on C2 pointers.

EDIT: Anyway, this topic is about dBpowerAMP not EAC.  To steer this portion of the discussion back on topic, it seems as though spoon's ripper has "Advanced code to detect when drive is interpolating and hiding errors."  Does this mean that it also has some immunity to consistent errors that EAC doesn't have?  It seems as though EAC has no immunity.

Secure Ripper Test (part 2 concise results)

Reply #22
well just the fact that this ripper uses re-reads even if c2 doesn't report an error is a dramatic improvement.

I think i read in his technology preview that it said it also used c2 IN the re-reads as well...

As far as i know c2 is the protection against consistent errors and re-reads is the protection against inconsistant, which is why it makes sense to me to use them both whereas plextor tools and eac don't... correct me if i am wrong spoon about c2 erros mostly being consistant.

Secure Ripper Test (part 2 concise results)

Reply #23
Think about the worst case of c2 (in its usage in dBpowerAMP, EAC is different), perhaps you have a case where c2 is reporting an error which is not there - dbpoweramp will go through the process of re-ripping (that sector) around 40 times, if the CD is in accuraterip it will verify correctly at the end.

If a error slips past c2 undetected the re-read (programmable times) will hopefully pick it up.

so yes, this implementation of c2 is designed to be as good as it gets.

Secure Ripper Test (part 2 concise results)

Reply #24
I think i read in his technology preview that it said it also used c2 IN the re-reads as well...
C2 is not used during re-reads with EAC.
As far as i know c2 is the protection against consistent errors and re-reads is the protection against inconsistant, which is why it makes sense to me to use them both whereas plextor tools and eac don't...
A C2 pointer may spot an inconsistent error but upon re-reads, EAC will likely consider the consistent error good.

Again, EAC offers very little (if any) immunity to consistent errors.  This is one instance where spoon's new ripper has the opportunity to offer some significant improvement.