Transcoding flac:wav odd sound

[DavidHB]

(23-12-2013 21:21)Foxman50 Wrote:  Unfortunately too keep Minimserver requires me to do a lot of retagging to make things look as i like it. Mp3Tag if a fantaastic piece of software so its not too much work.

And, if my experience is anything to go by, the effort is worthwhile; you only have to retag each track once ...

Quote:I'm told that the control point, my nstream app i believe, decides what it receives in the way of tagging information from upnp server. But if this is the case why does the diplay on my ipad have different information on it with Minimserver than it did with media server.

Your understanding is not correct. The browse tree (that is the set of music file information made available to the control point - n-Stream in your case) is determined and provided by the server. Some control points do their own thing (for example, they cache the browse tree at their end rather than accessing it directly on the server), but this is not what the standard specifies. Control points do of course determine how the browse tree is presented to the user, but do not (if they are standards compliant) determine its content.

UPnP AV does not specify which information should be used for browsing. MinimServer provides an almost unlimited range of options for users to configure the tree for their own purposes; you can choose, for instance, which tags are indexed (and so can be used for browsing), and how tags appear in your Control Point. So not only does MinimServer have (by default) a different browse tree from other servers; each implementation of MinimServer (including separate implementations on the same network) can itself be different.

I think that your Synology Media Server is a DNLA rather than a UPnP server. The underlying system is the same for both (DNLA is in part based on the UPnP protocol), but DNLA servers have (in my experience) a common, and much more restricted, browse tree, and do not provide options to change this. I assume that this restriction is part of the DNLA specification, but can't be sure as the specification is not published. DNLA is designed to be used in a wide range of consumer products, so limitations of this kind are a necessary part of the way it works. Unfortunately, for serious users of digital media and the associated metadata (for example, classical music fans who wish to browse files by composer), this approach is far too restrictive.

Interestingly, I find that DNLA control points and players/renderers can see and use the MinimServer browse tree. n-Stream is in any case a UPnP control point, so is better matched to MinimServer than to a DNLA server.

I hope that this explains things.

David