This is a complicated issue not totally addressed by profiles. You can make the distinction between 1 and 2 using the single PlugPlayer profile. For 2. assuming you want to transcode all lossless files to mp3: in the PlugPlayer profile, in the "Transcoding to mp3" section - set transcode to never - tick "lossless" and "and internet connection" check boxes. - leave the "except extension" field blank (or add some exceptions). Thanks a lot for your answer, I followed your instructions and basically created a PP profile that would address scenarios 2 and 3, leaving me with some format incompatibilities in scenario 1, which is not so critical to me.It's unfortunately not possible to make the distinction between 1. and 3., because when PP makes the browse request (returning streaming URLs), there's no way for the plugin to know it is for playing to the PP media renderer or for the fb2k renderer. Usually other Media Server that do not have profiles just expose a list of streaming URLs (with different audio formats) and let the Control Point choose one to play on the renderer based on what the renderer claim to support. More often than not, Control Points will make a poor decision (for example streaming the first supported format instead of the format with the highest quality, or just the first streaming URL). Streaming profiles do not work in the case of a Control Point playing to different renderers. It can work if you find common settings between all your renderers but it is less than ideal (you make the profile for the lowest common denominator). I've been thinking of replacing them with something better but if I ever do it, it will be a lot of work. Basically you'd have a virtual Media Server for each renderer you want to manage. Each virtual server's conf would contain what is actually in a streaming profile + more stuff (custom browse tree, ...). It sounds a bit like a workaround but would it be difficult to pass some kind of profile string from PP (or any other CP) each time it connects to the server? It needs to be supported from the CP, which makes it more of a PP feature.