Gus141 Posted February 20, 2019 Share Posted February 20, 2019 I was playing one of my playlists just now through the iOS app and noticed for the first time that some of the quality labels to the far right of the song (e.g., CD, Hi-Res) are in blue; not many, most are gray labels. What does the blue signify? Cheers Link to comment
Gus141 Posted February 20, 2019 Share Posted February 20, 2019 11 minutes ago, dmackta said: @Gus141If it's blue that means it is cached on your device. Thanks! And congrats on the successful US launch. As a new US user, I’m loving it! Link to comment
Gus141 Posted July 7, 2019 Share Posted July 7, 2019 @rando @Polyglot I agree with both of you. I paid for Sublime for the year so I could be patient and support the Herculean effort it must take to move to NA. But I kept my TIDAL subscription because of the superior catalog and search capabilities (and I like the My Mix playlists for discovery). I’m not a fan of being trapped into an MQA universe, so everything in my TIDAL playlists I can find in Qobuz, I add to my Qobuz library. I’m hoping for the day I can cancel my TIDAL sub when Qobuz does everything I need. Link to comment
Gus141 Posted July 23, 2019 Share Posted July 23, 2019 I’ve been playing Qobuz through the new DragonFly Cobalt (iPad and iPhone via USB3-connection-kit). Since that DAC is limited to PCM 24/96 I noticed that when I play 192kHz-sampled music the Cobalt’s LED indicates the color for 96kHz (light-blue is the correct color according to AudioQuest, contrary to the manual). So I’m assuming Qobuz will downsample anything higher than 96kHz to an appropriate lower (even multiple) rate. My question is, does that downsampling happening in the app (iOS app in my case) and therefore using cached songs if possible, or does the app request a downsampled version from the Qobuz servers to stream? The Computer Audiophile 1 Link to comment
Gus141 Posted July 23, 2019 Share Posted July 23, 2019 3 hours ago, PAR said: ...BTW the correct colour for 96 kHz is magenta. So if you send it a 192kHz file it should show a magenta light. Blue represents 48kHz. ... That may be true for the DF Red, but I emailed AQ because I was getting a light-blue-almost-white light for anything at 96kHz. This was there reply: “We are working on updating the Cobalt manual for 96kHz. It is not magenta but more of a light blue. This helps make more of a distinction between the MQA Magenta(MQA Purple) and the previous magenta 96kHz on DragonFly Red and Black. Which looked too close to each other when playing Tidal Masters/MQA. We most likely will have the downloadable manual of our site updated first with color descriptions and then the printed manuals for future production of Cobalts. We apologize about that. There are no firmware updates at this time nor changes. No defective LED’s. It is the manual that needs to be corrected.” Cheers, Gus Link to comment
Gus141 Posted October 29, 2019 Share Posted October 29, 2019 Does anyone else see value in creating a new thread: Qobuz Feature Requests. To me, it seems appropriate to post requests for new features (for the service and/or the apps) in a thread separate from the one designed to talk about problems with existing supported functionality. I don’t want to complain about missing features in this thread, but would gladly list all the things I wish the app did differently in a separate thread if the Qobuz team wanted that feedback. left channel 1 Link to comment
Gus141 Posted October 29, 2019 Share Posted October 29, 2019 21 minutes ago, Polyglot said: Besides Audirvana and Roon what other software is able to play Qobuz? Besides native Qobuz apps for desktop and mobile I also use mConnect for some DLNA use which supports both Qobuz and TIDAL. mConnect supports standard DLNA not the OpenHome variant so may not work for some setups. The BlueSound app has pretty good Qobuz support too but only works with BluOS-based hardware. Polyglot 1 Link to comment
Popular Post Gus141 Posted January 10, 2020 Popular Post Share Posted January 10, 2020 5 hours ago, David Craff said: Our first implementation of UPnP was to directly send the url of the track to the UPnP Player. As I said before, this is a problem for most of UPnP player. So the next step, is to transform the desktop application into UPnP Server. This one will take the audio from ours media servers and distribute to UPnP player via is own UPnP server. In this way, by using the same protocol between emitter and receiver, a good compatibility is ensured. My experience with DLNA/UPnP if interested: —turning on the DLNA/UPnP beta in the Qobuz app (MacOS) does not work in my setup: the app sees my Oppo 205 and a Lumin U1 Mini (they are listed in the audio device list) and I can select each one (getting the check mark), but after selecting a song to play, the song never plays —mConnect app sees my Oppo 205 and Lumin U1 Mini and performs DLNA/UPnP controller duties without issues as long as I keep the iOS app in the foreground and don’t do any app switching/multi-tasking (this is when streaming Qobuz and TIDAL); no dropouts, no glitches (tested up to 24/192 on Qobuz) I really wish whatever mConnect is doing correctly could be implemented in the Qobuz iOS app directly 😉. As a minimum, hopefully the API team keeps adding functionality for third-party UPnP controllers like mConnect so that the experience is just as fun as using the native app. Kyhl, deho and greyscale 3 Link to comment
Gus141 Posted February 24, 2020 Share Posted February 24, 2020 4 hours ago, Norton said: Chris, hands up my tone was perhaps rather sharp, ... And so was mine. Apologies. Talisman 1 Link to comment
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now