· Can Roon log in and setup my dedicated surface pro as the server for more reliability. I have tried everything to keep it awake and not drop tracks in the middle of playing. I have a robust high speed mesh network, multiple tv can stream 4k without any issues. I don’t need a Nucleus I have a Wiim ultra connected to a dac usb. Only using Wiim as streamer and only stream music. Thanks for the help, Bill
It sounds like you are trying to use the Surface Pro as a dedicated Roon Server, and the playback dropouts are likely tied to how Windows is keeping that machine awake and connected.
Before we go further, a few things would help us narrow this down:
Is the Surface Pro connected to your network over WiFi or Ethernet?
What version of Windows is it running?
When the tracks drop, does the Surface actually go to sleep, or does Roon stay open and the audio just stops?
In the meantime, the two most important things to check on a Windows server are power settings and network sleep behavior. We want the Surface to stay awake, keep the network adapter active, and avoid any USB power-saving settings that could interrupt the Wiim or DAC connection. If you have not already, also make sure the Surface is plugged in and set to never sleep while Roon Server is running.
I think the next step here is to enable some diagnostics on your account so our technical staff can get some more insight into what’s going on here.
However, before I enable this feature, I’d like to ask for your help ensuring we gather the right information.
First, can you please reproduce the issue once more and note the time at which the error occurs. Then respond here with that time, and I’ll make sure we review the diagnostics related to that timestamp.
If you can share those details, we can tell you whether this looks like a Windows power management issue, a network issue, or something specific to the USB path.
Just checking in on this. Were you able to try the power and network sleep settings we mentioned on the Surface Pro, and confirm whether it is connected over WiFi or Ethernet, what version of Windows it is running, and whether the Surface is actually going to sleep or Roon Server stays open while the audio stops? If you were able to reproduce it again, please send us the time it happened so we can line that up with the diagnostics we want to review. Please reply with any updates or questions.
Please note, if we don’t hear back from you this thread may close automatically soon. If the thread auto-closes and you need further assistance, please submit a reopen support request via the technical support help form below and specify that the issue should be reopened. Thank you.
Just following this as I was expecting the response that snapdragon based devices aren’t supported. Can you explain the position here?
The graphic issues seen (or perhaps better described as “not seen” , i.e. invisible text) on search and other text entry certainly make this challenging to use.
I had understood the fix was taking a very long time because it was not yet part of the ‘authorized support’.
I flag this as a warning to anyone trying to use the app on this type of device - but is the server seen as OK?
The issues affecting Snapdragon-based Windows tablets/laptops are limited to the GUI (Roon Remote). You may find that text renders invisibly and the app itself might crash/hang. If that doesn’t match your symptom, we’ll definitely need to look into this more.
Interruptions during playback (the middle of a track) wouldn’t be related to the chipset, and can arise from 1) accumulated dropouts during uncompressed audio transport over WiFi (most common), 2) hardware limitations (like RAM) that limit the Roon Server’s ability to perform DSP and background functions at the same time (less common, but depends on the machine).
When tracks fail to play entirely and won’t start within Roon (or play silently), that’s often because the audio source (streaming service servers on the internet or your storage) isn’t delivering data as expected. This isn’t always true, but it causes the vast majority of cases.
We don’t have logs from your account available except from about a week ago, but examining those diagnostics, we can see two things happening:
In some cases, Qobuz failed to deliver data via their API. This is a known issue with Qobuz that their team is working to resolve. This causes tracks to never play at all:
In most cases in your logs, we see a WiiM endpoint (and other endpoints) re-requesting samples that have dropped out over the network. This causes interruptions and pauses mid-track.
This wouldn’t be a question of network speed, but sustained throughput of large volumes of data. What is the make/model of mesh setup you’re using? We can recommend specific settings.
How do you have this laptop connected to the network? Is it hardwire, or relying on WiFi? If the latter, are you relying on an AP or the main router?
What about the WiiM?
We’ll watch for your reply. Thanks again for your patience.
I think your responding to the wrong issue / person. I don’t have any other issue than the hidden text in search and when trying to name outputs displays in settings. I didn’t raise the issue about Quobuz but I am trying to understand if ROON officially supports Snapdragon based players - in the hardware guide you specifically indicate surface and surface pro are supported, elsewhere there are indications they are not. If supported, I’m just trying to encourage this being prioritized. I don’t have a WiiM and my roon / quobuz and tidal set up performs great (apart from the know cases of specific Quobuz tracks occasionally not being there !).
Thanks anyway for following up - I realize there are many competing requests for attention!
So broadly speaking, Snapdragon-based players are supported by Roon as Windows devices, but they’ve faced some hiccups that were in the pipeline until very recently. These issues were enough to fundamentally break the user experience; as a result, we issued communications advising users to temper expectations for Snapdragon-based Surface/Surface Pros for now. The invisible search bar was the main bug, but there will be scrolling issues and other visual artifacts with font rendering.