Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
dsf to wav : what CPU power ?
21-09-2016, 15:09 (This post was last modified: 21-09-2016 15:11 by lyapounov.)
Post: #11
RE: dsf to wav : what CPU power ?
Situation is even funnier : Kinsky does recognize the Linn, and therefore makes the conversion, but when playing dsf on the Oppo, it displays WAV 176,4 kHz / 24 bits on the IOS app, as if it also did the conversion

On the Mac app, it also displays WAV 176,4 kHz / 24 bits

Here is the Mac Kinsky console FYI
21/09/2016 16:04:44: Device+ Device{Udn{078b871d-a7ed-35cc-be38-64f9356605bb}Udn{078b871d-a7ed-35cc-be38-64f9356605bb}UpnpLocation{http://192.168.73.58:8895/deviceDescription/078b871d-a7ed-35cc-be38-64f9356605bb}UpnpIpAddress{192.168.73.58}}
21/09/2016 16:04:44: DeviceUpnp.OpenResponse: http://192.168.73.58:8895/deviceDescript...f9356605bb: The remote server returned an error: (403) Forbidden.
21/09/2016 16:04:44: Device- 078b871d-a7ed-35cc-be38-64f9356605bb
21/09/2016 16:04:44: Device+ Device{Udn{078b871d-a7ed-35cc-be38-64f9356605bb}Udn{078b871d-a7ed-35cc-be38-64f9356605bb}UpnpLocation{http://192.168.73.58:8895/deviceDescription/078b871d-a7ed-35cc-be38-64f9356605bb}UpnpIpAddress{192.168.73.58}}
21/09/2016 16:04:44: DeviceUpnp.OpenResponse: http://192.168.73.58:8895/deviceDescript...f9356605bb: The remote server returned an error: (403) Forbidden.
21/09/2016 16:04:44: Device- 078b871d-a7ed-35cc-be38-64f9356605bb
21/09/2016 16:04:44: Device+ Device{Udn{078b871d-a7ed-35cc-be38-64f9356605bb}Udn{078b871d-a7ed-35cc-be38-64f9356605bb}UpnpLocation{http://192.168.73.58:8895/deviceDescription/078b871d-a7ed-35cc-be38-64f9356605bb}UpnpIpAddress{192.168.73.58}}
21/09/2016 16:04:44: DeviceUpnp.OpenResponse: http://192.168.73.58:8895/deviceDescript...f9356605bb: The remote server returned an error: (403) Forbidden.
21/09/2016 16:04:44: Device- 078b871d-a7ed-35cc-be38-64f9356605bb
Find all posts by this user
Quote this message in a reply
21-09-2016, 15:18
Post: #12
RE: dsf to wav : what CPU power ?
Now it is even worst : the Oppo has disappeared from the BubbleuPnp server :-(
Find all posts by this user
Quote this message in a reply
21-09-2016, 18:25
Post: #13
RE: dsf to wav : what CPU power ?
(21-09-2016 15:09)lyapounov Wrote:  Situation is even funnier : Kinsky does recognize the Linn, and therefore makes the conversion, but when playing dsf on the Oppo, it displays WAV 176,4 kHz / 24 bits on the IOS app, as if it also did the conversion

On the Mac app, it also displays WAV 176,4 kHz / 24 bits

This might be because the Oppo is not advertising support for the audio/x-dsf MIME type (even though it can play this type), so Kinsky selects the stream with MIME type audio/x-wav instead.
Find all posts by this user
Quote this message in a reply
22-09-2016, 16:16
Post: #14
RE: dsf to wav : what CPU power ?
(21-09-2016 18:25)simoncn Wrote:  
(21-09-2016 15:09)lyapounov Wrote:  Situation is even funnier : Kinsky does recognize the Linn, and therefore makes the conversion, but when playing dsf on the Oppo, it displays WAV 176,4 kHz / 24 bits on the IOS app, as if it also did the conversion

On the Mac app, it also displays WAV 176,4 kHz / 24 bits

This might be because the Oppo is not advertising support for the audio/x-dsf MIME type (even though it can play this type), so Kinsky selects the stream with MIME type audio/x-wav instead.

This issue does not happen with the Lumin app : dsf is sent to Oppo

As you said, Simon, it seems that issues are not with materiel, but with apps : some recognize that Oppo can read dsf (Lumin, Kazoo), some don't (Kinsky). Some recognize that Klimax cannot read dsf (Kinsky), some don't (Lumin Kazoo).

BTW : I can access the Oppo only through the BubbleuPnp server. Does it make a difference regarding advertising what Oppo can read ?
Find all posts by this user
Quote this message in a reply
22-09-2016, 17:27
Post: #15
RE: dsf to wav : what CPU power ?
I don't know whether BubbleUPnP Server is making a difference to what MIME types are advertised. You could check this with Bubbleguuum.

In order for this to work correctly, both the control point and the renderer need to do the right thing. Kinsky is definitely doing the right thing, so it seems that the renderer (or perhaps BubbleUPnP Server) is not doing the right thing.
Find all posts by this user
Quote this message in a reply
23-09-2016, 08:43
Post: #16
RE: dsf to wav : what CPU power ?
(22-09-2016 17:27)simoncn Wrote:  I don't know whether BubbleUPnP Server is making a difference to what MIME types are advertised. You could check this with Bubbleguuum.

In order for this to work correctly, both the control point and the renderer need to do the right thing. Kinsky is definitely doing the right thing, so it seems that the renderer (or perhaps BubbleUPnP Server) is not doing the right thing.

Kinsky is not doing the right thing with Oppo, because it converts the dsf to 24/176 instead of sending dsf through, which Lumin does. Kinsky does the right thing only with Klimax, by converting. Other app do the right thing with Oppo, by not converting, and do the wrong thing with Klimax, by sending dsf through

No app is worling properly so far.
Find all posts by this user
Quote this message in a reply
23-09-2016, 10:00
Post: #17
RE: dsf to wav : what CPU power ?
(23-09-2016 08:43)lyapounov Wrote:  Kinsky is not doing the right thing with Oppo, because it converts the dsf to 24/176 instead of sending dsf through, which Lumin does. Kinsky does the right thing only with Klimax, by converting. Other app do the right thing with Oppo, by not converting, and do the wrong thing with Klimax, by sending dsf through

No app is worling properly so far.

As I said in a previous post, this probably means that the Oppo is failing to advertise that is supports the audio/x-dsf MIME type. If the Oppo is telling Kinsky that it only supports audio/x-wav, then Kinsky is doing the right thing by sending an audio/x-wav stream to the Oppo.

The LUMIN app and some other apps are "working" with the Oppo because they ignore advertisements from the renderer and send the first stream in the list. This happens to be the audio/x-dsf stream.

The UPnP system can only work as designed if both the renderer and the control point do the right things.
Find all posts by this user
Quote this message in a reply
30-09-2016, 09:33
Post: #18
RE: dsf to wav : what CPU power ?
Sorry to come back on this topic :

if I type
dsf:wav24;176/-

then it is "always" transcoded.

My feeling is that the controller always chooses the first one when he does not know ?
Find all posts by this user
Quote this message in a reply
15-11-2016, 19:51
Post: #19
RE: dsf to wav : what CPU power ?
Regarding the Oppo 105, I believe it only supports DSF when acting as a USB DAC, not when using it in the way described in this thread, which would explain why it is not reporting dsf compatibility.
Find all posts by this user
Quote this message in a reply
15-11-2016, 21:17
Post: #20
RE: dsf to wav : what CPU power ?
(15-11-2016 19:51)stampie Wrote:  Regarding the Oppo 105, I believe it only supports DSF when acting as a USB DAC, not when using it in the way described in this thread, which would explain why it is not reporting dsf compatibility.

I have some evidence that the OPPO does play native DSF files when acting as a UPnP/DLNA renderer if the MIME type is set to audio/x-dsf. See this post and subsequent discussion.
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)