Qobuz track slow to start to play in latest release

[Graham_Bird (Graham)]

Core Machine (Operating system/System info/Roon build number)

Version 1.7 (build 667) stable

Running 5 days, 17 hours, 38 minutes, 47 seconds.

Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)

Wired and Wireless - same problem on each

Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)

Seems to be on all devices

Description Of Issue
When a track or album is played, there is a significant pause before playback starts - 15-20 seconds seems to be the median pause.

When the same track is played via Qobuz desktop app (MacBook Pro) then start is as expected in around 2-3 seconds.

I have restarted Roon and also logged out and back into Qobuz in Roon.

[noris]

Hi @Graham_Bird,

Does this same behavior occur with albums with different sample rates from Qobuz?
Can you try to output to your Core’s System Output zone and verify if that has the same issue?

[Graham_Bird (Graham)]

Core is a ROCK (Intel NUC) with no output.

Oddly it seems to be most prevalent with tracks that are 44.1. I tried a number and they all had the hesitation, whilst several tracks at high (96 and 192) start immediately.

Cheers

[noris]

Hi @Graham_Bird,

@Graham_Bird

Oddly it seems to be most prevalent with tracks that are 44.1. I tried a number and they all had the hesitation, whilst several tracks at high (96 and 192) start immediately.

That is very strange, what happens if you try to apply DSP to up-sample lower quality tracks, do they then start quicker?

@Graham_Bird

MacBook Pro

Can you try to play to your Macbook Pro System Output zone (the internal speakers) and verify if the same issue occurs there?

[Graham_Bird (Graham)]

This seems to have resolved itself. I have made no changes, but the exact same tracks in a playlist are started as expected.

I have no explanation for why…

[noris]

Hi @Graham_Bird,

Thanks for letting us know that the issue resolved itself! It is possible that there was an intermittent networking issue. If you need any assistance in the future, please let us know!