>- "musicip": if MusicIP is listening on port 10002: use it (all systems).
Just a thought - if there is no wizard, you can't put up a message to tell the user to have MusicIP running before installing and running SC the first time. It's unlikely that average users will have configured MusicIP to run in headless mode, and would they really think to have MusicIP running before installing/running SC? If you could detect the MusicIP library file, and no response on port 10002, you could tell the user to start MusicIP if they want to import music from that source. I think it's quite unlikely that there are many users that would only have MusicIP installed. It's not a ripper; and not great as a tagger. It's primary purpose is to provide mixes. It's more likely that users with MusicIP have used some other software, eg. iTunes, and then discovered and installed MusicIP to make more intelligent mixes, so I'm not sure about the merits of detecting the presence of port 10002 and importing the library data. I assume MusicIP plugin would be set to run as a source for music library content, not the new mixer-only mode? I think the old-style import music from MusicIP is a bad idea personally, especially if it adds this to music discovered from My Music or iTunes, because that is likely to cause a much longer scan time and a lot of confusion (potentially duplicate songs, etc). Phil _______________________________________________ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/lists/listinfo/beta
