Official Qobuz Issues Thread

[rickca]

3 minutes ago, Gus141 said:

Does anyone else see value in creating a new thread: Qobuz Feature Requests.

I think that's a very good idea.  

[rickca]

1 minute ago, David Craff said:

 

New UI search is for Web Player and Desktop as a beta. This will arrive after for iOs and Android.

So what is new in 5.3.0-b005 desktop app?  I just installed it and I don't see any search filters.

[rickca]

4 minutes ago, David Craff said:

 

For desktop on 5.3.0 you get the new UI Search. For Android or iOs new release does not have the new UI Search

OK I see the filters right at the top of the screen now. Thanks.  Your comment saying 

New UI search is for Web Player and Desktop as a beta.

confused me.  I didn't think 5.3.0-b005 was a beta release. Does the 'b' in 'b005' indicate a beta?  If so, why is it automatically downloaded?

[rickca]

25 minutes ago, left channel said:

Just received another update, JS version 5.3.0-b008. Hope that solves the new issues reported above.

My latest update says JS version 5.3.0-b009.  What is the JS version anyway?  If I'm using the Windows 10 desktop app, where does JS come into play?

 

One of my Windows 10 instances is very stripped down by using getblackbird.

https://www.getblackbird.net/documentation/

 

On that instance, I get a JS error at Qobuz startup, but then everything seems to work.  I'll capture a screenshot next time I boot to that instance.  So I'm mystified why things apparently work just fine despite this JS error. 

[rickca]

8 minutes ago, Sal1950 said:

Just got a email offering Qobuz Premier Studio for $14.95 a month?

https://audiophilestyle.com/ca/bits-and-bytes/qobuz-tugs-on-supermans-cape-makes-bold-move-with-industrys-best-pricing-r854/

 

[rickca]

I still don't get the reference to Superman's cape.

[rickca]

18 minutes ago, Polyglot said:

This will force the entire industry into CD quality at least.

I wish this were true, but I don't think it is.  Just take a look at Spotify's 3Q2019 results.  Qobuz/TIDAL subscribers are just rounding error to them.

https://investors.spotify.com/financials/press-release-details/2019/Spotify-Technology-SA-Announces-Financial-Results-for-Third-Quarter-2019/default.aspx

[rickca]

6 minutes ago, Talisman said:

Anyone else?

Yes, same experience here in Florida.

[rickca]

2 hours ago, The Computer Audiophile said:

Wow, this is bad. ISPs do this so they can collect info on their users through DNS queries.

Chrome and other browsers are moving to DNS over HTTPS, so DNS lookups will be encrypted.  But I think the DNS provider has to support the protocol.

[rickca]

I clicked on the album cover for Mozart: Clarinet Concerto, Clarinet Quintet & Quintettsatz, K.Anh.91 and Malwarebytes Premium blocked an outbound connection to datapro.website due to a potential Trojan.  The IP address is 172.241.69.4 port 63551.

 

I've never seen this before while using Qobuz Desktop on Windows 10.  Now I'm getting this when clicking on some other album covers as well (but different IP and port).

@David Craff any idea what's happening?

 

Is anyone else running Malwarebytes Premium and getting similar warnings?  

 

[rickca]

3 minutes ago, rando said:

Fairly high chance MB is being proactive

I agree that this is likely a false positive and something that Malwarebytes needs to change rather than Qobuz.

I'd still like to hear from Qobuz why the Windows desktop app would make an outbound connection to URL datapro.website.

[rickca]

@dmackta @David Craff can Qobuz hire Damien as a consultant and get DLNA working in the Qobuz desktop app?  DLNA has worked very well in Audirvana for a long time already.

 

Qobuz has a really nice desktop app.  Where is support for DLNA/UPnP endpoints in your list of priorities?

[rickca]

45 minutes ago, David Craff said:

We have to add some feature before, like secure audio flow

Can you please explain what secure audio flow is?  OK I understand you have development line items with higher priority than DLNA.