1424: Quick spoiling of the library [#8481]

[willyvds]

Rusty,
I've cleaned up the library, and several issues are gone now. Testing is difficult if several things are wrong at the same time but I suppose I don't have to tell you that...

The slowness is still there sometimes, but it is this issues again (still): http://www.mediamonkey.com/forum/viewto ... =7&t=59254
To summarize: MM slows down if MM on another PC accesses the same MM DB. This even continues after the second PC has stopped. This is not due to limitations in SQLite, because SQLiteSpy does not show this behaviour.

It just happened that my husband looked up something in MM while I was doing the testing.... and that makes my MM slow until I restart it.

This means that the originally reported issue in this thread is solved, as far as I can see.
I would really appreciate it if this multi-user issue could also be solved (or improved). It is THE issue in MM that takes away a lot of the fun for two music lovers here.
Is there any hope? Is it of any use to report that issue in the Beta forum?

Regards, Willy

[jiri]

To be honest, I wouldn't expect any significant improvement in this scenario anytime soon. The thing is that although SQLite can work quite well for very _few_ users, we have MM operations tuned to be as fast as possible for one user. Although we support >1 user per DB, it's preferable to have 1 DB per user and only share files, possibly keep in sync using File Monitor or e.g. newly in MM 4.0 UPnP.

Jiri

[willyvds]

Jiri,
thanks for the honest reply. I understand that you have to make choices although we are really not happy with this one.

File monitor is not an option I think; we do keep all metadata in the tracks but with file monitor we cannot share playlists and playcount.
I cannot find information about the UPnP option. Could you tell me where to look?

Regards, Willy

[Lowlander]

UPnP/DLNA is a way to share your Library. This is a standard many manufacturers/softwares use to share music. Two key components are the Server and the Client. MediaMonkey can be the server and client. All you do is share the master Library through UPnP and the other clients will access it through UPnP (available in the Media Server node). This means all playlists of the master library are available to clients and any plays from the clients will be registered in the master library.
There are drawbacks as you can't edit tracks in the clients (nothing can be saved back to master library through UPnP) and not all fields that MediaMonkey supports are available through UPnP.

As SQLite is inherently few user friendly you might want to add support to the ability to use alternative database engines in MediaMonkey like SQL Server or MySQL which are much more robust. The added advantage is that some NAS's support MySQL database's natively and that even SQL Server offers a free variant. For developers it might also be a boon as it might be easier to integrate into other projects.