(10-12-2016 12:39)simoncn Wrote: (10-12-2016 12:22)bubbleguuum Wrote: I will also make BubbleUPnP recognize audio/x-dsd (and the alias audio/dsd). This is purely for display in the Now Playing screen for the codec which will display as "DSD".
Does MinimServer ever send this mime-type and in which case ?
The history of audio/dsd is that JRiver sends it for both DSF and DFF, leaving it to the renderer to work out which of these it is. Some other products (renderers and possibly servers) have imitated this. MinimServer always uses the specific audio/x-dsf and audio/x-dff types. never audio/x-dsd.
For aliasing purposes in the control point, I think the following should work:
1) A renderer that claims to support audio/dsd or audio/x-dsd should be considered compatible with the following server types:
audio/dsd or audio/x-dsd
audio/dsf or audio/x-dsf
audio/dff or audio/x-dff
This is not required for the Sonore but is required for renderers such as the Melco N1, which advertises audio/dsd and audio/x-dsd only.
2) A renderer that claims to support audio/dsf or audio/x-dsf should be considered compatible with the following server types:
audio/dsf or audio/x-dsf
3) A renderer that claims to support audio/dff or audio/x-dff should be considered compatible with the following server types:
audio/dff or audio/x-dff
A question : is there somewhere a database / web site of how do all renderers which you can buy advertises their support ?
That would be instructive (cf. my problem where dsf:-/wav24;176 with a klimax does work with kinsky app, but does not work with kazoo nor lumin app ?)
Thx
Serge