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 145717 times) previous topic - next topic
0 Members and 5 Guests are viewing this topic.

Secure Ripper Test (part 2 concise results)

Reply #225 –
@singaiya

Normally CD drives do not vanish, unless they crash internally, could be c2 is not well supported on that drive...

It is hoped full release will be early January, certain features look as though they will be pushed back to perhaps R13 (image ripping perhaps can be handled on the DSP effects, the implementation is quite extensible).

Secure Ripper Test (part 2 concise results)

Reply #226 –
Hi!
Long time reader, and now first time poster.
First, thanks Spoon. Your secure ripper is really kicking serious butt.
However I have one question.
My drive is LG GMA-4082N (Shipped as Asus) and using latest firmware available, ripping with r12 alpha 8. Ripping results on one of my cds this weird thing on track three (Diablo's Eternium and track is Queen of Entity). Unfortunately I didn't save the log (CD is my girlfriends, who lives 370km away, so it's not possible to test again at the moment), but everything was okay except for one frame. Ripper says "Insecure (c2 dropped 694, best c2 matched)" and the crc is consistent for the track (AR says accurate, confidence 3) and there's no audible errors. The CD is copyprotected and is very rarely ripped as the max confidence was 4.
Settings: c2 enabled, secure with min of 2 and max of 6 ultra secure, end with 2 clean passes, re-read frames 700 times. it results the best possible quality for the cd on my setup (according to logs i've examined).
To the question, is it possible that the track is truly accurately ripped even though the ripper had to guess the frame or is it some minor beauty bug in the code? Or is it just me being paranoid again since one frame isn't that big of a problem? 
Hevay is The Way!
 

Secure Ripper Test (part 2 concise results)

Reply #227 –
With a c2 best match, there is no guessing going on, it is just that the required 8 matching frames were not achieved, so the ripper says, ok  lets trust c2 and in that case it obviously was good as the AccurateRip verified it.

If AccurateRip verifies your rip with a confidence of 2 or above then it is error free.

Secure Ripper Test (part 2 concise results)

Reply #228 –
Quote from: spoon on
If AccurateRip verifies your rip with a confidence of 2 or above then it is error free.
Why not with a confidence of just 1?

Secure Ripper Test (part 2 concise results)

Reply #229 –
There is a chance that the guy submitted his result previously so the result is his

Secure Ripper Test (part 2 concise results)

Reply #230 –
Just an idea, could you make it possible to rip the same (damaged) CD with multiple drives? Since different drives handle errors differently, some frames might be ripped OK with one drive, and some with another, so that could increase the chance of getting a good rip. IsoBuster uses this technique for recovering damaged data CDs.

This is probably too much too late to still be included (and I don't know how well it would work with audio CDs, or if people would use it), but I thought I'd share it anyway  .

Secure Ripper Test (part 2 concise results)

Reply #232 –
Quote from: spoon on
Everything is possible
Long time lurker de-lurking here...

Well, I read that as a 'post your strangest ideas' and so will I do :-D

I didn't believe it until I saw a friend of mine show it to me, but severely damaged CD (I mean deep scratches on the mirror side) can be repaired with a mix of fine-grained sandpaper and some kind of polish liquid which looks like the liquid they use to polish cars.

He took my U2-Zooropa CD that I had been considering dead for 10 years (and didn't care). Something really bad had happened to it 10 years ago and it was the worst deep-scratched CD I had ever seen. No player would even try to read it. My friend did his thing and five minutes later, the whole disk was accurately ripped with a rating of 20+ for each track. I repeated the operation on other scratched CDs and every resurrection was a success.

Now the downside is that the 'polished' and resurrected CD's lose they glossiness. They have a kind of white voil on them which isn't pretty to the eye (but just fine for laser beams, even el cheapo ones). I wouldn't dare to apply this method to CDs that are not mine.

So, my strange idea of the day is to add a visualization feature to the ripper, which would give us a visual clue of where the unrecoverable tracks are on the disc. For instance, the last CD I resurrected this way had its track 15 (on 17) unrecoverable. I wasn't able to say what the fatal scratch was, even by looking at the supposed section (which should have been, in that case, somewhere near the borders of the disc).

My limited knowledge of CD technology lends me to believe that track numbers can be mapped that way (think LightScribe, but inverse). It would be incredibly more useful that 'sector number 123456, 123478 and 12456 are unrecoverable and would allow us to perform 'surgical' scratches removal instead of polishing the complete disc.

Spoon, am I crazy?

Take care,
CPL593h

(Note: edited each time I find a typo or grammar error -- sorry )

Secure Ripper Test (part 2 concise results)

Reply #233 –
I think this would depend on the track pitch remaining within the standard.  Should work for most factory-pressed CDs, less likely to work for custom burned ones.

However, on factory discs I can usually tell where tracks start/end by looking at the disc under a bright incandescent light, and can definitely see the scratch in question above it. 

So I'm not sure how much good showing it graphically will do.

-brendan

Secure Ripper Test (part 2 concise results)

Reply #234 –
Quote from: bhoar on
I think this would depend on the track pitch remaining within the standard.  Should work for most factory-pressed CDs, less likely to work for custom burned ones.


Well, I suppose that people who want 'secure' copies will most likely work from original pressed CDs. Anyway since they are backup copies, I just trash them when they are scratched

Quote from: bhoar on
However, on factory discs I can usually tell where tracks start/end by looking at the disc under a bright incandescent light, and can definitely see the scratch in question above it. 

So I'm not sure how much good showing it graphically will do.

Well it depends on the kind of music you listen to. Most of the discs I listen to don't have a 'blank' between tracks, they just increment the number (live recording, classic rock music). For this kind of disc, this feature would be interesting, if possible of course.

Take care,
C.

Secure Ripper Test (part 2 concise results)

Reply #235 –
You might be able to tell from the % bar and the ripping position indicator, ie the total % bar is the start of the track in secure mode (as it sits at the start until encoding), and when reripping the red line shows where in the track it is, add the two together?

Secure Ripper Test (part 2 concise results)

Reply #236 –
Dare i request an option to shift the accurate rip offset by 30 samples to match the newly revised absolute offset? And possibly submit new rips to a parallel "corrected" database?
..... please?

Secure Ripper Test (part 2 concise results)

Reply #237 –
There really is no point, 99.99999999% of cds would not even have non-zero audio samples for those 30 samples, also many, many cds do not even start at the 30 offset, they are all over the shop.

Secure Ripper Test (part 2 concise results)

Reply #238 –
Quote from: spoon on
There really is no point, 99.99999999% of cds would not even have non-zero audio samples for those 30 samples, also many, many cds do not even start at the 30 offset, they are all over the shop.

Amen spoon!

What is the point in ripping 680 microseconds sooner when offsets between different pressings can be thousands of samples?

AccurateRip would ignore those 30 samples anyway, lol.

Secure Ripper Test (part 2 concise results)

Reply #239 –
Beta 1 Released

Beta 1 Released

Added Batch Converter (was called previously File Selector)
Added configuration option Folder right click 'batch convert'
Version numbers in configuration
Check for updates in configuration
bug fix: small screen resolution cd ripper leaving hidden txt boxes on screen
bug fix: massive fixes now compatible with Win9x (and possibly Win64)

Secure Ripper Test (part 2 concise results)

Reply #240 –
Hi first post here. you have been warned ;-)

Wanted to say that I am very impressed with this new version.

Its fast, it seems accurate and its very nice to use.

Could someone confirm that at present its not possible to do multiple format rips in one pass? (wav and MP3) I think this can be done in the current (non Beta) version.

Also I am struggling to understand the format of the Naming options for Ripped files, I can’t understand how they work in particular the [ifcomp] types when nested.

Ideally I want to do a single pass rip and produce 2 groups of folders, one holding .wavs and the other putting mp3’s into the standard iTunes folders.

Secure Ripper Test (part 2 concise results)

Reply #241 –
MAREO can be used (a native multi encoder will be released shortly in the new year).

[ifcomp]  is applied if a compilation and the section ends [] (off the top of my head),

Secure Ripper Test (part 2 concise results)

Reply #242 –
Hi Spoon

Can I start archiving my CD collection now with Beta 1 or are there still more improvements to come on the ripping side?

Thanks, and Merry Christmas to everyone!
David.

Secure Ripper Test (part 2 concise results)

Reply #243 –
CD Ripper is pretty much finished for R12.

Secure Ripper Test (part 2 concise results)

Reply #244 –
Out of interest, could AccurateRip compensate for the 30 sample difference? I think that I've seen somebody mention something along those lines, but I'm not sure.

Secure Ripper Test (part 2 concise results)

Reply #245 –
I was curious if it'd be possible to make R12 re rip the bad frames at multiple speeds. Say after 100 C2 errors dropped it kicks down to 16x, 8x, 4x and so on.

EAC gradually slows down the drive upon an error, and I noticed this gives me better results with my LG drive.

Now I can set it to re-read at 4x, 8x etc, but I've noticed some cds rip better at different speeds, and some cds make the drive stop responding after a while when I set it for a lower speed.

Secure Ripper Test (part 2 concise results)

Reply #246 –
Even if the 30 samples were NULL (ie silence) the crcs would be different.

------

If 4x rips best on your drive for errors, then set to use that all the time. Varing the ripping speed on re-reads will only increase the number of errors IMHO.

Secure Ripper Test (part 2 concise results)

Reply #247 –
Great ripper spoon - I finally got rid of EAC and am using your software only.

OT: Any chance you could add an option for lowercasing, uppercasing, sentence-casing (first letter of first word uppercase, rest lowercase) or word-casing (first letter of each word uppercase, rest lowercase) the titles?
Also, I find it a bit annoying that in title editing mode, the text-box moves to the left.

Secure Ripper Test (part 2 concise results)

Reply #248 –
Well, one thing's for sure and that is that i am extremely jealous on you guys for being able to use this "seems to be" absolutely fantastic piece of ripping software 

;Waiting patiently for Spoon to add image ripping capabilities to the R12 ripper

CU, Martin.

Secure Ripper Test (part 2 concise results)

Reply #249 –
Hi Spoon,

This ripper is fantastic and I have also replaced EAC with it. I only have one issue with it so far. The metadata from AllMusic has the album year with the date after it (2004 03 23). In the ID Tag Options one is allowed to "Force no date on year (ie 2004 not 2004 03 23). I use this option as I don't want the date, just the year in my audio file's ID tags. This doesn't apply to the file structure naming though. If I use [year] in the file name setting for directory making purposes it adds the date after the year. I'd like an option to be able to truncate the date from this as well. Otherwise, fantastic ripper and it also works well in Ubuntu with Wine.