3.0.0.1069: Database Conversion Issues

Beta Testing for Windows Products and plugins

Moderator: Gurus

Mizery_Made
Posts: 2283
Joined: Tue Aug 29, 2006 1:09 pm
Location: Kansas City, Missouri, United States

3.0.0.1069: Database Conversion Issues

Post by Mizery_Made »

The most noticable thing right off the bat is the fact that in the conversion, the "Artist 1; Artist 2" type artists you may already have AREN'T broken up, they are treated in the same manor as 2.5 treated them. This may just be a limitation type thing in the conversion process and simply isn't possible to get these fixed in that manor, don't know.

Anyway, another noticeable thing is the fact, the Album Artist has disappeared! You look under the "Artist & Album Artist" node as those artists that are Album Artists have pluses like normal, the tree is working perfectly fine in regards to it actually. It's when you look in the Album Artist column on the tracklist or in the properties sheet that you notice the problem, it's not showing any Album Artists in either of these spots.

There also seems to be a problem with the Composer Node with this converted Database. It would appear, only those songs with Composers matching that tracks artist exactly, is showing. Thus, a track with a composer such as "Aaron Zigman" which is also that track's artist will show, but if the composer field is "Aaron Zigman/Someone Else" or "Aaron Zigman, Someone Else" etc, then these aren't displayed. If this makes any sense, finding this one hard to explain.

There is also an issue with the Album Node & "Unknown Albums." You look under the Album Node and will see the "Unknown" node per usual, but right underneath this node I have a second node that shows the exact same content as the first, but the name is empty.

"Maintain Library -> Compact Database" doesn't have any effect on any of these issues. A "Add/Rescan" on the other hand seems to remedy every problem except the Album Node issue. Even looking past the Album Node problem, having to Rescan isn't exactly the "smooth" transfer from 2.5 to 3.0 people are going to expect. :\

Non of these issues are present in a clean database scan, so must be something directly related to the conversion and not an overall problem with the database structure or whatever.

A small notation, when doing the Rescan, I stopped it after a couple thousand tracks so I could skip to a folder with "Multiple; Artists" to test if it fixed that, when canceling the scan, I was presented with a window for "Unavailable Tracks," basically listed everything in the Database that had not just been scanned, even though the files ARE there and I can even go to them in the library and play them without problem.

If all of this is confusion to read, or you just want to look into it further to see exactly what's going on, I do have copies of several databases I could supply:

MediaMonkey 2.5 Database
MediaMonkey 3.0B1 Database - 2.5 Conversion (Untouched)
MediaMonkey 3.0B1 Database - 2.5 Conversion (Rescanned)
MediaMonkey 3.0B1 Database - Clean Scan

Just let me know if you need/want them.

On a unrelated note, with the new Multiple Artist deal, any chance to see the "Find More from Same -> Artist" option tweaked to better support this? Something like:

Code: Select all

Find More from Same -> Artist -> 2Pac
_________________________________MC Breed
_________________________________Too Short
(Don't mind the underscores, was just to get it to line up) So, while 2Pac is listed first in the artist field, while playing this song with 2Pac, MC Breed & Too Short, I could find more from MC Breed. Just a thought.
PetrCBR
Posts: 1783
Joined: Tue Mar 07, 2006 5:31 pm
Location: Czech
Contact:

Re: 3.0.0.1069: Database Conversion Issues

Post by PetrCBR »

Hi. Issues you mentioned will be fixed in next version of DBUpgrade tool (beta 2).
judas
Posts: 572
Joined: Thu Jun 02, 2005 11:26 pm
Location: Bogotá, Colombia

Post by judas »

Wow, that's fast!!! Good work PetrCBR and devs!
Cheers, judas
T2k
Posts: 15
Joined: Mon Oct 02, 2006 8:27 pm

Post by T2k »

If I'd give it (B1) a try would this leave intact my 2.5 DB?
Mizery_Made
Posts: 2283
Joined: Tue Aug 29, 2006 1:09 pm
Location: Kansas City, Missouri, United States

Post by Mizery_Made »

Yes, it should. When it upgraded mine, it left the 2.5 database in the same spot, pretty much untouched. Though, you should always make a copy and tuck it away 'just in case' since your ARE dealing with Beta software.
gab
Posts: 328
Joined: Tue Oct 11, 2005 1:20 pm

Post by gab »

I've had several problems with conversion. Is there a way to run the conversion again?
Mizery_Made
Posts: 2283
Joined: Tue Aug 29, 2006 1:09 pm
Location: Kansas City, Missouri, United States

Post by Mizery_Made »

Delete the MM3.0B1 database, run the Beta again and it should once again find your 2.5 database and convert.
gab
Posts: 328
Joined: Tue Oct 11, 2005 1:20 pm

Post by gab »

thanks - that did the trick
paulmt
Posts: 1170
Joined: Tue Jul 18, 2006 6:06 pm

Post by paulmt »

An issue I have with 3.0b1 is that the conversion has dropped about 2gB of ratings.
These are all present and correct in 2.5 but even a clean re-conversion comes up with the same result.
It seems to be mostly recently installed tracks from perhaps the last month or so. I use an auto rating script which rates all tracks played for the first time at 2.5
I don't think the issue is caused by the script as only a small percentage of ratings have been lost. Also the ratings that have not showed in 3.0b1 are not just restricted just to 2.5 stars being more random than that.
The 2.5 database has been compacted and is working without any problems with all ratings intact with "ratings\unknown" showing no tracks.
WinXP SP2, MM v2.5.5.998, All MM system files are in the default location.

Not a big problem but does anyone have any suggestions??
Post Reply