Qobuz discover/Quobuz Taste/Favorites etc. not visible in AS 1.10.2

Studio Streaming
1

Hi @Antoine and other forum members.

Maybe it is only me, but since update 1.10.2 all Qobuz screens are blank (except for the playlists).

An example below:

image
image1655×662 80.7 KB

I already tried to disconnect from Qobuz and connecting again in AS, but no luck.
Anybody else has this issue too?

I am running AS on Windows 11 on a NUC i5.

Debug info:

Audirvana Studio 1.10.2 (11002)

Windows 11 (22000) with 16GB physical RAM

Connected account of : **************

SIGNAL PROCESSING:

Polarity Inversion:
	Globally: OFF
	Per track: ON
Effects plugins NOT ACTIVE

UPSAMPLING:
r8brain to DSD256 with filter type B 7th order
r8brain filter parameters
Bandwidth = 99.5%
Stop band attenuation 218dB
Phase linear

AUDIO VOLUME:
Max allowed volume: 100
Replay Gain: None
SW volume control: OFF

LIBRARY SETTINGS:
Sync list: 1 folders
AUTO: D:
Library database path: C:\AudirvanaDB\Studio\AudirvanaDatabase.sqlite

Remote Control server:
Listening on ************

ACTIVE STREAMING SERVICES
Qobuz: Connected as Qobuz Studio
HRA-Streaming: Connected as VirtualVault

=================== AUDIO DEVICE ========================

Max. memory for audio buffers: 4076MB

Local Audio Engine: WASAPI

Preferred device:
Luidsprekers (TOPPING USB DAC)
Model UID:MMDEVAPI\AudioEndpoints
UID:\?\SWD#MMDEVAPI#{0.0.0.00000000}.{fe3aab63-7bc8-41a6-b0e6-824ccdccc884}#{e6327cad-dcec-4949-ae8a-991e976a79d2}

Currently playing in Integer Mode:
Device: 2ch 24bits Integer, 8 bytes per frame 705.6kHz

Active Sample Rate: 705.6kHz

Bridge settings:
Sample rate limitation: none
Sample rate switching latency: 1s
Limit bitdepth to 24bit: OFF
Mute during sample rate change: ON

Selected device:
Local audio device
Luidsprekers (TOPPING USB DAC)
Manufacturer: Microsoft
Model Name: Luidsprekers (TOPPING USB DAC)
Model UID: MMDEVAPI\AudioEndpoints
UID: \?\SWD#MMDEVAPI#{0.0.0.00000000}.{fe3aab63-7bc8-41a6-b0e6-824ccdccc884}#{e6327cad-dcec-4949-ae8a-991e976a79d2}

10 available sample rates up to 768000Hz
44100
48000
88200
96000
176400
192000
352800
384000
705600
768000
Volume Control
Physical: Yes
Virtual: No
MQA capability
Auto-detect MQA devices: Yes
Not a MQA device, user set to not MQA
DSD capability: DSD via PCM 1.1
Device audio channels
Preferred stereo channels L:0 R:1
Channel bitmap: Ox3, layout:
Channel 0 mapped to 0
Channel 1 mapped to 1

Audio channels in use
Number of channels: 2
Use as stereo device only: No
Simple stereo device: No

1 output streams:
Number of active channels: 2, in 1 stream(s)
Channel #0 :Stream 0 channel 0
Channel #1 :Stream 0 channel 1
2 ch Integer PCM 16bit little endian 44.1kHz
2 ch Integer PCM 24bit little endian aligned high in 32bit chunk 44.1kHz
2 ch Integer PCM 32bit little endian 44.1kHz
2 ch Integer PCM 16bit little endian 48kHz
2 ch Integer PCM 24bit little endian aligned high in 32bit chunk 48kHz
2 ch Integer PCM 32bit little endian 48kHz
2 ch Integer PCM 16bit little endian 88.2kHz
2 ch Integer PCM 24bit little endian aligned high in 32bit chunk 88.2kHz
2 ch Integer PCM 32bit little endian 88.2kHz
2 ch Integer PCM 16bit little endian 96kHz
2 ch Integer PCM 24bit little endian aligned high in 32bit chunk 96kHz
2 ch Integer PCM 32bit little endian 96kHz
2 ch Integer PCM 16bit little endian 176.4kHz
2 ch Integer PCM 24bit little endian aligned high in 32bit chunk 176.4kHz
2 ch Integer PCM 32bit little endian 176.4kHz
2 ch Integer PCM 16bit little endian 192kHz
2 ch Integer PCM 24bit little endian aligned high in 32bit chunk 192kHz
2 ch Integer PCM 32bit little endian 192kHz
2 ch Integer PCM 16bit little endian 352.8kHz
2 ch Integer PCM 24bit little endian aligned high in 32bit chunk 352.8kHz
2 ch Integer PCM 32bit little endian 352.8kHz
2 ch Integer PCM 16bit little endian 384kHz
2 ch Integer PCM 24bit little endian aligned high in 32bit chunk 384kHz
2 ch Integer PCM 32bit little endian 384kHz
2 ch Integer PCM 16bit little endian 705.6kHz
2 ch Integer PCM 24bit little endian aligned high in 32bit chunk 705.6kHz
2 ch Integer PCM 32bit little endian 705.6kHz
2 ch Integer PCM 16bit little endian 768kHz
2 ch Integer PCM 24bit little endian aligned high in 32bit chunk 768kHz
2 ch Integer PCM 32bit little endian 768kHz

Local devices found : 1
Device #0: Luidsprekers (TOPPING USB DAC) Manufacturer: Microsoft Model UID: MMDEVAPI\AudioEndpoints UID: \?\SWD#MMDEVAPI#{0.0.0.00000000}.{fe3aab63-7bc8-41a6-b0e6-824ccdccc884}#{e6327cad-dcec-4949-ae8a-991e976a79d2} Model Name: Luidsprekers (TOPPING USB DAC)

UPnP devices found : 1
Device #0JPLAY FEMTO UID: uuid:JPLAY192.168.178.192-MediaRenderer Location: http://192.168.178.192:48167/JPLAY192.168.178.192-MediaRenderer/Upnp/device.xml

2

You are spot on, it is not only you.
But not only AS, it is the same with 3.5.44 as well.
All categories and albums are missing under DISCOVER and QOBUZ TASTE.
Very annoying.
What happened?

Matt

3

There is an issue with the Qobuz API that cause the issue. I will report you back about it as soon as possible.

2 Likes
4

I just opened Audirvana and all my Qobuz info is showing, so maybe the API issue was temporary.

Edit: Spoke too soon, the Discover and Qobuz Taste sections are still showing blank screens. Everything else appears to be working though, including favorites. FYI: I’m still using AS 1.9.0.

1 Like
5

Thanks for your reply @Antoine.
For your info, AS is not the only one:

  • I just started Roon and Roon has the same problem as AS (no results shown on Qobuz screens).
  • I also started the native Qobuz app and that seems to work.

We’ll wait and see what happens :wink:

1 Like
6

Qobuz webplayer works as well.

Matt

7

It seems they are not using the same API as their partner which is not really surprising :crazy_face:

8

Why do exist different APIs for Qobuz and their partners?
With different APIs there will always be trouble.

Matt

9

You’ll have to ask Qobuz about that.
But since Qobuz has (probably) written the API themselves it makes sense that they have access to more code than they provide to their partners :wink:

10

Maybe, but I imagine that Audirvana is paying for the Qobuz API so they should not have disadvantages in comparison to the native Qobuz app.

Matt

11

This is fairly standard practice. There are different functional and security requirements for internal use vs. partner / contract use. It should use some of the same base code, but even then multiple API versions for each need to be maintained to keep compatibility in check.

2 Likes
12

Had the same issue, no display on quobuz discover new album. tried few minutes ago.

13

I had to shut down Audirvāna and restart, everything is there now. Mac and 1.10.2

1 Like
14

Yes! Qobuz is back! It seems to work again.

1 Like
15

Mine started functioning normally all on its own just now.

16

All is fine on 3.5.44 as well. Bravo!

Matt

17

Qobuz came back to us yesterday night about it, the issue was on their side and they made a hotfix during the night. You can now Discover and take a look at Qobuz taste in Audirvāna Studio and older versions of Audirvāna as it was before :wink:

4 Likes