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: CUETools versions 1.9.5 through 2.1.6 (Read 1906490 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #525 –
Hey.  Hopefully this problem hasn't been posted already... reading through hundreds of posts just to find out does not seem fun =X

I have a rip of a CD that, when run through Accuraterip, gives me the following report:

Code: [Select]
[Disc ID: 0010513d-008297e5-780a1c0a]
Using preserved id, actual id is 00105b7a-0082e023-8e0a200a.
Track	[ CRC    ] Status
 01	[556083d0] (00/09) No matches
 02	[8e0bc192] (00/09) No matches
 03	[e21b5480] (00/09) No matches
 04	[e45ba285] (00/09) No matches
 05	[9678f28a] (00/09) No matches
 06	[f8ca984e] (00/09) No matches
 07	[17c734bc] (00/09) No matches
 08	[6b56fdac] (00/09) No matches
 09	[e6da051f] (00/09) No matches
 10	[d138c590] (00/09) No matches

There's just one thing: I'm not using a preserved ID.  There is no REM ACCURATERIPID tag in the entire CUE Sheet.  So where is CUE Tools getting that "preserved ID" from?  I tried putting a tag in there with the actual ID and it will force that check, but when I remove the tag, it goes right back to checking the false ID.  Why?

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #526 –
hello everyone... i've been a long time reader of the forums here and have gotten tons of valuable info. first, thanks to the author(s) of the wonderful CUETools, I have been looking for a piece of software like this for ages and I'm excited to have it now.

Although I have tried to read up and learn as much as possible, I am still having trouble wrapping my head around a few concepts... one of them being offsets. I have tried reading and searching through this thread, but it's simply too many pages to read through.. and my girlfriend has already been bitching at me enough to get off the computer when I start getting into these and reading them. I just need someone with a clear understanding of this to lay this out to me in a simple enough manner where I can grasp the concept.

I will give this example. These are the calculations from a 13 track CD,  file-per-track FLAC files; this is the first table under the "disc id" line. I assume this is the actual calculated CRC of the input tracks that i am verifying...? (please correct me if i'm wrong) Obviously, something isn't matching up, since there are no matches showing:

Code: [Select]
Track	[ CRC    ] Status
 01	[213508d0] (00/23) No matches
 02	[90b36db6] (00/23) No matches
 03	[1152ecdf] (00/23) No matches
 04	[6e1252ab] (00/23) No matches
 05	[d3591909] (00/23) No matches
 06	[2cf2a748] (00/23) No matches
 07	[2b7fa67c] (00/23) No matches
 08	[81453f47] (00/23) No matches
 09	[ea507b41] (00/23) No matches
 10	[3d4ba5bd] (00/23) No matches
 11	[c1f5c908] (00/23) No matches
 12	[370b551f] (00/23) No matches
 13	[40fd1bea] (00/23) No matches

I have gathered that what is wrong is the offset, because there are several more tables underneath of different "pressings" using different offsets, for instance:

Code: [Select]
Offsetted by 6:
 01	[05b7cf72] (15/23) Accurately ripped as in pressing(s) #1
 02	[829d6f3f] (15/23) Accurately ripped as in pressing(s) #1
 03	[5d639b34] (15/23) Accurately ripped as in pressing(s) #1
 04	[a6c7db40] (15/23) Accurately ripped as in pressing(s) #1
 05	[3c021a2a] (15/23) Accurately ripped as in pressing(s) #1
 06	[b77a7c94] (15/23) Accurately ripped as in pressing(s) #1
 07	[8c789ccc] (15/23) Accurately ripped as in pressing(s) #1
 08	[2ad60b8d] (15/23) Accurately ripped as in pressing(s) #1
 09	[973462dd] (15/23) Accurately ripped as in pressing(s) #1
 10	[14e882c3] (15/23) Accurately ripped as in pressing(s) #1
 11	[16bc618d] (15/23) Accurately ripped as in pressing(s) #1
 12	[51ca571e] (15/23) Accurately ripped as in pressing(s) #1
 13	[3e2ef5aa] (15/23) Accurately ripped as in pressing(s) #1

I see that my tracks with an offset of 6 applied, matches pressing #1. I realize that if I select my files, choose Encode or Encode and Verify and put in 6 as a manual offset, then after encoding, my tracks will match up and then BAM, all is good... the FLAC files test out in both CUETools and TripleF.

I am assuming that I have modified the data in the FLAC files and maybe.. shifted the samples over +6 or something? I am trying to understand:

1) To me it seems that in a file-per-track rip, if i change the offset by so much, I am effectively either cutting "X" amount of audio off of the end of track or the beginning of the track (depending if the offset is positive or negative)...?

2) Am I going about this the wrong way by re-encoding?

3) By adjusting the offsets, am I losing audio data? For instance, if there were a huge sample offset, and I change it to that, is it possible it could cut off the first or last second(s) of audio in the track?

4) If I recall correctly, if i take this "corrected" version from the Converted folder, and create a dummy CUE file for it, using a ripping program like EAC or dbPowerAmp, the disc shows up as absent from the AR database or fails. Any idea why?

5) When fixing the offset (if this is OK to do), is it best to choose the smallest offset difference (so as to limit the "difference" between the original and fixed, or is it best to fix the offset according to the pressing with the most confidence? smaller offset vs. more confidence

Ultimately, from these questions, is the main point: When I have a FLAC set with no cue or log, and it does not match AR entries because of an incorrect offset... and I fix the offset, am I removing audio or destroying the integrity of the tracks or am I doing no harm?

Thank you to anyone who can help explain!

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #527 –
One more thing: what does "Fix Encoding" do when using the Freedb lookup option?  It searches Freedb and Musicbrainz and comes up with a bunch of CD track times, start and finish.  I have a CD in which my start and finish times were different than Freedb's start and finish times for each track.  So, I checked the "Fix Encoding" box and then made a new encoding of it.  I then began a new encoding with THAT new copy to check it against Freedb again, and the exact same difference came up.  It's like it didn't do anything.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #528 –
Quote from: Fuki on
Does the AR database have the actual name of the disc (Artist, Title) stored along with the Disc ID and its track CRC values?
In another words, can I find out the name of the disc if I have its Disc ID (and vice versa)?
So, if CouTools could give me a list of potential CD's (like FreeDB does), I could pick the right one and than CueTools can give me the AR results for that one.

Unfortunately, AR database doesn't have the actual name of the disc, and doesn't provide any search interface.
In theory one might use freedb to locate the possible discids by artist/title. But that would not be of much help.
DiscId is only a function of track lengths. If your CD-R copy has different track lengths from the original,
there's no straightforward way to compare the tracks.

There is one simple case when freedb can help, that is if original CD had a non-zero pregap, and that is the only difference between it and your backup copy.
When locating this disc in freedb (e.g. using CUETools itself), one of the results will most probably contain a correct pregap value, which you can then specify in CUETools.
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #529 –
Quote from: Ryker on
There's just one thing: I'm not using a preserved ID.  There is no REM ACCURATERIPID tag in the entire CUE Sheet.  So where is CUE Tools getting that "preserved ID" from?  I tried putting a tag in there with the actual ID and it will force that check, but when I remove the tag, it goes right back to checking the false ID.  Why?

ACCURATERIPID is probably present as a tag in audiofiles.
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #530 –
Quote from: Chinch on
Although I have tried to read up and learn as much as possible, I am still having trouble wrapping my head around a few concepts... one of them being offsets. I have tried reading and searching through this thread, but it's simply too many pages to read through.. and my girlfriend has already been bitching at me enough to get off the computer when I start getting into these and reading them. I just need someone with a clear understanding of this to lay this out to me in a simple enough manner where I can grasp the concept.


You answered most of the questions yourself.

Here is the closest analogy i can think of: Non-offset-corrected rip would be a copy of the book, where e.g. the first several pages of the book are missing, and the same number of blank pages is inserted in the end, so that the total amount remains the same.

Offset correction would insert several blank pages at the beginning, and remove the same number of pages at the end. (or vise versa, if offset is negative)

If this is the same number of pages that was lost when ripping, than the correction is harmless. No additional pages will be lost.

This can only be achieved when you know exactly which drive model was used during initial ripping, lookup this drive's offset at http://www.accuraterip.com/driveoffsets.htm, and apply this offset.

Any automatic offset correction (to the nearest or to the most popular offset) is risky - it can result in additional pages being lost. Correction to the nearest offset is statistically less harmful.

I already stated my opinion several times, that there's no good reason to correct offsets - some data can be lost, and nothing can be gained (unless you intend to burn the result to CD-R and want it to be identical to some pressing of the original CD)

The good news is that in most cases those first/last 'pages' are blank anyway, and the most you can loose is about 4 milliseconds of near-silent audio.
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #531 –
Quote from: Ryker on
One more thing: what does "Fix Encoding" do when using the Freedb lookup option?  It searches Freedb and Musicbrainz and comes up with a bunch of CD track times, start and finish.  I have a CD in which my start and finish times were different than Freedb's start and finish times for each track.  So, I checked the "Fix Encoding" box and then made a new encoding of it.  I then began a new encoding with THAT new copy to check it against Freedb again, and the exact same difference came up.  It's like it didn't do anything.

"Fix encoding" has nothing to do with track lengths, it fixes track names for entries that were submitted using non-unicode software, such as EAC, when track names are in non-latin (e.g. cyrillic) encoding.
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #533 –
Quote from: tuxman on
Feature request:
A job queue, so CUETools can process another file while displaying the log for a finished one.
(And I could set a few jobs and leave it alone for a while.)

Sounds very nice. I don't think i can do it soon, but i'll keep that in mind.
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #534 –
Thanks a lot for the answers!  I wasn't even aware that audio files could have ACCURATERIPID tags in them.

Your program is great.  Keep it up!

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #535 –
I want to know if Windows 2000 is supported by CueTools, since Version 2.0.x i get an .net framework error "Unable to find an entry point named "ILFree" in DLL 'shell32.dll'  : Continue or quit

If I hit continue, program starts, but in left panel, there is no browser, and it remains "freezed".

Any ideas?
Thanks

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #536 –
Quote from: rootsandculture on
I want to know if Windows 2000 is supported by CueTools, since Version 2.0.x i get an .net framework error "Unable to find an entry point named "ILFree" in DLL 'shell32.dll'  : Continue or quit

If I hit continue, program starts, but in left panel, there is no browser, and it remains "freezed".

Any ideas?
Thanks


My quick advice:

If there seems to be a problem with a corrupt .NET framework, i would recommend this tool, developed by someone affiliated with Microsoft/MSDN. Do a google search for the file "netfx_setupverifier_new.zip" and look for the  Aaron Stebner WebLog. You can run this utility, which you select which version of the .NET framework you want to verify/test, and then it will check and see if there are any problems with the installation, such as missing/corrupt files or screwed up registry entries, etc.  If you find problems, or otherwise want to start over fresh, I would try removing the .NET framework from Add/Remove programs, then (on either success or failure) running this tool by the same author... which manually cleans any traces left of the .NET framework version you select. Again, google search for the filename "dotnetfx_cleanup_tool.zip" on Aaron Stebner's site. There are plenty of instructions and info on the page; plus the programs are extremely straightforward.

From quick lookup, it appears to me that the latest version that runs on 2000 is .NET framework 2.0 SP1... which requires that you be at Service Pack 4. (Unverified that this is the last version that works with Windows 2000, I could be wrong, but microsoft's site stops mentioning Windows 2000 in the list at this point).

That should get you pointed in the right direction if it is indeed a .NET problem.. but 2000? Thought about upgrading?

Anyways, I hope that advice helped you in some way. Let me know the results out of curiosity.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #537 –
That's not a .NET problem.

Win2k is not officially supported, but it might work with recent service pack and
most importantly - recent Internet Explorer version.
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #538 –
Quote from: Gregory S. Chudov on
That's not a .NET problem.

Win2k is not officially supported, but it might work with recent service pack and
most importantly - recent Internet Explorer version.


Lastest Service Pack is SP4 and update Rollup installed.
Lastest IE is 6SP1

I tried installing NET Framework 2.0 SP1, with no luck
When hide the browser (the left panel), rest appears to be ok.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #539 –
Well, your system is up to date, as far as i know IE6 is the maximum version for Win2k.
Which means, that the browser panel won't work on Win2k. Sorry.
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #540 –
Another experimental version is out.
Not much new there again this time, summer makes me lazy.
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #541 –
Quote from: Gregory S. Chudov on
Another experimental version is out.
Not much new there again this time, summer makes me lazy.


awesome... thanks for all your hard work!! great program, i'm glad to see that you're still putting time into it. it's much appreciated!



edit: just FYI, i'm having some trouble with the new version... getting a few errors such as (Could not load file or assembly 'CUETools.Codecs.TTA, Version=1.0.3505.28501, Culture=neutral, PublicKeyToken=null' or one of its dependencies. This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem. (Exception from HRESULT: 0x800736B1). --- this is when selecting a flac group in multi-select mode

the dll file is there... maybe it is trying to look in the current directory of the FLAC files instead of EXE location? or maybe DLL extention was accidentally left off? sorry.. no programmer, just trying to help


CUETools versions 1.9.5 through 2.1.5 (current)

Reply #542 –
Is your system 32-bit or 64? If 32, maybe you downloaded x64 version by mistake?
Does it verify/encode FLACs after showing this error message?
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #543 –
This is a longshot but ever thought of integrating support for discogs.com in there?

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #544 –
v2.0.4 says "Welcome to CUETools 2.0.3".
audiophile // flac & wavpack, mostly // using too many audio players

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #545 –
Sorry, but things are getting worser & worser for me, I already never used V2.03, but I cannot even test V2.04 as the drag&drop zone has completely disapeared ... & I am not even using 120% fonts this time.

Windows XP SP2 (Net Framework V2.0+Ms Visual C++) Font Size=100% (Default):



Things get even worst when I select the convert mode:



I am still using V2.02, & it was not a big problem with V2.03 but there are added features/fix in V2.04 that I would like to adopt now, specially [* AccurateRip log made a bit more tidy (good offsets first, no 'as in pressing(s)' spam] which is a fix I requested ... I hope this will get fixed.

Am I alone to have this problem ? I mean, my settings are very basic now, I turned every display tunings off in order to, at last, try this version, even with bugs like I did with V2.03, but this time I completely failed ...

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #546 –
just to give you a little more info... i am running Windows XP SP3 (32-bit), and I am positive I downloaded the x86 version (the folder name has x86 in it, plus i re-downloaded and tried extracting/running it from a different drive).

Any other info I can give you... as for .NET version installed, I have

.NET Framework 1.1
.NET Framework 2.0 SP2
.NET Framework 3.0 SP2
.NET Framework 3.5 SP1

The error occurs in all modes when doing a VERIFY, and it opens the bottom log window, then immediately spits out the error and goes no further. This is the only output shown in the output window. It does not totally crash the program, it just will not verify files. Here is the code shown, and a screen shot of (possibly the same) error code in a dialog box.

C:\FLAC\01 - Whatever.flac: Could not load file or assembly 'CUETools.Codecs.TTA, Version=1.0.3505.28501, Culture=neutral, PublicKeyToken=null' or one of its dependencies. This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem. (Exception from HRESULT: 0x800736B1).



Hope this helps in finding the problem.

BTW, I ran the program in a virtual machine and I came up with the same error... and on my girlfriend's laptop.. same thing.
 

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #547 –
Chinch:
Do you have Microsoft Visual C++ installed ? I get this kind of error message if I don't install it.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #548 –
Quote from: sauvage78 on
Chinch:
Do you have Microsoft Visual C++ installed ? I get this kind of error message if I don't install it.


yes, it looks like i have both 2005 and 2008 versions. not sure what program(s) installed each version, but i know the ATL updates came down from windows update recently it seems... here is a shot of it:



still a mystery to me. i noticed my g/f's laptop, which has the same error message.. has only the 2005 version... but also that update. maybe i'll try and remove the update and see what happens...

is ANYONE else experiencing this problem? i have tested it out on 3 different machines and got the same result.. that can't be coincidence...

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #549 –
I've been using the old Moitah CUE Tools v1.9.1 for a while, but I decided to try the new version. Unfortunately, I keep getting "Exception: There are no more files." I would love to use all the new features, but it just doesn't want to work for me.

I'm currently running CUE Tools x86 in Windows XP as a guest in VirtualBox on OpenSolaris 2009.06. I'm moving to a Solaris and ZFS based file server, so I'm in the transition phase of moving data. I decided to split my old FLAC images to individual tracks with CUE Tools while I'm taking the time to organize everything.

I think the problem is that I have my ZFS backup drive as a shared folder in VirtualBox and mounted in XP (just like you would mount a standard network folder). I thought the problem might have been the long paths I have to my music (/backup/media/audio/old/flac/%artist%/%album%/%artist%-%album%.cue in Solaris, B:\media\audio\etc... in Windows) but making shorter paths didn't work. I'm sure it has nothing to do with VirtualBox because I copied files from the shared folder to the hard drive XP is installed on (a virtual hard drive in VirtualBox) and all versions of CUE Tools worked. The odd thing is that the old v1.9.1 works fine with the shared folder.

So, I'm wondering if anybody has tried running CUE Tools on files in a mounted network folder. It seems that the current version of CUE Tools has problems with files on mounted network drives / folders.

I hope this gets fixed soon, otherwise I'll be using the old version on the 200+ albums I have to convert.