Music playback not functioning (ref#0MHBKH)

What best describes your playback issue?

  • Music doesn’t start when I press “Play”

What type of Zone is affected by this problem?

  • *All of my Zones* are affected.

Does the issue affect all file formats?

  • The issue affects *multiple/all* file formats.

Does the issue happen with local library music, streaming service music, or both?

  • *Only local library *music is affected.

(At the moment I do not have a streaming service.)

Where is your local content stored?

  • On the same machine where RoonServer is running, internal drive

Please try playing content of a lower sample rate (44.1kHz or 48kHz), does this work as expected?

  • No, lower sample rates are still affected

Do you have an approximate timestamp of when the issue last occurred?

  • The problem started (again) yesterday 6 May 2026.

What are the make and model of the affected audio device(s) and the connection type?

  • Synology DS1520+
  • Mac Mini M2 Pro
  • Arcam rPlay

Describe the issue

Music does not playback

Describe your network setup

GL.iNet GL-MT6000 Router

  • Connecting via Ethernet: Roon Core on Synology
  • Connecting via Ethernet: Roon client on Mac Mini as Remote and Audio Device
  • Connecting wirelessly: Arcam rPlay as Audio Device on iPad
  • Connecting wirelessly: Roon client on iPad as Remote and Audio Device

Photo of player

The play head is stuck to 0:0 min, the play animation “plays”, but no sound is to hear.

Did you happen to recently restore from a database backup?

No, I have never restored from a database backup.

Hi @hallo_leo,

Could you please let us know whether anything changes if you reboot your Roon Server? Just to clarify, does the issue also happen when you try to play to the Mac Mini system output zone?

Please also send us the exact local date, time, and track the next time this occurs so that we can review diagnostics around that time-frame.

Indeed, rebooting sorts it out.

Yes, it happens with Mac Mini System output as well.

Ok, it happened again around 9 May 2026, 10:10am my time. I checked it is the same on the Mac mini (running one Roon Client) and on the NAS (running the Roon Server).

  • Song I played before it happened (Path on the RoonServer NAS):

    /var/packages/RoonServer/target/roonmnt/music/core/Classical/\_VariousComposers/Memory/15 Breathing Light.m4a

  • Song I played when it happened (Path on the RoonServer NAS):

    /var/packages/RoonServer/target/roonmnt/music/core/Classical/_VariousComposers/Memory/15 Breathing Light.m4a

Then I rebooted again - and now Roon is playing audio again. :grinning_face_with_smiling_eyes:

  • A Song I played since this reboot (Path on the RoonServer NAS):

    /var/packages/RoonServer/target/roonmnt/music/iTunes Music/Augie March/Moo, You Bloody Choir/01 One Crowded Hour.mp3

Hope this helps, narrowing things down.

Hey @hallo_leo,

Thanks for the update! From a fresh Roon Server diagnostic report, we can see that at the exact moment playback “starts”, the log shows:

19:05:52 [prebuffer] short read: 0 / 8820 fill=0
19:05:53 [prebuffer] short read: 0 / 8820 fill=0

This means Roon’s pre-buffer is completely empty (fill=0). The RAAT audio pipeline is being handed a stream, but there’s no audio data in it. The clock continues ticking internally (the RAAT endpoint reports PLAYING) but the position never advances because no audio frames are actually being consumed.

This is a buffer starvation condition: the server starts playback before it has filled the buffer, and then can’t fill it.

Worth noting - the stuck-at-0:00 events seem to only occur with LowQuality (AAC) files. When playback works normally (e.g., the Memory album ALAC files on May 7 afternoon), the signal path shows Enhanced or Lossless and the buffer fills to 100% immediately.

Here are some next steps to try:

1. Let audio analysis finish before playing. After a reboot/restart, wait 10–15 minutes before playing. Watch for the analysis to complete in Roon: Settings → Library → check if “Analyzing audio files” spinner is still running. Only start playback when it’s idle. This directly addresses the resource contention.

  1. Throttle background audio analysis. In Roon: Settings → Library → Background Audio Analysis Speed → set to “Throttled” (or “Off” if you want manual control). This prevents the analysis process from competing with live playback.

  2. Separate your Voice Memos / corrupt files from the music library. The logs show Roon repeatedly trying and failing to analyze a large number of Voice Memo .m4a files and some corrupt MP3s (e.g. the Sulari Gentill audiobook file). These cause constant analysis noise. Move or exclude those folders via Settings → Storage → Edit the watched folder → use the “Organize” or exclusion options.

Thank you! :folded_hands:

Thanks heaps for the detailed reply.

I will look through my library and clean it up!

I have set the Analysis to Off:

However when I play the following song

Title: Bomboloni
Artist: Gianna Nannini
Path: /var/packages/RoonServer/target/roonmnt/music/iTunes Music/Gianna Nannini/Bomboloni/01 Bomboloni.m4a

the playback stops again. This happened on 13 May 2026 at 18:31.

This file is not corrupt: The VOX audio player on my Mac can play it perfectly.

What can I do about this?

Hi @hallo_leo,

Thanks for the timestamp! From a fresh Roon Server diagnostic report, we can see the log clearly shows a manual pause of the track, 10 seconds into the song. Did playback stop by itself, or did you (or a remote/app) pause it?

If it stops by itself on other occasions, the culprit is more likely to be your Roon Remote client disconnecting (as happened at 18:35:32 — the Mac at 192.168.8.199 dropped off the network), which can abort playback mid-song.

On the Mac Mini: open System Settings → Battery (or Energy Saver) → uncheck “Put hard disks to sleep when possible” and set display sleep independently from system sleep.

Also check System Settings → Network → Wi-Fi (or Ethernet) → Advanced and disable “Wake for network access” if it is causing erratic re-connections. If the Mac is on Wi-Fi, switching to Ethernet almost always fixes this class of problem.

I’d also test out temporarily disabling your macOS firewall, and see if the same issue occurs.

Thank you! :folded_hands: