Skip to main content
Topic: CUETools DB (Read 190970 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: CUETools DB

Reply #251
Thank you very much!

Re: CUETools DB

Reply #252
Yes, ditto from me.    Thanks for fixing the '/&/" problem.

However, one thing I've learned from this exercise is that I still have to watch out for the issue identified by plugs13amp where close-single-quote (x92) characters have been used in metadata instead of actual apostrophes (x27), as the Yamaha RN500 network receiver that I use to stream music from my NAS can't display x92 characters - they appear as underscores.  (But the associated Yamaha NP control app on my iPad does display them correctly.)   It would interesting to know if this is also a problem with other players.

Re: CUETools DB

Reply #253
Belated thanks for the &apos fix from me too (been on holiday)

In response to Twangster, my Squeezebox setup doesn't have a problem with the close-single-quote (x92) character, neither the web interface nor the hardware player's display (V3 Classic). My little Sansa Clip+ also displays it properly with the native software, but I have it set up to dual boot with RockBox, and that displays a dotted rectangle instead.


Re: CUETools DB

Reply #255
Thanks for letting me know. Running the upgrade now.
CUETools 2.1.6

Re: CUETools DB

Reply #256
Running the upgrade now.
Is there possible a manual database update with correct data?
I know that the CTDB uses the same data for multiple releases of the same disc, but the releases data might be obsolete or incorrect.
For example my dual set PIO-CD-5180-2 Pioneer's release of Armitage III OST barcode 013023518025 gets recognized as Geneon release 51942  barcode 013023519428 which is not. Just because there is no such of release (Pioneer's) in CTDB.
Correct me if I not understanding it properly.

Re: CUETools DB

Reply #257
Manual intervention was only needed once, back in August because the database schema changed in May, and i didn't notice it. Normal replication that syncs the database every hour was resumed in August, on the day when i made that comment.

Musicbrainz is probably just missing information about your release. Or more likely, it knows about your release, but doesn't have a CD TOC attached to it. The same CD TOC is attached to other release though (probably because those releases have the same TOC). You can manually attach your TOC to the correct release. When you click the musicbrainz button in the CUERipper status bar, it actually takes you to the musicbrainz website to do just that. If you do that, in about an hour the correct information will reach CTDB.
CUETools 2.1.6

Re: CUETools DB

Reply #258
Nah, I just used eac_log_to_musicbrainz_discid.py to verify/merge discids from Geneon release to Pioneer (appears to be they contain the same data)
For convenience maybe this function can be extended to CUETools: to use EAC logs/TOCs as database verify medium instead or in addition to cues, and for submitting to Musicbrainz. Of course it is not THAT reliable as original discs but still viable option.

Re: CUETools DB

Reply #259
Can anyone clarify me about "Rel" column? I think "Rel" comes from "Relevance" but I dont understand the meaning of it.
Sometimes "Rel" column is empty but other times there are values between 0 and 100 I think.
From my understanding empty would be the best "value", followed by 100 until 0, right?

Re: CUETools DB

Reply #260
The column is blank when the TOC based lookup results in a match.
Not certain how the relevance is scored but the 100-0 is attached to results from a fuzzy search.
korth

Re: CUETools DB

Reply #261
The column is blank when the TOC based lookup results in a match.
Not certain how the relevance is scored but the 100-0 is attached to results from a fuzzy search.

Thank you for your explanation. Maybe the developer @Gregory S. Chudov can explain anything else about how the score is achieved. As I'm new at CTDB and I'm exploring the database, I'd really like to understand how important is the Relevance scores. From what I can see in the ctdb.php, and I'm not an PHP expert, looks like the score is achieved in a different way between different music databases.

 

Re: CUETools DB

Reply #262
Hello,
I am having an issue with my CTDB plugin in EAC. It is not pulling any metadata in. I ripped a CD using the MusicBrainz FreeDB proxy, and I'm getting a database access error when trying to submit the TOCID to CTDB. I'm on plugin version 2.1.6 and the latest version of EAC.
Thanks.

Re: CUETools DB

Reply #263
Hello,

I ripped a CD from The Cranberries.
After the first rip I got this message:

Track  5  accurately ripped (confidence 200)  [B143B820]  (AR v2)
All tracks accurately ripped


End of status report

---- CUETools DB Plugin V2.1.6

[CTDB TOCID: cVfZRstXeJJVtLUMDmuuIcqRiIQ-] found
Submit result: cVfZRstXeJJVtLUMDmuuIcqRiIQ- has been confirmed
Track | CTDB Status
  1  | (1476/1486) Accurately ripped
  2  | (1473/1486) Accurately ripped
  3  | (1473/1486) Accurately ripped
  4  | (1473/1486) Accurately ripped
  5  | (1263/1486) Accurately ripped, or (205/1486) differs in 1362 samples @03:06:66-03:06:67
  6  | (1474/1486) Accurately ripped
  7  | (1474/1486) Accurately ripped
  8  | (1472/1486) Accurately ripped
  9  | (1475/1486) Accurately ripped
10  | (1465/1486) Accurately ripped
11  | (1474/1486) Accurately ripped
12  | (1461/1486) Accurately ripped
13  | (1471/1486) Accurately ripped

I retried to rerip the cd to see if my cd is bad:

Track  5  accurately ripped (confidence 200)  [B143B820]  (AR v2)
All tracks accurately ripped


End of status report

---- CUETools DB Plugin V2.1.6

[CTDB TOCID: cVfZRstXeJJVtLUMDmuuIcqRiIQ-] found
Submit result: already submitted
Track | CTDB Status
  1  | (1477/1487) Accurately ripped
  2  | (1474/1487) Accurately ripped
  3  | (1474/1487) Accurately ripped
  4  | (1474/1487) Accurately ripped
  5  | (1264/1487) Accurately ripped, or (205/1487) differs in 1362 samples @03:06:66-03:06:67
  6  | (1475/1487) Accurately ripped
  7  | (1475/1487) Accurately ripped
  8  | (1473/1487) Accurately ripped
  9  | (1476/1487) Accurately ripped
10  | (1466/1487) Accurately ripped
11  | (1475/1487) Accurately ripped
12  | (1462/1487) Accurately ripped
13  | (1472/1487) Accurately ripped

Does it means my (two) rips are accurate (+1 accurately ripped on CTDB tracks submitted ?) but someone tried to rerip 205 times to try to fix his cd?


Re: CUETools DB

Reply #264
It means there are two versions of this disc. You got a perfect rip of the more popular version. About 13% of copies (205/1487) slightly differ in just one spot spanning just a few milliseconds. There's no telling which one is "better" other than listening carefully to this exact spot in both versions.
CUETools 2.1.6

Re: CUETools DB

Reply #265
Alright, so from the time I get the message "Accurately ripped" and highest number for example : 700/1000 it means my disc is perfectly ripped and is the same than 699 other people?

When you say there are two versions it is because 205 other people have 1362 samples different @03:06:66-03:06:67.
Is it possible than one person retried 205 times to submit result from different rip or via cuetools?

I listened to the song at 3 min 06 and there is nothing unusual than I can heard

Re: CUETools DB

Reply #266
it means my disc is perfectly ripped and is the same than 699 other people?
Yes.

Is it possible than one person retried 205 times to submit result from different rip or via cuetools?
No. One person can only submit once. Maybe a few times, if they have multiple computers and/or multiple CD drives. But not 205 times. Notice that when you copied your CD for the second time, the log said "Submit result: already submitted".

I listened to the song at 3 min 06 and there is nothing unusual than I can heard
Sometimes those things are barely audible, if at all. But most probably your version is OK.
CUETools 2.1.6

Re: CUETools DB

Reply #267
Ok thanks!

The warning : "or (205/1487) differs in 1362 samples @03:06:66-03:06:67" scared me but since then I get "accurately ripped" and a large number like 5/8, 46/60 or even 130/160 my rip is safe?

but if I get thing like :

"[8eb13402] (01/76) Differs in 78 samples @48:10:50,50:31:02
  [e9bcfc58] (01/76) No match
  [295eb06b] (01/76) No match
  [7af752c1] (01/76) Differs in 4879 samples @65:36:73-65:36:74"

then my disc has to many scratches or doesn't match the 75 other ones? am I correct?

Re: CUETools DB

Reply #268
"[8eb13402] (01/76) Differs in 78 samples @48:10:50,50:31:02
  [e9bcfc58] (01/76) No match
  [295eb06b] (01/76) No match
  [7af752c1] (01/76) Differs in 4879 samples @65:36:73-65:36:74"
That doesn't tell me anything. Out of 76 people who copied this, this is just 4 individual copies that probably went wrong. You can pretty much ignore anything that says (01/xx). Look for the big number.
CUETools 2.1.6

Re: CUETools DB

Reply #269
I thought it meant it was the only wrong different tracks ripped of the other 75 people

Then how can I know like my previous problem than my rip isn't the same as the others?

Re: CUETools DB

Reply #270
I didn't understand the question.
CUETools 2.1.6

Re: CUETools DB

Reply #271
I thought it meant it was the only wrong different tracks ripped of the other 75 people
This looks like a CD with one long single track?

With one track, it might be that there is another release with different music exactly the same track length (although that happens more often with CD singles). If you are one out of two who have ripped the rare one, and 74 have ripped the different music ...
“It sounded bad to me. Digital. They have digital. What is digital? And it’s very complicated, you have to be Albert Einstein to figure it out.”
- Donald Trump, May 2017



Re: CUETools DB

Reply #274
I thought it meant it was the only wrong different tracks ripped of the other 75 people
This looks like a CD with one long single track?

With one track, it might be that there is another release with different music exactly the same track length (although that happens more often with CD singles). If you are one out of two who have ripped the rare one, and 74 have ripped the different music ...


It was a example from http://cue.tools/wiki/CUETools_log : CTDB (CUETools Database) Section

 
SimplePortal 1.0.0 RC1 © 2008-2018