It has come to my attention that in certain scenarios muso can cause unwanted side effects to your SqueezeCenter (SC) database.
When muso pushes a song file to a SC device, SC will implicitly add that song to its database if the full path given to it by muso is not registered within SC already. Muso is not to be viewed as another skin, it is a 3rd party app that gives the user the opportunity to push song files to SC devices that were not pulled from the SC database - but instead were pulled from a folder scan or imported from iTunes. For one of my beta testers this actually caused a problem with many duplicates being registered in SC. This can happen if you have an SC database which uses drive mappings for song file paths, and you use muso to scan folders by UNC path, or vice-versa. When muso pushes a song file to SC, it will not recognise the fact that it's the same song as another entry in the database which uses a different path mechanism, and so will register it again. Therefore I strongly recommend users NOT to mix UNC paths with drive mappings across muso and SqueezeCenter - always use either one or the other. If you view SC as the master repository and only import to muso from SqueezeCenter and never do folder scans, you should not have any problem, however. Also, if you do use drive mappings and the machine running muso is not the same machine that is running SqueezeCenter, please ensure both use the same drive letters to point to the same root. -- jezbo ------------------------------------------------------------------------ jezbo's Profile: http://forums.slimdevices.com/member.php?userid=9888 View this thread: http://forums.slimdevices.com/showthread.php?t=57629 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/plugins
