Thanks drakinite,

yes it was before the commit. I "only" downloaded the already built release 0.4.1
I'll see if I can make a build from the sources ... otherwise I'll wait for 0.5 :)

Hi, that was a bug that I (should have) fixed last night: https://github.com/mediamonkeyserver/mms/commit/4464e49bcff899857f230c7677061f672b5e1043
How recently did you download MMS? Was it after the time of that specific commit?

Hi all,

first: thanks all for working on this. I guess this is exactly what I'm waiting for: A centralised MediaMonkey DB which can be accessed by multiple clients and offers all the details MM has to offer (and not as limited as UPNP/DLNA).

I might be blind but I didn't see anywhere a "Quick Start for Dummies", so I would like to check, if my understanding is correct.
[list]
[*] I unzipped MMS on a Windows 10 host
[*] started MMS and configured via WebUI a new music collection
[*] waited for a while until the folder is completely scanned
[*] installed MM5 on a different machine
[*] Started MM5
[*] In the migration wizard, selected the checkbox 'Scan MMS to local DB'
[/list]
When I do this I get the error
[b]JavaScript Alert - file:///mainwindow.html"[/b] listPlaylists error: 401: not logged in

When I then click on Devices&Services/MM Server I see that the user [i]admin[/i] is signed in but it never has been synchronised.

Clicking on 'Set content store' shows the dialog box with all checkboxes unticked.
When I then only select 'Music', I get again the error mentioned above [i]"listPlaylists error: 401: not logged in"[/i]

Actually this error occurs regularly until I disable the sync to the local DB.

Any thoughts?