MediaMonkey forum

Only reason I bought the Gold version was the automatic monitor function (it only works on MM start-up). This is not working in my NAS environment (see my setup below). Only if I force it (rescan) new files are found.

Furthermore: If I do a rescan then duplicate files show up even though one of them is non-active (dead link). Dead links are only removed when I remove them manually file by file. This ought to be done automatically by the monitoring function I think...

All in all: I have gotten no improvement by buying the Gold version.

More info here: http://www.mediamonkey.com/forum/viewtopic.php?t=14628

Kos

I'd like to second that disappointment with the Gold version. I too have an NAS, and bought the gold version for such functionality as the automatic monitor...but it DOES NOT work.

As with Kos, it only works when i force it to rescan. Extremely disappointing. I too have not seen great improvement in spending the money (for a lifetime license mind you) for the gold version.

MM can only monitor folders/drives supported by Windows, if the system monitoring feature isn't supported, MM can't do anything about it.

Jiri

jiri, MM works almost perfectly for me. Whatever tag I alter in MM it is registered on my NAS in the corresponding file. It is THE OTHER WAY that doesn't work automatically (meaning: if I change a file on my NAS it is not automatically shown in MM). It's working one way so to speak and only both ways when I force the rescan.

So don't you think the folders are somehow supported by Windows? If it works by "force" then shouldn't it be a "technicality" to make it work automatically (file monitor feature)? Well, I am no programmer!

Kos

To clarify: if you're using a windows box as a file server, then the file monitor will detect changes made to the files 'on the fly'.

If you're using a non-Windows NAS, then the File Monitor can detect changes to files, but will not do so 'on the fly'. i.e. it will only do so if the folder being monitored with Tools > Options > File Monitor is configured with Start-up Scan = Yes. Then everytime you restart MediaMonkey it will automatically check for changes and update the library appropriately.

Note: You need to enable 'Remove Unavailable Tracks' if you want tracks that aren't found to be removed from the Library.

Hope this helps.

-Rusty

I reported a similar problem with network drives (not just NAS) in 2.5.4, and I guess it's not fixed in 2.5.5 Gold.

It would be nice if there were some way to make MM re-read information about already-existing tracks. Are you saying that I have to tell MM to rescan my thousands of tracks every time it starts up? That would be egregiously slow. Instead, could MM automatically detect the timestamp has changed and re-read those tracks? Can the Refresh command be changed to make it re-read selected tracks?

I understand about MM not being able to monitor drives that Windows's file-monitoring APIs don't support, but then MM should display those drives as being available for monitoring with File Monitor.

It seems clear that more and more people are keeping their (large) music collections on network drives and NASes and want to be able to see the current information on any machine they use to access that storage.

Or am I off in the weeds?

@skst, you have a different issue then the one discussed here. One of your issues is that once MediaMonkey's File Monitor detects the temp download it doesn't update when the file finishes downloading.
I don't know what is causing this but a possible solution lies outside of MediaMonkey. In some applications you can have files moved to a final location once finished downloading. If this is supported by the Podcast application you are using I'd advice to set this up and only have MediaMonkey monitor the final location.

As for the NAS users:
- Make sure you are using UNC paths instead of Mapped Drives.
- Make sure you sure that in the File Monitor you allow the removal of unavailable tracks.

Oh yes, there's that issue too. Unfortunately, Juice doesn't allow doing that with downloads.

The other issue is that if MM on one computer updates the tags of a track stored on a network drive (or on a local drive shared over the network), MM on a different PC doesn't display that change, even after using the Refresh command.

But that could still be a different issue, in which case, please ignore me.