Can’t play any Qobuz tracks. I keep getting the dreaded ‘track currently not available’ and then ‘too many failures. stopping playback’. This has been going on for days; in fact I’ve never successfully used Qobuz.
This happens when Core is on either a ROCK i5 NUC or a WIN10 i3 NUC.
I’ve logged off and on Qobuz several times, without any change to the problem.
All my endpoints and Core machines are connected via Ethernet.
The albums I’m trying to play are all CD quality.
No problem using Tidal. As of today, I’m using the newest Roon release (401).
BTW - I tried playing the OP’s Diana Krall ‘Turn up the Quiet’. That successfully played (MQA version). Too bad.
Thanks for your post, I have split it from the previous thread until we can confirm that this is the same issue. A few questions:
- How are your DNS servers set up? Are you using Google or Cloudflare?
- Can you try to clear your Roon cache using these instructions:
- Find and open your Roon database
- Navigate to
- Move the contents of the
/Cache folder elsewhere, like your desktop
- Try restarting Roon and verify if the issue still occurs
- If the issue still occurs afterwards, can you note the exact local time that you try to playback an album and when the issue occurs? I’d like to enable diagnostics mode for your account.
Tested with ROCK, but not WIN10.
First, I changed my DNS to Google’s. Rebooted ROCK and router. Problem still occurred.
Then, I moved cache contents. Rebooted ROCK. Problem still occurred.
I can recreate anytime you want. Today, the problem occurred at 10:43-44 A.M.
Let me know if there’s something else.
I have enabled diagnostics mode for your account and it appears that there is something wrong with your Qobuz subscription, you are being directed to the Qobuz sample servers:
02/21 15:37:38 Debug: [easyhttp] GET to https://www.qobuz.com/api.json/0.2/track/getFileUrl?format_id=27&intent=stream&request_sig=1510920f2b0770bb37b4ef04f6f363bc&request_ts=1550763458&track_id=57292339 returned after 227 ms, status code: 200
02/21 15:37:38 Info: [LVR] [zoneplayer] Queueing: https://sample2.qobuz.com/file
02/21 15:37:39 Debug: [easyhttp] GET to https://www.qobuz.com/api.json/0.2/track/getFileUrl?format_id=27&intent=stream&request_sig=e10b144837964373ecaf137ce0c4232c&request_ts=1550763458&track_id=57292338 returned after 270 ms, status code: 200
02/21 15:37:39 Info: [LVR] [zoneplayer] Playing: https://sample2.qobuz.com/file
And being limited to just 30 seconds of playback in MP3 resolution:
Line 933: 02/21 15:37:44 Trace: [LVR] [LowQuality, 24/44 QOBUZ MP3 => 24/44] [100% buf] [PLAYING @ 0:04/5:35] Still Awake - Yaron Herman Trio
Line 949: 02/21 15:37:49 Trace: [LVR] [LowQuality, 24/44 QOBUZ MP3 => 24/44] [100% buf] [PLAYING @ 0:10/5:35] Still Awake - Yaron Herman Trio
Line 960: 02/21 15:37:54 Trace: [LVR] [LowQuality, 24/44 QOBUZ MP3 => 24/44] [97% buf] [PLAYING @ 0:15/5:35] Still Awake - Yaron Herman Trio
Line 975: 02/21 15:37:59 Trace: [LVR] [LowQuality, 24/44 QOBUZ MP3 => 24/44] [49% buf] [PLAYING @ 0:20/5:35] Still Awake - Yaron Herman Trio
Line 979: 02/21 15:38:04 Trace: [LVR] [LowQuality, 24/44 QOBUZ MP3 => 24/44] [1% buf] [PLAYING @ 0:25/5:35] Still Awake - Yaron Herman Trio
Line 990: 02/21 15:38:09 Trace: [LVR] [LowQuality, 24/44 QOBUZ MP3 => 24/44] [1% buf] [LOADING @ 0:00] Upside Down - Yaron Herman Trio
I would do two things here:
- Verify this is actually the case by opening the Qobuz web player (https://play.qobuz.com) and trying to play back a track until completion (sample accounts are limited to 30 seconds).
- Contact Qobuz and ask them what your account status is, if you were on a trial it is possible that your trial expired.
Aha! Last night, after I posted to forum, I thought to try Qobuz on my iPad. I was in fact limited to 30 secs. and the app kept asking me did I want a free trial. I figured my problem was because I didn’t understand the app.
I had already signed up for a free 1 month trial, which is what I use to sign on under Roon. That free trial is only about 1 week old.
Thanks for the help; I’ll contact Qobuz.
This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.