Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Jaguu]

Hello,
last summer I ripped all my cd's with MJ7 in wma8 format. I did a lot tag editing as I have plenty of classical music and did not always like the information as it was presented by CDDB.

Now I wanted to re-rip a few cd's to another format and realize that MJ8 is always querying CDDB instead of the local CDDB info and with some cd's it wants me to re-submit all the tag info again, although I did submit it last summer and it is there in my library. So the local CDDB info is not recognized any longer.

Why? Can anyone help? I have a single library and I did a complete reinstall a few weeks ago.
Where is the local cache stored on disk?
Thanks in advance!

Jaguu

[JimH]

Jaguu, there was a thread on this in the last week.  Please see if you can find it.

It may also be in the version 8 help in MJ.  Not sure.

[Jaguu]

JimH,
searched for "CDDB" and "local cache". The only useful infos were to do a new install and that it only works with the original library. So I deinstalled the current version (282) and installed the complete product (284, 9MB). The problem remains.
Don't find any way that a re-inserted cd finds its tag info locally, it always queries CDDB.
Would appreciate more help as I did a lot of tag editing and I would not like to do it again. Thank you!

Jaguu

[JimH]

[from JohnT's earlier post on this]

Here's what happens when you insert an audio CD that Media Jukebox 8.0 hasn't seen before:
1. MJ checks the CDDB "local cache". This is stored on your computer so it doesn't need to go on-line to do this.
2. If it's not in local cache, it checks the "cdplayer.ini" file to see if it can find the info there.
3. If it can't find it in cdplayer.ini, it tries to read "CD-Text" data from the CD.
4. If there isn't any CD-Text info, it tries to go on-line and search the CDDB on-line database for a match.
5. If it can't find it on-line, it asks if you if you want to fill in the info and submit it to CDDB.

Once it has info for an audio CD, MJ stores it in it's own database so the next time you insert this CD it just grabs all the information instantly from it's own database without any CDDB or cdplayer.ini checking.

[Jaguu]

JimH,

>>Once it has info for an audio CD, MJ stores it in it's own database so the next time you insert this CD it just grabs all the information instantly from it's own database without any CDDB or cdplayer.ini checking

That's exactly what in my opinion is not working. Let's have an example:
Last summer I ripped the following album (with MJ7.2):
Artist: Royal Philharmonic Orchestra
Album: Symphony No. 3 by Ludwig Van Beethoven

I did not like the artist entry, so I edited tags and database entries to:
Artist: Beethoven
Album: Symphony No.3 (Royal Philharmonic Orchestra)

These entries I now see in MJ8 library, so they are in the database.

Now, I re-insert the same cd. According to your rules above, I immediately should get (with no CDDB query) the same infos as above, Beethoven being in the artist field.

But, what is happening, MJ8 makes a CDDB query, and I get once more the CDDB content, so now the artist field is again the "Royal Philharmonic Orchestra". So if I do a re-rip, I will have a completely new entry in the database. I will have to delete the old entry and re-edit the tags of the new entry again. That's the issue I would like to avoid.

Hope, I could make my issue more understandable now. I assume that, even if I edited the tags, MJ8 would be able to identify it as the same cd. Or maybe my understanding about it is wrong. (The format is wma).

Jaguu

[JimH]

Problem is, I think, that 7.2 didn't track CD's in the same way as 8.0.

[JohnT]

Yes, that's the issue. Version 8 has a removable drive database that stores CD specific information. This is totally separate from the information in your music library (stuff that's been ripped, imported, etc.). So if you ripped the CD with version 7, version 8 will still have to go through all the lookups to get the CD specific information, then it will store it in the (new) removable drive library.

One correction to my earlier post, step #1:
"1. MJ checks the CDDB "local cache"..."
MJ doesn't do this anymore, so the actual first step is to check the MJ removable library.

[Jaguu]

JohnT,

OK, that's clear, but with this new design, what are the consequences of editing database info?
Am I correct in assuming that renaming the artist of an album in the main database, does not change the artist's name of the album in the removable database?

How do others handle this situation? Editing tags in both libraries separately? What are the best practices?

Also, if I delete a cd title from the removable library, is the library cleared from any information about this cd, so that a next cd re-insert would query CDDB again?

Jaguu