#Rip frameio update

I understand what you mean about the accurate rip database, but I have many CDs which are not found in that database.Here i have frame-relay network running RIP protocol, currently too many weird things happening in thise scneario.let see one by one,įirst i make a frame-relay network all three router has end to end ip connectivity, after that i start rip protocol on all three routers but didn't see any router sending update by viewing debug ip rip cmd.i did google search some of them saying run rip on interface level and some other saying use neigbour cmd on hub router then running rip by interface level router1 (hub) start sending updates i did the same thing on r2 and r3 now both spoke router can able to ping hub router loop interface, but router1 not ping to spoke doesn't has any rip route. So, dB was seeing ghosts.Īnyway, thanks you all and let me know if there is a way to test the accuracy of my drive's c2. But before finding this out, we could have safely supposed that the problem was in dB, not in EAC, because there cannot be errors in tracks verified as accurate. Maybe dB should improve the way it detects drives?). Now we know it was some problem caused by the fact that the drive was in an external case, via USB (and we still should understand why dB had this problem and EAC did not. With that same good CD dB found errors and made the frames countdown. With a good CD it was fast, there was no error, and the tracks were verified as accurate. How can I know that EAC had no problems? Because it did what it was expected: with a scratched CD it was very slow (particularly if in high error recovery mode) and gave of course no accurate rip result. So I thought that a result of accurate 200 was very inaccurate and I could not rely only on it.Ībout C2, if Spoon knows how I can find out how good it really is my drive in c2, I would like to test. Now, a quick mea culpa, I thought that accurate 1 was better than 200. I have done that same CD and there was no frames countdown now. Now a 75kb cache was detected and no FUA. There was no detected cache, and the FUA had been detected and was active. Which shows that the same drive does not perform the same when directly internal in sata or external in usb.Īnd it is not only a matter of amount of data.įor example, take the screen 2 a few posts above. With surprise some results were now different. Ok, I have installed the dvd again inside the notebook, after all in this moment I am ripping a lot and it makes sense to have a better performance on the dvd than on the HDD.Īnd I have done all the detecting on dB again.

I think dB is doing something very wrong there. I have now tested the same song once again with EAC and changed the recovery option to high, and it ripped the song in 1 minute 20 seconds.

I had to set its error recovery option to low. I really cannot imagine why should it make a 22000+ frames countdown of one hour for one song which EAC rips in 3 minutes, and we all know that EAC is quite paranoid with errors. Thanks for the link, I had read the help file but not seen that one.ĭo you think it may be that dB did not detect my device correctly? I do not feel secure with only relying on AR database. I do not want any fanatic paranoid accurate ripping, but I want a secure one. This is going to be my only rip before I sell or give all my CDs. How can I know how accurate is the c2 of my drive?Īnyway, yes, deactivating c2 all is good, but, hey, it only relies on accurate rips database to tell me it is ok, and with a confidence of 200!!! Or of 20 with pressing offset -664. Yes, all what I have ripped (in eac or dB) which was non scratched gave accurate rips with good confidence generally below 10.Īnd about c2, eac had no problems with c2 active, I do not see why should dB.

Rip frameio