Hi @
fralippo,
To summarize how it works: The mConnect Qobuz plugin on your iPhone (192.168.1.7) connects to the Qobuz service, it fetches e.g. the list of tracks and displays it locally in the App as a list of songs. When you choose one and press Play (having your Moode Pi as renderer), the mConnect on your iPhone fetches the stream from Qobuz on its own AND then it serves it to your Moode on its own. mConnect acts like the "Qobuz server" for your Moode. It does so by telling the MPD from Moode to "play" a URL, i.e. the URL http://
192.168.1.7:57645/proxy/qobuz/6B7...roxy=false. This URL is created by mConnect App and also served from there. Note the IP, it tells to Moode to Play the stream from your mConnect App from the iPhone. Yes, the mConnect is not "just" an app, it has a upnp server inside, in order to be able do that.
This is the reason why, if you look at Moode from any device (Mac, your phone, Grandma's laptop, ...), Moode will tell you which stream is playing, i.e. the Qobuz stream from the iPhone mConnect App: http://
192.168.1.7:57645/proxy/qobuz/6B7...
Thus, as @
TheOldPresbyope mentioned as well, this is normal.
Now, what happens is that when Moode tries to fetch the stream that it has been told to, http://
192.168.1.7:57645/proxy/qobuz/6B7... it cannot. As mentioned above by @
TheOldPresbyope , I can confirm that the URL here (I am using also mConnect on the iPhone and an external DAC via USB on my own here) does NOT contain the "proxy" neither in the path nor as the url parameter (at the end, after the question mark). This URL is created by mConnect itself, and MPD is asked to play it; mConnect adds this proxy stuff to it, I do not see yet why.
Here is a couple of more things that I would try: (
Update ! see next post! )
- First, check on the iPhone that indeed it has the IP address 192.168.1.7.
- start mConnect from the iPhone and go into the Qobuz plug-in, open it and browse some music. Press Play on some song and check the URL that is failing on Moode via browser. Note down the failing URL (copy if you can)
- While mConnect still open and inside the Qobuz plugIn, open a new browser tab on the Mac and open the failing URL from the previous step. Check if it is failing (most probable). If not, your browser should start playing that song.
- Assuming it was failing before, change the URL by removing the
/proxy from the path and
?proxy=false at the end and try opening again. Check if it plays.
What happens is that mConnect is adding the "proxy" stuff to the URL that it generates and we no not understand why. Either it is behind a VPN and that's why, or for other reasons. I would suggest asking mConnect folks as well, under which circumstances are they doing that.
The other option - as mentioned above - is to use the direct Moode connector to Qobuz. I do have exactly the same Set-up at my home, with an iPhone + Pi + Michi via USB Audio 2.0, with both the native mConnect PlugIn (which I do not use often) and the upmpdcli (where I helped fixing the bug to connect to Qobuz), even before it has been included into newest Moode versions.With the newest version is easy to set-up, you have the key points above.
To be honest, I personally like to use the upmpdcli way, for several reasons. 1) In this way, the stream would go from Qobuz to your PI directly, not using the iPhone as a proxy. This will give you less network hops (the iPhone is no longer in the streaming chain) 2) better gap-less playing experience (with mConnect Qobuz plug-in, gapless playing leads often to frozen player, both on my iPhone 14 Pro as well as on the iPad 10,2). and 3) No crashes of the App (actually freezing) However, you should be prepared for the less good user experience, as browsing Qobuz will look like browsing folders.
IMHO it is worth a try, and you'll most probably get rid of the network problems that you had so far.
- my iPhone is in GhostVPN and not in my home net anymore 