![]() When there is a CD in the drive, clicking on the displayed text causes it to change from the evaluated ripping destination expression to the expression itself. When there is no CD in the drive, this control looks like a disabled edit control with no text in it at all, but when you click on it, the expression for the ripping destination appears seemingly out of nowhere, allowing it to be edited. I almost gave up on it at first until I realized that in the combo box below the track list, you could click on the text and edit a destination expression for the ripped files, which then becomes the default for future rips. It automatically avails itself of the CUE sheet and correction facilities of CueTools during the ripping processs. CUETools and CUERipper save this log as a file with the default name format: filename.accurip(but this name formatcan be changed if you want). I don't have dbPowerAmp though, since I'm a cheapskate.ĬueTools also comes with the CueRipper program, which does a darned good job of secure-mode CD ripping. This page shows an example of the CUETools Verification Log (verbose)along with some tips on how to read it. CueRipper is now my preferred CD ripping choice. I'd been using EAC for well over a decade, but with CueRipper, the only thing I needed to do for program configuration was edit the text in that combo box to set the destination for the ripped files. PerfectTunes finds one corrupted file (it is indeed corrupted), but still reports the album as Accurate. ![]() I'd never seen a UI having a combo box without a separate edit control in which you can actually edit the text, or one in which the text changes to something different when you click on it. It's very strange, but once you figure it out, it's about the only essential configuration needed that isn't done automatically. ![]() Here is the CueTools verify log with the repaired files:ĬueTools also comes with the CueRipper program, which does a darned good job of secure-mode CD ripping. The repaired file is now identical to what is in the AR database compared against rips other people made with different drives with different offsets. I answered my last question, I just forgot to update the thread. I understand they did fix mistakes in early CDs that would be "silent" revisions, ie no indications on the artwork or disc art. It's not an early pressing CD but one that came out around 2008. It's a digital error, it might look analog because of the huge amount I've zoomed in. ![]() Is there another way to objectively know in cases where this PRE flag isn't set? cue file, the CD did not have that "FLAGS PRE" turned on!Īs I said, I hadn't heard of pre-emphasis before and I've only read a few things on it but if the above quote is correct, I'm not sure how someone could be certain that they don't have some "bad" rips in their collection, aside from the subjective "this sounds harsh" test. He sent me some samples and to me, the tonality was that of pre-emphasis applied yet when I checked with him and the. I was inspired to write this because a couple weeks ago, a friend wrote to me that he finally got around to ripping some old CDs and he had an old Spandau Ballet Truth CD that just "didn't sound right" when copied to his music server. One wonders if in some instances, this might represent a subset of the complaints around early CDs sounding too "thin". To make matters worse, there are CDs that appear to have pre-emphasized content but did not bother to turn on that PRE flag! This results in highly "tinny" and harsh playback.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |