Jump to content

Cebolla

Members
  • Content Count

    2411
  • Joined

  • Last visited

1 Follower

About Cebolla

  • Rank
    Cepa Computensis Musicalis

Recent Profile Visitors

10050 profile views
  1. Hi Stefan @BigBadger also mentions loosing connectivity with the MOON MiND 180 when using the normally very well behaved BubbleUPnP Android app, a third party UPnP/DLNA control point - so not just the MOON MiND Controller app. In fact, the post goes on to say that the BubbleUPnP app even loses connectivity with the UPNP/DLNA media server. This would strongly imply a general UPnP/DLNA device discovery problem with the network management system (eg the router) itself, so that issue may not be the same as yours. Have you tried using your MOON MiND 180 using a third party controller app, such as the excellent BubbleUPnP app (Android only, unlicensed version is free) or the mconnect Player app (iOS & Android, free Lite version available)? John
  2. Ah, it all makes sense now. In which case, unfortunately, I believe you cannot use the BubbleUPnP Server method with an iOS device remotely on its own, given that you need to use the BubbleUPnP Tether Client (a Java command line application) on some device on the remote network - unless you can find some way of getting Java runtime support on iOS! Only the BubbleUPnP Android app and the foobar2000 Windows audio file player with the foo_upnp plugin can natively remotely connect to the BubbleUPnP Server; otherwise the remote UPnP control point application needs to go via the BubbleUPnP Tether Client on the same remote network. How about using an Android phone instead?
  3. That should not explain why the mconnect Player iOS app is now able to find the microRendu. The mconnect Player does not have an OpenHome control point, so will not see the BubbleUPnP Server created OpenHome renderer for the microRendu! It's likely something (else) has changed on the network to allow the mconnect Player app to now find the microRendu's built-in standard UPnP/DLNA renderer. Can you remember exactly what you did, especially with regards to the router/other network infrastructure controlling device or even the microRendu's settings?
  4. ??? Why is the iPhone's own hi-res audio handling limit a factor? I can't see that being an issue if the remote network is a standard UPnP audio network streaming setup, so with the iPhone running the mConnect Player app just to control a UPnP renderer (eg your microRendu) on the same network and online access to your home UPnP media server via an ISP. So the streamed audio files will not be handled by the iPhone at all. - Is your intention to use the mConnect Player app's built-in player for playback on the iPhone itself, rather than use it as a UPnP controller for a UPnP renderer on the remote network? - And/or is it that you intend using the phone's network operator for internet access rather than via its WiFi connection?
  5. Unfortunately, the UPnP/DLNA streamer graveyard is full of failed attempts even after promises of gapless playback via a 'simple' firmware fix, eg, all OPPO streaming devices, the original dCS Network Bridge, the first generation Marantz streamers, the old Cambridge Audio NP30, etc. I hope you are not further disappointed.
  6. BTW, to save you some of this hassle for next time, the Open Software Project's suite of Developer Tools for UPnP Technologies can be very useful. Unfortunately (for some) it's only available for installing on Windows: https://www.meshcommander.com/upnptools The AV Media Controller tool can examine the properties of all the audio streams supplied by any UPnP/DLNA media server, including JRiver Media Center's. So you can navigate to the audio file stream of interest and examine its resource properties to view what the UPnP/DLNA media server is saying it's supplying over the network, for example, a .dsf file stream:
  7. Not entirely convinced, though it's not unknown for a player to not display correctly - at least it's not DoP as that would be PCM at 176.2kHz for DSD64. I suspect that the receiver may ironically itself be configured to convert the .dsf file it's receiving from JRiver to PCM at 88.2kHz! No worries - glad you managed to get it going.
  8. All current Pioneer, Denon & Marantz models can network stream & play .dsf & .dff files.
  9. ??? No, the majority of the current DSD supporting UPnP/DLNA streamers can stream and play the DSD files for themselves.
  10. Why have you assumed that? Remember we are talking about the playback capabilities of the Oppo or the Marantz network audio file player, not how the player itself needs to pass the resultant audio output signal to its own internal DAC (be that DoP or native DSD). Edit: Thanks @pas for confirming that at least the Marantz can stream & play single rate .dsf & .dff DSD files
  11. This won't make any difference as they should be greyed out and ignored by JRiver, if the OP sets the Audio -> Mode to "Original", as advised.
  12. Regarding foobar2000, there are two plugin components that provide it with UPnP/DLNA capabilities, foo_upnp and foo_out_upnp, but only the older currently unsupported foo_upnp plugin supports native streaming of DSD files and that's limited to single rate DSD at 2.8MHz aka DSD64. The limit is there because the plugin's developer has never updated the plugin for DSD file streaming, since providing the initial support, which was single rate at the time. That DSD file streaming support was a bit of a hack, anyway, implemented on the UI by adding the 2822400 upper limit setting to the PCM sample rate range, in the plugin's UPnP/DLNA media server Streaming Profiles settings configuration screen! The foo_out_upnp plugin, as its name suggests, provides the foobar2000 audio engine's own output as a continuous PCM stream (with the option of it being either as raw LPCM or contained in a WAV file or encoded as a FLAC file), rather than the individual audio file tracks themselves. The audio engine only produces a PCM audio output signal since it is currently independent of the foo_input_sacd plugin component that provides foobar2000 with its DSD decoding support. So to answer your original questions, it is possible to use foobar2000 for streaming single rate DSD files and you were likely either using the wrong (ie, foo_out_upnp) plugin o you hadn't configured the foo_upnp plugin properly for DSD streaming support. JRiver Media Center is arguably just as confusing for setting up to use for UPnP/DLNA streaming as foobar2000 is, if not worse. No excuse really, given that the support is supposed to be built-in, rather than by adding third party designers' plugin components. First off, ignore everything to do with the JRiver player's own audio output settings. The stream produced by its UPnP/DLNA media server does not use the Audio Output encoding setting, regardless if its set to DSD in DoP, Native or anything else. The Windows computer's audio output drivers do not get involved with UPnP/DLNA streaming. To stream the audio file tracks natively, you must make sure the Jriver UPnP/DLNA media server that you are using is configured with its Audio - > Mode set to "Original", as you did in the first place. This will also get JRiver to ignore all the other Audio -> settings, so you don't need to worry about those (eg, the Audio -> Advanced settings should be greyed out). Additionally, for DSD file tracks to be streamed natively (ie, so that they can be played unaltered as their original DSD files by either the Marantz or the Oppo), the Advanced -> Bitstream DSD (requires DoPE compliant renderer) setting must not be set. Otherwise the DSD file tracks will be transcoded to DoP contained in WAV file streams.
  13. No, the official TIDAL provided apps don't support UPnP renderers. You have to use a UPnP controller app that also provides TIDAL access, eg, BubbleUPnP (Android only) or mconnect Player (Android & iOS, free Lite version available). BTW, upmpdcli is both an OpenHome (aka UPnP with Linn extensions) renderer as well as a standard UPnP renderer, so you can also use an OpenHome controller with it, eg, the Linn Kazoo app. OpenHome is incompatible with standard UPnP and has its own (optional) mechanism for providing TIDAL access. Also, don't expect to be able to stream TIDAL's MQA file tracks using this method and there are no software UPnP renderers that can decode MQA files to the MQA Core signal (aka 'first unfold'). Only the mconnect Player controller app can properly get standard UPnP renderers to stream (undecoded) MQA file tracks from TIDAL's online server and you also need to use a full MQA decoding capable DAC if you require MQA decoding. Personally, if online music service hi-res streaming is your aim, then I'd go for Qobuz instead of TIDAL as it supplies bog standard lossless hi-res FLAC file tracks and you can avoid the complication of decoding the lossy MQA tracks.
  14. Indeed - the ethernet / USB shared pipe bottleneck has been eliminated, resulting massively improved benchmarks for both: https://www.raspberrypi.org/magpi/raspberry-pi-4-specs-benchmarks/
  15. All of Bluetooth's current audio codecs, including the ones that support hi-res, are lossy. WiFi gives you both lossless (eg bog standard FLAC) & lossy (eg MQA) options for hi-res.
×
×
  • Create New...