· Mac Remote Import repeatedly copies files and creates gigabytes of temporary data when multiple files are dragged into Roon.
Setup: - Roon Remote on macOS, Roon 2.71 build 1683 (production) - Roon Server 2.71 build 1683 (production) - Roon Server runs in an x86 Debian VM hosted on an NVIDIA DGX Spark - The watched music folder is local to the Roon Server and is writable
Source files: Seven stereo DSD64 .dsf files from the NativeDSD Music Starter Pack. The files are valid and play correctly once imported.
Steps to reproduce: 1. Select multiple DSF files in Finder. 2. Drag them into the Roon Mac application. 3. Choose "Yes, copy!"
Expected: Each selected file is copied once to the configured Roon import location and then added to the library.
Actual: The import counter expands beyond the selected file count (observed 15/84 and 17/55), and Roon repeatedly copies the same files. Gigabytes of retry/temp files accumulate, the copy does not finish normally, and force-quitting the Mac Remote is required. Partial imports can create duplicate album entries. Importing files individually can complete, although retry debris may still be left behind.
The Mac Remote logs repeatedly show: System.IndexOutOfRangeException: Index was outside the bounds of the array. at Sooloos.Client.Models.Import._DoPut(Uri uri, Stream toreadfrom)
Reproduced on August 23, 2026 around 16:02-16:07 and 16:25-16:35 EDT. Both complete Mac Remote and Roon Server log archives are available for private upload.
Tell us about your home network
· The Mac Remote, NVIDIA DGX Spark host, Debian VM running Roon Server, and LUMIN endpoint are on the same home LAN. The Roon Server music storage is local to the VM. No VPN or remote WAN access is involved in the reproduction. Router and switch models were not recorded.
Thanks for the detailed report! We were able to review a fresh set of Roon Server logs, and have found the following:
When you drag several files in at once, the Mac Remote opens an import transaction, starts uploading, hits an internal error, and abandons the transaction, then immediately starts over. It restarts every 11–13 seconds, and each retry begins at the same file (the last one in your selection) rather than moving forward through the list. In your 16:01–16:07 and 16:25–16:35 attempts it looped like this 36 times without ever completing.
Two consequences you saw:
The growing counter. Your seven DSF files also carry seven cover-art sidecars plus a folder image, 15 items, which is the “15” in “15/84”. The total keeps climbing because each failed attempt re-queues the work.
The gigabytes of temp data. Uploads are staged in a hidden .tmp folder inside your watched folder and only moved into place when the transaction commits. Across that session 22 files were uploaded and only 8 committed, so 14 full-size DSD64 copies were left behind. Single-file imports work because there’s no list to advance through, but they leave the same debris when a retry happens.
What to do for now
Copy the files directly into your watched folder instead of dragging them into Roon. Your 16:55 attempt did exactly this and it was flawless, all seven tracks, one album, one pass.
To reclaim the disk space, restart Roon Server. It clears that .tmp folder automatically on startup
Worth tidying up: /home/roon/Music/Roon Imports/Mac/ has two imported at … folders from the partial runs, including a duplicate copy of the Vivaldi track. Removing those should clear the duplicate album entries.
With that, we’ve written this up for the development team with the log evidence attached. I’ll let you know as soon as I have an update.
Thanks, and no, you were not doing anything wrong.
One thing we would like you to try, and to tell us the result. Please copy the files from your Mac to the server’s watched folder over the network, using an SMB share to the Debian VM, rather than dragging them into Roon. Then let us know whether the import completes cleanly and whether any temporary files are left behind.
For what it is worth, this is the recommended order generally. Our Nucleus guide puts it plainly: copying over the network is the recommended method for adding music, and dragging into the Roon app is the alternative, best suited to an album or two at a time.
That article is written for Nucleus hardware rather than a self-built server, so the paths in it will not match yours, but the principle is the same and the reasoning in Method 1 versus Method 2 is worth reading.
