Intermittent audio dropouts after moving Roon Server to Docker on QNAP (ref#DDW3MO)

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· Roon Server is running on my QNAP TS-1655 using Docker in QNAP Container Station.

Since I had to move Roon Server from the previous native QNAP installation to Docker, I have been experiencing intermittent very short audio dropouts during normal music playback.

The affected zone is a Denon DNP-2500NE. Playback may work normally for a while, but suddenly several brief dropouts begin occurring. I am not changing any settings when this happens.

Restarting the Roon Server container does not solve the issue reliably. The latest dropouts occurred approximately one hour after I had already stopped and restarted the container.

Muse equalisation is enabled. This same setup worked correctly, or with only very occasional issues, before moving Roon Server to Docker.

Could you please check the server diagnostics and logs to determine whether the dropouts are related to Roon Server running in Docker, QNAP Container Station, network communication with the Denon, or another issue?

I would also like to know whether intermittent playback dropouts are a known issue with the current official Roon Server Docker installation on QNAP.

Tell us about your home network

· My home network uses a router ZTE F8748.

The QNAP TS-1655 is connected to my home network by Ethernet.

Roon Server runs on this QNAP in Docker using QNAP Container Station.

The Denon DNP-2500NE is connected directly to the QNAP by USB and is used as a USB DAC. There is no separate computer or network audio endpoint between the QNAP and the Denon.

The network includes standard Ethernet switches, but the audio output path itself is direct USB from the QNAP to the Denon.

I do not use a VPN for Roon.

Hey @J.A,

Thanks for the detailed write‑up! We were able to review a fresh set of Roon Server logs, and with your context, it made this much easier to narrow down.

During playback, Roon Server is doing its job perfectly. Your music is decoded, your Muse EQ is applied, and the audio is handed off with the buffer sitting at 100% the entire time. That’s important, because it rules out the things people usually worry about, it’s not your library storage, not your network pulling files, and not the QNAP being too slow to process the audio. Muse is a light load here and isn’t the cause either.

The dropouts are happening at the very last step: the USB connection between the QNAP and the Denon. A few fingerprints stand out. In one ~40‑minute session the Denon had to re‑establish its timing/clock with the server 14 times (a stable USB DAC normally does this once and holds), and at one point the DAC briefly disappeared from the system entirely (“device not available”). Across the logs, the Denon’s USB connection also repeatedly drops and re‑adds itself. That combination is the classic signature of the QNAP host’s USB power management interfering with the DAC, something that behaves differently under Docker/Container Station than it did with the old native QNAP package, which is exactly why this started when you moved.

So, to answer your direct question: yes, this is a recognized pattern. It’s not a bug in Roon’s official Docker image, the image itself is fine, but intermittent USB‑DAC dropouts after moving Roon Server to Docker on QNAP come up regularly, and the cause is almost always host‑side USB handling rather than Roon itself.

Here’s what I’d try, roughly in order:

  1. Disable USB autosuspend on the QNAP. The host is power‑managing the Denon’s USB port, which is what knocks it offline. Over SSH, first confirm the DAC’s ID with lsusb (look for the Denon / D&M Holdings entry). As a quick test you can turn autosuspend off for that device live; if the dropouts stop, we make it permanent with a small udev rule on the QNAP host so it survives reboots. Send me the vendor:product ID from lsusb and I’ll give you the exact rule.
  2. Change the USB port. Move the Denon to a rear USB port directly on the QNAP (not through a hub), and disable any global USB power‑saving in the QNAP settings. These issues often follow one specific port or hub.
  3. Check the container settings. Make sure your container passes through both /dev/snd and /dev/bus/usb, and is using host networking (host mode is required for Roon’s discovery and audio to work reliably).
  4. Throttle background analysis as a test. Set Settings → Library → Background Audio Analysis Speed to Throttled. Your logs show heavy analysis activity on the same days the dropouts clustered, and easing that off helps confirm whether CPU load is a contributing trigger.
  5. One clean isolation test. Play a local track to the Denon with Muse turned off and see if the re‑syncs and dropouts go away. That tells us definitively whether anything in the audio processing is involved versus it being purely the USB link.

My strong expectation is that step 1 solves it, but the others will either speed things up or confirm the cause. If you can grab the lsusb output for the Denon, I’ll get you the exact autosuspend rule for your setup.

Thank you!

Hi,
I ran lsusb with the Denon switched on and connected via USB.
The device appears as:
154e:1007 D&M Holdings, Inc. (Denon/Marantz)

Please send me the exact autosuspend rule and the steps to make it persistent on the QNAP host.
Thank you.