Qobuz Qobuz Connect released

Minor Connect quibble: iOS and MacOs apps forget the latest output device (=WiiM connect streamer) and reverts to internal phone and mac speakers next day. I would expect the apps to select the last chosen output device.
 
Minor Connect quibble: iOS and MacOs apps forget the latest output device (=WiiM connect streamer) and reverts to internal phone and mac speakers next day. I would expect the apps to select the last chosen output device.
I've got the Android Q Connect version on my phone. It most often starts with the phone as player, especially if there has been any period of time between sessions.
 
I've got the Android Q Connect version on my phone. It most often starts with the phone as player, especially if there has been any period of time between sessions.
I guess this is soon sorted out. Anyway, I could post a ticket in a month or so (but I guess it will be fixed by then).
 
Do I have to download something new from the iOS and Mac Appa stores to use connect?
Yes, the IOS Apple Store has Qobuz and visited it seeing "update" to the new version for QC.

On the Mac OS desktop, I restarted the Qobuz application and then it showed atop that an update awaited.
So I hit that and restarted again with the QC download version. In about it says, "8.0.0-b009 (Apple)."

Desktop then shows the version history saying the desktop app is the "Initial release of Qobuz Connect."
 
I've got the Android Q Connect version on my phone. It most often starts with the phone as player, especially if there has been any period of time between sessions.
I think this is deliberate - starting a new session requires the controlling device and streamer to be connected to the same network. Once the session is active both devices need only be connected to the internet. So the session timing out helps prevent the Spotify Connect issue of being able to accidentally (or not-so-accidentally) play music on the streamer at home when away from the house).
 
Using the app with Qobuz Connect, I had one slight hiccup when it changed to the next track on a gapless piece of music. I couldn’t repeat this though, so maybe just a glitch.
I'm getting this big time! The last few albums gapless I listened to had gaps inserted, minute gaps, but gaps... its not repeatable in that it isn't the album, its probably something to do with caching on the Wiim maybe? This is using the Mac OS desktop app by the way, be interesting to see how many are noticing this? I'll post a mention here as well as answering your post...
 
Not sure where to drop this, but I’m still getting gaps between tracks that shouldn’t have gaps, nothing repeatable, which leads me to believe it might by WiiM end of things just not buffering enough data from the stream? I've reported to Qobuz and via the WiiM Home App.

If I go back to the previous track and wind to nearly the end there isn’t a problem usually.

Recently had loads of gaps listing to https://open.qobuz.com/album/5099952205552 but like I say I don’t think this is album specific really, maybe network traffic, latency, who knows… something somewhere just needs to store a few extra seconds of data methinks! 🤷‍♂️
 
Not sure where to drop this, but I’m still getting gaps between tracks that shouldn’t have gaps, nothing repeatable, which leads me to believe it might by WiiM end of things just not buffering enough data from the stream? I've reported to Qobuz and via the WiiM Home App.

If I go back to the previous track and wind to nearly the end there isn’t a problem usually.

Recently had loads of gaps listing to https://open.qobuz.com/album/5099952205552 but like I say I don’t think this is album specific really, maybe network traffic, latency, who knows… something somewhere just needs to store a few extra seconds of data methinks! 🤷‍♂️
Best place to drop this is to raise a ticket to WiiM when it happens via the more/feedback section in the app so they can inspect your device logs and hopefully identify the root cause.
 
Not sure where to drop this, but I’m still getting gaps between tracks that shouldn’t have gaps, nothing repeatable, which leads me to believe it might by WiiM end of things just not buffering enough data from the stream? I've reported to Qobuz and via the WiiM Home App.

If I go back to the previous track and wind to nearly the end there isn’t a problem usually.

Recently had loads of gaps listing to https://open.qobuz.com/album/5099952205552 but like I say I don’t think this is album specific really, maybe network traffic, latency, who knows… something somewhere just needs to store a few extra seconds of data methinks! 🤷‍♂️

Seems if the gap problem was at the Wiim end of things it would affect all music played through the devices with any program. I have a number of gapless albums on my local server that I created. I have zero problem playing them gapless whether using the Wiim App or LMS. However, since they are not streamed from Qobuz, it is impossible to test them with the Qobuz Connect app. I don't recall having any gapless issues with commercial albums when using the Wiim app, LMS or Qobuz, but then I've only had the Qobuz Connect app installed for a few days at this point so my experience with that app is very limited at this point.
 
Seems if the gap problem was at the Wiim end of things it would affect all music played through the devices with any program. I have a number of gapless albums on my local server that I created. I have zero problem playing them gapless whether using the Wiim App or LMS. However, since they are not streamed from Qobuz, it is impossible to test them with the Qobuz Connect app. I don't recall having any gapless issues with commercial albums when using the Wiim app, LMS or Qobuz, but then I've only had the Qobuz Connect app installed for a few days at this point so my experience with that app is very limited at this point.
Perhaps the right question is whether this intermittent gapless issue on Qobuz Connect manifests on any non-WiiM renderers. If not, and it's limited to Qobuz Connect on WiiM, then it could require a fix on WiiM's end, on Qobuz's end, or perhaps on both. There were a few issues that showed up with QC-WiiM during the beta testing process, that were mostly if not completely addressed via a firmware update pushed by WiiM.

I've asked the question over at Qobuz Club to see if anyone has seen this issue on any non-WiiM renderers. Will let you know what responses I get.
 
Perhaps the right question is whether this intermittent gapless issue on Qobuz Connect manifests on any non-WiiM renderers. If not, and it's limited to Qobuz Connect on WiiM, then it could require a fix on WiiM's end, on Qobuz's end, or perhaps on both. There were a few issues that showed up with QC-WiiM during the beta testing process, that were mostly if not completely addressed via a firmware update pushed by WiiM.

I've asked the question over at Qobuz Club to see if anyone has seen this issue on any non-WiiM renderers. Will let you know what responses I get.
Thanks, I’ve raised the issue there as well… I’ve had the WiiM Pro playing as a Roon endpoint for a year or so and not had any issues, but RAAT is a very different kettle of fish I would have thought? I would have thought the same WiiM bit of software that pulls Qobuz down directly and is controlled by the WiiM Home app, would be used for the basic work undertaken by Qobuz connect - I haven’t used that to any extent so I’ll give it a go with the album I was listening to yesterday.

I’m sure it will be fixed but it’s a shame as the Chromecast issue with gapless playback is why I have been waiting for Qobuz Connect for so long.

Edit: ah sorry I didn’t notice it was you @Balthazar B 👍😊
 
Thanks, I’ve raised the issue there as well… I’ve had the WiiM Pro playing as a Roon endpoint for a year or so and not had any issues, but RAAT is a very different kettle of fish I would have thought? I would have thought the same WiiM bit of software that pulls Qobuz down directly and is controlled by the WiiM Home app, would be used for the basic work undertaken by Qobuz connect - I haven’t used that to any extent so I’ll give it a go with the album I was listening to yesterday.

I’m sure it will be fixed but it’s a shame as the Chromecast issue with gapless playback is why I have been waiting for Qobuz Connect for so long.

Edit: ah sorry I didn’t notice it was you @Balthazar B 👍😊
Qobuz have released a basic SDK intended to be implemented in firmware on streaming devices (with enough power -- I.e., not the WiiM Mini) that enables them to be renderers for Qobuz Connect. I don't know to what extent the SDK code needs any customization/configuration with each streaming platform, or to what extent other changes need to be made in the host firmware to make it just work. And even on a single platform -- let's say a WiiM Ultra -- there will be environmental complexity that may ultimately affect the user experience. For instance, is room correction on? Parametric equalization? Is there a downstream DAC? Over coax or Toslink? What happens if bitrate/resolution changes between gapless tracks? And probably a couple dozen other potential factors.

Because it's intermittent, it's a pure guess, but I think it may be due to some kind of buffering/memory condition, and/or the efficiency of communication between the renderer and cloud to keep everything in sync (and if there's a glitch, there are a set of conditions that only occasionally triggers it). It's hard to say yet whether it affects devices other than WiiMs.

That's why it's important to notify both parties when issues like this come up, because there's no telling which one needs to implement the fix, or if it requires a joint effort.
 
Last edited:
Did the WiiM firmware update today and it turned hell on IOS. Can't lock on to Qobuz Connect from an iPhone or iPad.

Same ones that worked just fine the other day (as I noted here earlier).

After the WiiM update, neither IOS device would lock on to Qobuz Connect. It could select every other option BUT Qobuz Connect. Rebooted the WiiM Pro several times. Same problem.

Then from the Mac OS Desktop version of Qobuz, was able to choose Qobuz Connect. Only then would the iPhone and iPad suddenly "see" and show on Qobuz Connect and allow any additional actions.

So, if I didn't have Qobuz on the desktop I would not be able to use Qobuz Connect using either IOS device. It would reject each attempt and default back to the last alternative option selected.

Firmware 4.8.7.16250
 
Did the WiiM firmware update today and it turned hell on IOS. Can't lock on to Qobuz Connect from an iPhone or iPad.

Same ones that worked just fine the other day (as I noted here earlier).

After the WiiM update, neither IOS device would lock on to Qobuz Connect. It could select every other option BUT Qobuz Connect. Rebooted the WiiM Pro several times. Same problem.

Then from the Mac OS Desktop version of Qobuz, was able to choose Qobuz Connect. Only then would the iPhone and iPad suddenly "see" and show on Qobuz Connect and allow any additional actions.

So, if I didn't have Qobuz on the desktop I would not be able to use Qobuz Connect using either IOS device. It would reject each attempt and default back to the last alternative option selected.

Firmware 4.8.7.16250

Have you turned off Private WiFi Address on your iOS devices? https://support.apple.com/en-gb/102509

It plays havoc with mDNS, which protocol Qobuz Connect uses for advertising network addresses between controllers and renderers, and thereby locating them.

As a best practice, I'd also recommend assigning static IP addresses to any devices on your network involved in Qobuz Connect operations.
 
Did the WiiM firmware update today and it turned hell on IOS. Can't lock on to Qobuz Connect from an iPhone or iPad.

Same ones that worked just fine the other day (as I noted here earlier).

After the WiiM update, neither IOS device would lock on to Qobuz Connect. It could select every other option BUT Qobuz Connect. Rebooted the WiiM Pro several times. Same problem.

Then from the Mac OS Desktop version of Qobuz, was able to choose Qobuz Connect. Only then would the iPhone and iPad suddenly "see" and show on Qobuz Connect and allow any additional actions.

So, if I didn't have Qobuz on the desktop I would not be able to use Qobuz Connect using either IOS device. It would reject each attempt and default back to the last alternative option selected.

Firmware 4.8.7.16250
Ok with my Pro from my iPad. Have you tried power cycling the Pro and your router?
 
My WHA couldn’t find the Pro as per usual after update, closed the app and swiped away, was fine from then on… yes I too found Mac network security features mess up on so many levels for apps that need a constant IP.
 
I’m on Qobuz Android app 9.0.0.2 and Wiim Pro Plus firmware 4.8.714841

Everything OK with Qobuz Connect when I listen keeping the Qobuz app open in foreground.

Everything OK if I close the Qobuz app and open another app.

If I don’t close the Qobuz app, when I open another app, the Qobuz app goes to background, and after a few minutes sometimes the track stops, the next track in the queue starts playing, and an error message is displayed in the Qobuz app.

It looks like the Qobuz app tries to keep in synch but fails the synch.
 
Ok with my Pro from my iPad. Have you tried power cycling the Pro and your router?
Did the WiiM Pro three times. Did not reboot the router. Today, noticed the same issue on IOS devices.

They spin when choosing Qobuz Connect. Once the desktop Qobuz application is opened and connected to Qobuz Connect then both IOS devices can connect.

The iPad easily connected then. The iPhone then showed as defaulted to Qobuz Connect. Didn't see this on the prior WiiM firmware.

Could be something that happened to me. After the firmware downloaded, nothing was working. I then rebooted the WiiM Pro to get it working again. Maybe that had something to do with this issue arising.
 
Have you turned off Private WiFi Address on your iOS devices? https://support.apple.com/en-gb/102509

It plays havoc with mDNS, which protocol Qobuz Connect uses for advertising network addresses between controllers and renderers, and thereby locating them.

As a best practice, I'd also recommend assigning static IP addresses to any devices on your network involved in Qobuz Connect operations.
No, I've not fiddled with any of this. The iPhone is already set to FIXED. The iPad is older OS and shows Private IP address as on. I'll reboot the router too though.

Once again today, I saw the issue but when the Mac OS desktop Qobuz application connects to Qobuz Connect, the other devices then have no issue connecting after.

I would prefer to reload the firmware as it didn't work after the update yesterday. I think the kink may lie there.
 
Last edited:
Back
Top