There seems to be a problem when using the MusicIP integration on Mac OS when the music files is behind a soft link. This is only a MacOS problem.

MusicIP:
- Refers to files using the soft link

SlimServer: 
- Refers to files using the real path even if the files is behind a soft link, the soft link is expanded to the real part during SlimServer scanning. 

The result of this is that if you use the MusicMagic(MusicIP) plugin integration on a Mac, you will get the MM icon and all tracks will show up correctly in SlimServer, but you won't be able to create mixes from SlimServer if the files are behind a soft link. When you click the MM button on a track which is behind a soft link you will just get an empty mix.

I think the problem is that MusicIP expects the soft link based path, but SlimServer sends the real path in the MusicIP API. In the SlimServer database the url in the tracks table refers to the real path, so I have a feeling the real problem is in the SlimServer scanning and not in the MusicMagic plugin.

I have only verified this with a end user which had similar problem with the TrackStat plugin MusicIP integration on a real Mac. I have also verified it myself with Mac OS running inside VM-Ware on a PC, but I haven't verified this myself on a real Mac and I don't have the equipment to do it.

An example configuration:

A directory:
/home/xxx/music/part1
And a symbolic link:
/home/xxx/music/part2 -> /mnt/externaldrive1

A music file track.mp3 is stored in:
/mnt/externaldrive1/track.mp3

In the SlimServer database this track is refered to as:
file:///mnt/externaldrive1/track.mp3

When creating a Mix SlimServer sends the following path to the MusicIP API:
/mnt/externaldrive1/track.mp3

But MusicIP expects the following path:
/home/xxx/music/part2/track.mp3

References to the discussions in the forums related to this:
http://forums.slimdevices.com/showthread.php?t=36086
http://forums.slimdevices.com/showthread.php?t=35931 (Discussion about the same problem with TrackStat MusicIP integration)