· About two weeks ago we started getting drop outs when streaming Qobuz. Then I started to get non responsive when hitting play on Qobuz or Tidal albums. I looked at the logs and I’m getting a failure on geoip lookup which seems like the culprit. But I can’t clear the error even went as far to uninstall Roon and rebuild my library from scratch, not a back up. Since I noticed the error Roon has become less reliable. I was playing a record from my local library and got pause and skip in the middle it.
Tell us about your home network
· Asus zen router. SonicTransport with static IP. Eversolo dma6 with static IP. The transport and Eversolo are Ethernet wired in the same TP Link gigabit switch.
Thanks for writing in and for sharing your report! Does this issue happen no matter the endpoint you play audio from? For example, the system output of your mobile device or macbook air?
We were able to review a fresh set of Roon Server logs from your sonicTransporter, and although the Roon Server log excerpts provided do not contain explicit underflow or dropout errors, there is rapid file sorting and heavy audio analysis that consume substantial processor cycles and memory. On a server like a sonicTransporter, sustained memory use and high garbage collection overhead can tax the processor enough to prevent smooth real-time streaming, which leads directly to audio dropouts.
That said, the GeoIP lookup error could also very likely be the direct cause of the non-responsiveness when hitting play on Qobuz or Tidal.
Since this error persists even after a complete Roon reinstall, it is not a library corruption issue. Instead, it points to a network routing or resolution problem:
DNS Resolution: The sonicTransporter might be having trouble resolving external domain names. If the static IP was set manually on the sonicTransporter, double-check that the DNS server addresses (like 1.1.1.1 or 8.8.8.8) were entered correctly.
WAN / Firewall Blocking: The Asus Zen router or a setting on the sonicTransporter's operating system might be blocking the specific outbound port or domain needed for that GeoIP check.
Could you also check if the Roon interface is still running background audio analysis or library importing? If it is, pause it or let it complete before testing local playback again.
Thanks for getting back to me. I did some testing after work today and was able to reproduce the issue pretty quickly.
I hit play on a Qobuz track at around 17:45 today and the track never started. Roon just sat like it was trying to connect. Here is a bit of the log from that time:
03/30 17:46:18 Debug: FTMSI-B got length for qo/BABE4140; 343.4 MBytes
03/30 17:46:18 Debug: FTMSI-B-OE set min bandwidth for qo/BABE4140 to 3202 kbps
03/30 17:46:18 Info: FTMSI-B-OE qo/BABE4140 rid:286 response took 253ms
03/30 17:46:18 Debug: FTMSI-B-OE qo/BABE4140 rid:286 request ended – first block: 0 blocks read: 0 download speed: -256kbps response time: 253ms
03/30 17:46:18 Debug: FTMSI-B-OE qo/BABE4140 interrupted req 286; missing block 0
03/30 17:46:18 Debug: FTMSI-B-OE qo/BABE4140 created new req 287 for block 0 p 0; active requests 1
03/30 17:46:18 Debug: [easyhttp] [37838] GET to https://streaming-qobuz-std.akamaized.net/file?uid=995265&eid=156007276&fmt=7&profile=raw&app_id=188245549&cid=1306909&etsp=1774910719&hmac=N4lPjGpjYa4airVEmoO0Kic2bCM returned after 76 ms, status code: 200, request body size: 0 B
So I made the following changes in my Asus Router:
I set the router to always look up from 1.1.1.1 (CloudFlare) and fall back to 8.8.8.8 (Google). When the issue first started I was using Quad9 9.9.9.9 as it’s good for privacy, and then I switched to my ISP for sorting out DNS but that was how my router was configued today when I reproduced the issue.
The other thing I did was set both the Eversolo and SonicTransport to always use 1.1.1.1 as part of their static IP config.
On my Roon config, I set it to only run background analysis overnight from 1am to 5am so that shouldn’t be an issue when I’m streaming during waking hours. And the import has been done since late Satureday night so that should all be quiet now.
When I started writing my response, it was working fine but it just failed as I was finishing this email.
I’m not sure what other steps I can take on the router side. I’ve had Asus routers for several years now and I have never had an issue with streaming through Roon. Perhaps it was the Quad9 dns configuration but that was in place since last year and the issue only started just over a week ago.
It does seems to be specific to Qobuz. I have not been able to reproduce it with Tidal. Although I prefer Qobuz to Tidal, and I’ll use both to see if it’s a broader issue than Qobuz.
Thank you for the additional information and troubleshooting! Following what @Geoff_Coupe has mentioned above, we can fully confirm this is the issue you’re facing. The logs you’ve shared above:
Is exactly the common trace we’re seeing tied to all other users suffering from this issue.
The good news here is that our team is already working alongside Qobuz directly towards a solution. Things are looking good, but we’re still not fully sure on specific timelines for a fix to be released.
That said, we’ll be sharing any future updates to the tracking thread @Geoff_Coupe has shared above.
Certainly, let me know if you’re seeing this issue outside of Qobuz, but otherwise, rest assured a fix is in the pipeline and should be released to you soon!
This thread is now closing due to inactivity. However, you can reactivate the conversation anytime by submitting a new request here if you require further assistance. Thank you.
