MusicLibrary2 6.3 - Couple of little fixes

[pz1]

Ahh, may have just found it... in your logs you try loading Database factory: System.Data.OleDb.OleDbFactory

It should be
System.Data.SQLite.SQLiteFactory

Hmm, maybe you've set you db to MusicLibrary2.db3, but you config app say MSAccess....


Can you check

I was puzzled about that as well, but I do not know much about these database connectors. In the meantime I had reverted back to ML 5.4 _WITH_ SQLlite. In config.xml I see the following :

Code:

<DatabaseConnectionString>Provider=Microsoft.Jet.OLEDB.4.0;Data Source="C:\Program Files\devnz\gbpvr\musiclibrary2.db3";User Id=admin;Password=</DatabaseConnectionString>
<DatabaseProviderFactory>System.Data.OleDb.OleDbFactory</DatabaseProviderFactory>

Next I install ML2-6.3 as described above. I only choose the default ML2 SQLlite database and leave all other ML2 settings on their defaults:

Code:

<DatabaseConnectionString>Data Source="C:\Program Files\devnz\gbpvr\MusicLibrary2.db3";Version=3;New=True;</DatabaseConnectionString>
<DatabaseProviderFactory>System.Data.SQLite.SQLiteFactory</DatabaseProviderFactory>

I start config.exe a second time to only set the paths for the music directories, and again save it. Now the to my surprise the database string has changed in:

Code:

<DatabaseConnectionString>Provider=Microsoft.Jet.OLEDB.4.0;Data Source="C:\Program Files\devnz\gbpvr\MusicLibrary2.db3";User Id=admin;Password=</DatabaseConnectionString>
<DatabaseProviderFactory>System.Data.OleDb.OleDbFactory</DatabaseProviderFactory>

I don't understand how this happens. The stange thing is that ML2-5.4 functions quite well with this DatabaseProviderFactory

[pz1]

I just noticed that if I reopen the ML2 settings in config.exe the type of database is undetermined. (see attached image). As long as I do check the SQLlite database before hitting the OK button everything is working fine. If I do not check it, the problems as described above occur.
Is this happening only in my installation? If so any idea why?

[psycik]

I just noticed that if I reopen the ML2 settings in config.exe the type of database is undetermined. (see attached image). As long as I do check the SQLlite database before hitting the OK button everything is working fine. If I do not check it, the problems as described above occur.
Is this happening only in my installation? If so any idea why?

I've just made it so that if nothing is filled in, it should default to sqllite.

If i start it with a completely new configuration, I get a message saying the db tab is not filled out.

[psycik]

aha, and found the gbpvr.html - it's actually erroring with gbpvr.xml and I found where....

[pz1]

I've just made it so that if nothing is filled in, it should default to sqllite.

If i start it with a completely new configuration, I get a message saying the db tab is not filled out.

If you open the ML2 settings in config.exe in an existing situation, is the SQL database checked in the 'General tab' or does it look like my image, where the database type is undetermined?

[psycik]

If you open the ML2 settings in config.exe in an existing situation, is the SQL database checked in the 'General tab' or does it look like my image, where the database type is undetermined?

When i start mine the SQLLite option is selected.

The dll I just sent you, has a little more debug logging around here as well. I'd be interested to see what your logs say when it starts. Reply directly if you wish, or in the forums.

[pz1]

Reply directly if you wish, or in the forums.

I will reply directly to you, and if appropriate summarise the results in this space.

[nbarsley]

Are there any tips to help speed up Music Library2? I always thought that it was just my computer that made ml2 seem to lag so much but its actually slower with my new faster computer. Does it have to do with the amount of MP3's in my library? I only have ~4000 songs.

[psycik]

Speed up in what way? Navigating or it's updating of tracks?

There is a setting in the configuration called Always Query - which you can turn off, and it will stop ML2 from running a query everytime you navigate a new artist/album. You have to hit ok on the artist to activate the query.

Also there is an option to remove the "All/All" setting which is what the default view is when you navigate back in to ML2 from outside.

For the track updating, the very first one will be slow, but subsequent updates should only update what has changed.


One thing I did do with this new version was to push the playlist loading to a background thread. Now that i know how to do that, I might be able to do similar with the navigation.

Try some of those ideas and let me know how you get on.

[pz1]

I will reply directly to you, and if appropriate summarise the results in this space.

My problem has been solved by psycik with a patch that I presume will be part of the next public release.

In my debugging efforts I came across an issue with updating my library. It appeared that in the 6.x series my library did not reflect the changes I had made in my MP3-tags. I now understand that this plugin queries WMP to get the MP3-tags. The problem is that this function first looks in the WMP library if there are tags for a specific MP3. If it does not exist it queries the MP3 file. Months ago I once ran WMP on my server, and I did build a library. So this library was the source of my outdated information in ML2. Emptying the WMP library solved the problem.