MediaMonkey forum

Bit of a problem here. When I plug a flash drive into my computer and set up settings in MM5, including name, file locations, auto-sync, etc, then proceed to unplug it, plug in another flash drive, then plug the first in *in addition to* the one just plugged in (so there are two devices now, USB drives by the way, with the original one receiving now a different drive letter from before), the one I had already changed the settings on gets reset to defaults, on that drive. Then, when I unplug both then plug the original one back in by itself, it has now adopted the new device's settings. Intermittently, these flash drives are mixed up in MM as well. I plug one in, expecting it to pull up the settings for (A), but I can get (B) or (C) instead (even though each drive is even named differently in Windows). These settings should be drive-letter independent. I saw a "MediaMonkey" folder on these flash drives, and assumed this was where those settings were stored, but that must not be all of it. These devices need to be recognized at all times, no matter how many are plugged in or in what order (i.e. what drive letter they have). It shouldn't be too difficult to add a unique identifier to the existing file structure created by MM to use as the key.

Hi,
on each the device there is file /MediaMonkey/storageInfo.xml
and within the file there is storageGUID that is unique key in order to pair with the corresponding device profile in MMW. It was added mainly because https://www.ventismedia.com/mantis/view.php?id=12205 - so that two distinct SD cards in the same card slot are detected with unique profiles.

I will verify this, but unless you deleted the file it should work fine. Maybe you deleted it between the tests?

OK, I see, the storageInfo.xml is written only once the device is synced the first time.
Just setting up in MM5 (including name, file locations, auto-sync) doesn't create the file.
I guess this was the reason for the profile mismatch.

I have re-opened https://www.ventismedia.com/mantis/view.php?id=12205 and fixed for 4.1.24.1882 and 5.0.0.2130

Alright, as a follow-up, since you mentioned the necessity of syncing, I set up a different playlist to sync on each of two differently identified flash drives. I did so one at a time, setting all the settings on the first drive, then clicking "Sync Now". When it was done, I unplugged it, plugged in the other one, and noticed it automatically registered as the drive I had just unplugged. I then changed the name, set up a different playlist, hit "Sync Now" and unplugged it when done. I then plugged in the first one, and found that MM5 assumed it was the second one, which I had just unplugged. If I restart MM5 during this time, the first flash drive retains the settings it was "assigned" when MM thought it was still the second one.

Also, no auto-sync has happened during the course of all this testing.

Hi, strange, I've just tested with two distinct SD cards inserted to the same card slot (resulting in the same drive letter) on fresh MM5 install and I don't see any issues. Each SD has its own corresponding profile, see:
https://www.dropbox.com/s/4nx4oyyfxlqey ... 6.png?dl=0

If you look at the 'Device & Services' node (per my screenshot above), do you see two profiles?
If you look at the flash drives, do they have the /MediaMonkey/files/storageInfo.xml with unique storageGuid identifier?

Yes, they are there, and they are different. I just tried closing MM with nothing plugged in, plugging two of them in at the same time, and then starting MM. One came up with the name it was supposed to have, but with a (1) at the end of the name (I'm assuming it's because I have the names of the drives set in File Explorer the same as they're supposed to show up in MM), and the other one just had a drive letter for a name, and not even the one it currently had associated with it in File Explorer.

Hi, I am testing this again and I've just seen similar issues as yours, but I've found that the SD card was set as "write protected" .
Isn't this your case too? i.e. if you look at the drives, do they have the /MediaMonkey/files/storageInfo.xml with unique storageGuid identifier ?

EDIT: ok, I've just seen also the issue that the name was just drive letter instead of the real SD card name, I guess that it is, will look into it, thx.
EDIT2: It was related to the fact that in ma case the second SD card was inaccessible / locked somehow, so MM5 couldn't access its sotargeInfo.xml to read the file.
There was one more tweak related to this also (fixed in 2131)

I already said before, the storageInfo.xml is there and has a unique ID. Flash drives don't have lock switches like SD cards do. And it could still copy music files over just fine, regardless of whether it properly recognized the drive. The fault isn't in the drive, it's in MM. Why is MM even relying on anything other than the ID in that XML anyway? Why have the XML if it's not going to use it? It doesn't sound like you quite understood my exact problem, but I will wait to pass any further judgment on the problem until 2131 comes out.

I'm bringing this back up because, now that MM is recognizing my flash drives again, this isn't fixed in 2132. At all. Not even a semblance of a fix. I don't know what other details to give you. In fact, it's gotten worse. I even went so far as to plug two different drives in at the same time, set up their settings, unplug them and plug them in in reverse order, and MM thought they were each other. Turns out, MM isn't even writing the StorageInfo.xml file anymore to these drives, and is still relying on their drive letter to identify them.

malkierian wrote: ↑Sat Nov 17, 2018 4:05 pm Turns out, MM isn't even writing the StorageInfo.xml file anymore to these drives, and is still relying on their drive letter to identify them.

Could you please generate debug log of these? see item 4b here: viewtopic.php?f=30&t=86643
1) Run DbgView
2) Run MM
3) plug in the device1
4) change a setting of the device1 (e.g. select a playlist to sync) and click [Apply] -- at this point the storageInfo.xml should be written to device1 (if isn't already)
5) unplug device1 and plug device2
6) change a setting of the device2 (e.g. select a playlist to sync) and click [Apply] -- at this point the storageInfo.xml should be written to device2 (if isn't already)
7) save to log and attach (e.g. upload to a free file hosting service like DropBox and share the link here or PM me)

Thanks!

https://www.dropbox.com/s/bfa1vsxv2y2ns ... E.LOG?dl=0

It has a third plugin and unplug because when I hit apply for the second one, it seemed to unmount the device. Still didn't write the storageinfo.xml

Hi, thx, I can confirm (based on the log) that the storageInfo.xml really wasn't written to your devices.

Could you please replace your current /plugins/d_WMDM.dll by this d_WMDM.dll : https://www.dropbox.com/sh/1adyja3lz4o3 ... 4lqQa?dl=0
and try whether it fixes the issue + generate one more debug log ?

Thanks!

Alright, that driver made it start writing the storageinfo.xml file again, but it's still not recognizing and using the ID. I plugged in one of the drives, named it "First", hit apply, unplugged it, plugged in the other one, named it "Second", hit apply, unplugged it, plugged in "First" again, and MM said "Second" was plugged in.

Here's the log for that process:
https://www.dropbox.com/s/d6el3tt2yewps ... E.LOG?dl=0

Even when plugging in "Second", before modifying the settings, MM assumed it was "First", so there should be two instances of mis-identification in that log.

Hi,
thanks for the new log.

In the log I see that MM was trying to read the storageInfo.xml from the device, but got an error while trying to read it.
But the log is missing some debug lines to see the exact error number, this mostly happens when DbgView is started after MM start,
could you please generate one more log using this d_WMDM.dll (I uploaded new) : https://www.dropbox.com/sh/1adyja3lz4o3 ... 4lqQa?dl=0
but be sure that DbgView is started prior to MM?

Thanks!

Here you go.

https://www.dropbox.com/s/mplplwgws6czi ... E.LOG?dl=0