Get and Submit Temp - Revision history

Jane g: /* Submission Problems */

2013-09-23T18:38:22Z

Submission Problems

← Older revision		Revision as of 18:38, 23 September 2013
Line 22:		Line 22:
	where <foo> is the category under which you submitted. Quick solution: Double click on the CD in the sources list and pick another category, then try submitting again. Any category will work; it practically doesn't matter.		where <foo> is the category under which you submitted. Quick solution: Double click on the CD in the sources list and pick another category, then try submitting again. Any category will work; it practically doesn't matter.

	You're not doing anything wrong, and you're right on target to think there's something amiss with how freedb is implemented. It is based on CDDB, which is a very old standard. Before the dawn of time, folks thought that DiscID collisions would be so rare as to be almost nonexistent. To solve the problem of the super rare cases where the DiscID's actually do collide, they created "categories." Which unfortunately is not a very robust solution, because there are only 11 categories, and you can have disc1 that is Rock, and disc2 that is also Rock, and they resolve to the same DiscID. In that case, you have to put disc2 under something other than Rock. It gets worse if you have move than 11 discs that resolve to the same ID. Then you're just utterly screwed, you just can't add more than 11 discs with the same ID into the freedb. Here's the explanation from the horse's mouth.		You're not doing anything wrong, and you're right on target to think there's something amiss with how freedb is implemented. It is based on CDDB, which is a very old standard. Before the dawn of time, folks thought that DiscID collisions would be so rare as to be almost nonexistent. To solve the problem of the super rare cases where the DiscID's actually do collide, they created "categories." Which unfortunately is not a very robust solution, because there are only 11 categories, and you can have disc1 that is Rock, and disc2 that is also Rock, and they resolve to the same DiscID. In that case, you have to put disc2 under something other than Rock. It gets worse if you have move than 11 discs that resolve to the same ID. Then you're just utterly screwed, you just can't add more than 11 discs with the same ID into the freedb. Here's the explanation from the horse's mouth. <u>davequestion: I didn't know how to put in the link here.</u>

Jane g at 18:30, 23 September 2013

2013-09-23T18:30:17Z

← Older revision		Revision as of 18:30, 23 September 2013
Line 14:		Line 14:
	This also works for playlists with less than 30 songs. The songs MUST be in the correct track order and MUST contain every song in the album. Sort the playlist by "#" first (NOT by track number), and drag-reorder them to get them into the correct order. Then select the playlist and then go Advanced → Get CD Tracks... and choose the database you want to search.		This also works for playlists with less than 30 songs. The songs MUST be in the correct track order and MUST contain every song in the album. Sort the playlist by "#" first (NOT by track number), and drag-reorder them to get them into the correct order. Then select the playlist and then go Advanced → Get CD Tracks... and choose the database you want to search.

	Submission Problems		===Submission Problems===
	By far the most common problem is you get a message something like this:		By far the most common problem is you get a message something like this:

Jane g: Created page with "At any time you can attempt to get or submit disc info using the database. You might want to do this if you have messed up or destroyed your data, or if the CD is in multiple dat..."

2012-06-02T22:45:26Z

Created page with "At any time you can attempt to get or submit disc info using the database. You might want to do this if you have messed up or destroyed your data, or if the CD is in multiple dat..."

New page

At any time you can attempt to get or submit disc info using the database. You might want to do this if you have messed up or destroyed your data, or if the CD is in multiple databases and you want to see what is in each one. (You might like the data in one database over another.)

::Click on Advanced → Get CD Tracks...

kJams will attempt to find the info in the database that you specify. If data is found, kJams updates the copy that kJams keeps for that disc. Note that you will lose any info currently stored for that disc.

If you have entered new info or changed or corrected info for a disc, you are encouraged to submit that data to freedb or TrackType. To do this, click on
::Advanced → Submit CD Tracks to freedb
::OR
::Advanced → Submit CD Tracks to TrackType

When you do this, kJams contacts the freedb or TrackType server and submits the entries for that disc. If there are any problems with your submission, you should get an email explaining the problem, so that you can correct it and resubmit. Note that submitting does NOT update your local database, if you have one.

This also works for playlists with less than 30 songs. The songs MUST be in the correct track order and MUST contain every song in the album. Sort the playlist by "#" first (NOT by track number), and drag-reorder them to get them into the correct order. Then select the playlist and then go Advanced → Get CD Tracks... and choose the database you want to search.

Submission Problems
By far the most common problem is you get a message something like this:

:::Your freedb submission was rejected for the following reason:Discid collision in category <foo>

where <foo> is the category under which you submitted. Quick solution: Double click on the CD in the sources list and pick another category, then try submitting again. Any category will work; it practically doesn't matter.

You're not doing anything wrong, and you're right on target to think there's something amiss with how freedb is implemented. It is based on CDDB, which is a very old standard. Before the dawn of time, folks thought that DiscID collisions would be so rare as to be almost nonexistent. To solve the problem of the super rare cases where the DiscID's actually do collide, they created "categories." Which unfortunately is not a very robust solution, because there are only 11 categories, and you can have disc1 that is Rock, and disc2 that is also Rock, and they resolve to the same DiscID. In that case, you have to put disc2 under something other than Rock. It gets worse if you have move than 11 discs that resolve to the same ID. Then you're just utterly screwed, you just can't add more than 11 discs with the same ID into the freedb. Here's the explanation from the horse's mouth.