Jump to content

Cebolla

Members
  • Content Count

    2549
  • Joined

  • Last visited

1 Follower

About Cebolla

  • Rank
    Cepa Computensis Musicalis

Recent Profile Visitors

10727 profile views
  1. The 'Pi way' has humble beginnings, but can lead you quite far: https://allo.com/sparky/usbridge-signature-player.html
  2. Not sure what your issue is here, given the Topping D50 has a USB audio input in addition to the optical one that you've connected the CCA to. Couldn't you just continue using the CCA for Deezer HiFi and get yourself a Raspberry Pi based streamer for your hi-res files via the D50's USB audio input?
  3. It may be worth contacting SOtM to see if they can update upmpdcli to the latest version (1.4.7). The release notes mention a fix for issues with Kazoo on version 1.4.6, but it's possible the same Kazoo issues are present in 1.4.5 version currently installed on your SMS-200. BTW, upmpdcli's OpenHome control point online music streaming service connectivity issue identified around November last year was a Qobuz only access problem. Qobuz decided to tighten up on the security of their API & revoked access to a particular developer's API credentials that had become common knowledge and used unofficially by upmpdcli. So nothing to do with TIDAL and its access was unaffected by that particular issue.
  4. I'd suggest pencilling in gapless playback support as a must for the CCA replacement.
  5. Makes you wonder how serious Deezer are about their HiFi FLAC streams given that the Deezer Desktop app still can't be used in exclusive mode on Windows. it's been 3 years since the Deezer Desktop app came out with the beta HiFi version which had the obvious omission originally! I was about to suggest using the Deezer Desktop app (as you mentioned Audirvana) with a virtual audio cable & the foobar2000 player as the bit perfect go betweens to a UPnP/DLNA renderer on the RPi - until I double checked, that is.
  6. Somewhere's part of the problem, given that the OP's 'lost' the PC!
  7. I'd wait on the detail if I were you - don't forget lossy MQA can also be "hi-res audio > 16/44" & I wouldn't put it passed Sonos being tempted by MQA's lossy compression or something similar considering their previous concerns about wireless network bandwidth.
  8. Glad you appreciated it - hope you get some blessings soon, too!
  9. No, there's actually no such thing as an OpenHome media server, only OpenHome renderers (aka streamers aka players) and OpenHome control points (aka controllers). OpenHome devices always use standard UPnP/DLNA media servers (which are not aware that OpenHome even exists). OpenHome was originally developed by Linn as an extension to standard UPnP/DLNA, mainly to provide better management of the streamer's current audio file playlist and the handling of gapless playback. So the main difference between OpenHome streaming & standard UPnP/DLNA streaming is the interaction between their respective streamer & controller apps, but both OpenHome & standard UPnP/DLNA interact with the UPnP/DLNA media server in exactly the same way. OpenHome has nothing to do with digital audio signal formats such as PCM and DSD, nor converting from DSD to PCM. What you are referring to is a UPnP/DLNA media server's normal optional ability to transcode (convert the audio file to the desired format on the fly for streaming). Your 'problem' with JRiver Media Center appears to be with its UPnP/DLNA media server's built-in transcoder, not that it didn't 'support OpenHome'. BTW, MinimServer's transcoder is the optional MinimStreamer add-on package. At a guess (not having seen the original conversation) is that JRiver's JimH was referring to them not providing JRiver Media Center with an OpenHome control point & OpenHome renderer, in addition to its existing UPnP/DLNA control point & existing UPnP/DLNA renderer (so nothing to do with its existing UPnP/DLNA media servers).
  10. Thought it best to correct that bit of misinformation - MinimServer is a media server, supports the UPnP/DLNA media file network streaming standard and doesn't 'play' anything (it just provides the audio files over the network). The 'OpenHome musicplayer' is actually the U1 Mini in the case you described!
  11. Are you saying you don't use / plan to use the Roon Core server and therefore its built-in audio file player to output to other network devices - what's the point of announcing the Cambridge Audio devices' update to support RAAT, then?
  12. Would you be so enthused if the CXN V2 came with a NAA in a future firmware update, I wonder? Isn't "Roon over ethernet" similar to "HQPlayer over ethernet", ie, another two device "noise maker" system that you're apparently not so keen on?
  13. Depending on how you have set up the internal DLNA server that you are using within JRiver, it's possible that JRiver is not doing anything to the audio files at all. So JRiver may be sending the audio files over the network intact, without any involvement of JRiver's audio engine, for the Lumin itself to decode and play, ie, exactly the same as the Lumin's own controller app behaves.
×
×
  • Create New...