Kommentare

164 Kommentare

Datum Stimmen
  • Jorge

    So all threads (threats?) enquiring about Qobuz Connect have been getting closed and users ‘redirected’ to this one, which has also been closed during this time and only opened 4 days ago for the announcement about BluOS 4.12.x. And 2 days ago a thread of my own was deleted because I questioned BS’s practice of restricting discussions on Qobuz Connect. Well, this is certainly censorship and not transparency as alleged by BS - a shame a company in this time and age decides to engage in this kind of behaviour and show so little respect for its customers.

    0
  • Pehr Johnsson

    At last!!!!!

     

    BluOS 4.12.4 – The BluOS Support Crew

     

     

    1
  • Eugene K
    • Bearbeitet

    Hi, just installed the updates and updated my NAD C399 player with Bluesound MCD. All apps recognise the C399 but if I start playing songs from Qobuz app then ....NO Sound! And then after 3-4 seconds it stops playing the song, telling me there is an error (Impossible to play the track because an error occurred) and skips to the next song...with the same issues! And this goes on and on......

    Really frustrating as Spotify Connect works ok, but Qobuz Connect does not. 

     

    0
  • Mathijs van Steen

    It works!! Fantastic we now finally have this feature! And better than the Spotify Connect functionality (in my case, af least), as it nicely shows all metadata and album art on my M10 V2 (whereas Spotify does not)

    1
  • Tony W.
    Product Support Manager

    as it nicely shows all metadata and album art on my M10 V2 (whereas Spotify does not)

    That's also resolved in BluOS 4.12.4.

    0
  • Eugene K

    the last few hours tried everything to connect Qobuz Connect, the Qobuz app recognise my NAD C399 with Bluesound module as an audio output but when i choose the NAD as a device for some reason it does not connect to my NAD/Bluesound module. When i start playing a song, the Qobuz app is mentioning that is 'Impossible to play the track because an error occurred'. Then it automatically skips to the next song...with the same issues! And this goes on and on......until i have to shut down the Qobuz app. 

    Like I mentioned, all the correct updates have been done.

    I have really no idea what is going on and how to solve this. Hopefully the Bluesound Team can help me or someone else because this is really frustrating. 

    Thank you in advance!

     

    0
  • Tony W.
    Product Support Manager

    Hi Eugene

    As always, Settings, Send Support Request in the App is always the best first step so we can review the log file and help troubleshoot.

    0
  • Eugene K

    Hi Tony, thanks for your reply, Support Request send! 

    0
  • Thierry Pauly

    I updated Bluos controller to the latest version, but I still don't get possibility to upgrade my NAD M33 to the latest firmware…

    0
  • Tony W.
    Product Support Manager

    Hi Thierry

    We do apologise for this. Due to a separate issue, we have paused the release on NAD 2-channel products. Please see here for details; https://support1.bluesound.com/hc/en-us/community/posts/35149000861591

    We hope to get this package out to you on all models as quickly as possible.

    1
  • FOUQUE Jean-Michel
    • Bearbeitet

    Bonjour,

    Je l'attendais avec impatience. La mise à jour est arrivée.. mais pas de Qobuz Connect pour mon Node Bluesound 2021. Je n'ai pas trouvé s'il fallait l'activé ni comment le faire. Il n'est pas vu depuis mon Qobuz Player sur PC. Nos smartphones, sur le même lan Wifi, ne le voient pas non plus alors qu'ils se voient tous entre eux...
    J'ai comme l'impression que cette fonctionnalité ne sera pas implémentée dans mon node... :(

    Hello,

    I was eagerly awaiting it. The update has arrived... but there is no Qobuz Connect for my Bluesound Node 2021. I couldn't find out whether it needed to be activated or how to do so. It is not visible from my Qobuz Player on my PC. Our smartphones, on the same Wi-Fi network, can't see it either, even though they can all see each other...

    I have a feeling that this feature won't be implemented in my node... :(

     

    0
  • FOUQUE Jean-Michel

    Petit ajout : chose étonnante, je le vois bien avec avahi-browse… Va falloir que je cherche ce qui bloque…

    Small addition: surprisingly, I can see it with avahi-browse... I'll have to find out what's blocking it...

    0
  • FOUQUE Jean-Michel
    • Bearbeitet

    Rectificatif : Qobuz Connect est bien présent. Je pense qu’il est juste inhibé quand une autre source est en cours sur le node. Si je coupe la source, le node apparaît dans Qobuz Player.

    Correction: Qobuz Connect is indeed present. I think it’s just disabled when another source is active on the node. If I turn off the source, the node appears in the Qobuz Player.

    0
  • Manfred Bacher-Hoechst

    Hello Jean-Michel,

    my Node21 was identified in Qobus without any problem.

    Hello to the staff,

    Everything works fine, thanks to all developers (not to the management due to delay delay delay...). Very very nice to work with Qobus App and listening HiRes!

    1

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.

Sie haben nicht gefunden, wonach Sie suchten?

Neuer Post