Qobuz very slow in app
Beantwortet
-
Yes thanks, tried re-adding the app etc. I really don't want to get into the hassle of changing DNS servers just for the sake of one slow app within Bluesound when I don't have any other issues. Qobuz works fine everywhere outside bluOS so I'm pretty certain the issue is within the Node.
0 -
I have both Qobuz and Deezer (evaluating) linked on my BluOs and both are mostly extremely slow to load initially but after that it's all fine. However, that's just for streaming whatever 'they' throw up on the first screen. If I decide to go into my 'Favourites' in either service then I'm back to a 30 second or more wait time while BluOs finds them via either Qobuz or Deezer. No, I haven't tried to change the DNS as I'm already on Cloudflare. My NAD M33 is ethernet wired and I use a Pixel 5a or Samsung S7 tablet - both are fast.
I just chill, slow down and live with it now, much less stressful.👍
0 -
Looking on the DNS traffic I don't see a lot of queries.
I don't see how DNS answers could improve the slowness of Qobuz app.
0 -
Indeed! Same here. DNS traffic is fine. Favourites in Qobuz itself fine too. But more than 30 seconds on the NAD C700.
0 -
Update to this topic - 1 year later.
I have dropped both Qobuz & Deezer after an evaluation and opting for Tidal in the end. Reasons being that Tidal Connect by-passed the slow loading problems described above in BluOS (mine in a NAD M33) and now plays quickly flawlessly. Qobuz & Deezer do not offer a true 'Connect' feature, only Tidal and Spotify do this and well, Spotify did not get a look in for resolution reasons.
I would have preferred to stay with Qobuz but after contacting them numerous times I find that they have no real, meaningful plans in the pipe to add a connect feature that really works just as easily.
On a side-connected note, I was also evaluating Roon around the same time - using an old laptop as the core. Due to costs, one extra box to deal with and other factors I did not continue with it but, during this time I found that both Qobuz and Deezer loaded very, very quickly within Roon (which was connecting to the BluOS M33), so I do wonder if that in my case with the M33 and Nico's with the C700 it is, in the end, a memory and chip limitation problem within the NAD products. i.e. not enough processing power. Running Roon makes things very fast as it uses a powerful computer/server (PC, NUC or Roon's own Rock server) to do justice to software requirements.
Perhaps these (fantastic in all other ways) amps just aren't built to deal with this streaming-load up requirement via BluOS?
0 -
Sorry to revive this post, but using the Bluesound Node n130 with Qobuz, I too find it very very slow to browse and get started.
But somehow, once streaming starts, it is very fast to pause/pass/etc. But searching or selecting something else takes ages.
When using just the Qobuz app, no such issue, but we can't pass control over to BluOs.
So, a few points:
- Qobuz on its own is fine
- BluOs on its own is fine
The problem is the mix of both. I think we either see a bad integration offering on one side or a bad implementation on the other.Would it be a possibility to have both parties work together to solve this? It would be great.
If it can help, use BubblePnp on a Windows machine to hand over Qobuz to another unsupported amp and it seems to work faster. I use Qobuz to search, then share to BubblePnp app.
Can there be something to leverage there?
0 -
HI Michel
As always in these issue, please select Help, Send Support Request so the Support Crew can help troubleshoot the experience you are seeing in your environment.0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
7 Kommentare