Files on My NAS Drive

galegovision - September 16, 2026

Once it does finally finish adding, how is the performance playing over the network? Just curious.

blobby - September 16, 2026

superb no issues

Rick - September 16, 2026

Hi @blobby

First, a clarification: Digital Center does not re-read your 5 TB at every start. Every track's details are kept in a cache on the local disk, and a file whose date and size are unchanged is never touched again. What still happens is a quick pass through the folders, to see whether anything was added or removed while the kiosk was off - and over a network drive that pass is what takes the time, because every folder is a separate round trip to the NAS.

Since version 6.0.25 that pass runs in the background: your music should appear immediately from the cache, and you should be able to browse and play while the check finishes. If you are sitting and waiting for it, something is not working as it should, and we would like to get to the bottom of it.

Digital Center can hand us everything we need in one go:

• Restart Digital Center.
• When it has come up, press Ctrl+D.
• Click Show log, then Copy.

Please do that shortly after a restart, while the timings are still fresh. Send the log to our support. Please don't paste it here: it contains your machine's ID and your folder paths, and it is a fair bit of text.

A quick "sent" in the thread would be great, so we know to look for it.

One thing in particular we want to check: while Digital Center is running, it asks Windows to tell it when files change, so it only looks at what actually changed - which is exactly the behaviour you are after. Some NAS boxes accept that request but never send the notifications, and then we fall back to checking the folders on a timer instead. If that is what is happening on yours, it explains what you are seeing, and it is something we should fix rather than something you should work around.

blobby - September 21, 2026

Hi Rick

did you get the files i sent ok ?

Rick - September 22, 2026

Thank you - those logs were exactly what we needed, and what you described is what confirmed it.

You found a real bug, and you described it perfectly. Here is what was happening. The first time Digital Center sees a music library it has to go through every folder once and build an index. On a normal internal drive that takes seconds. On a 5 TB library over a network share it can take a very long time, because every single folder has to be asked for over the network.

The problem was that the index was only saved once that entire pass had finished. So when the screen appeared to hang and you closed it, everything it had read was thrown away - and the next time you opened it, it started again from zero. That is the loop you were stuck in, and it is also why a reboot behaved differently: on those occasions a pass had been allowed to finish at some point.

On top of that, the music screen was waiting for the whole pass instead of showing you what it already knew, which is why you eventually got an error instead of your music.

Both are now fixed in the next release:

• The library index is saved as it goes. If a pass gets interrupted, the next start picks up where it left off instead of starting over.
• Music Center now opens immediately and tells you the library is being scanned, with songs appearing as they are found - no more staring at nothing, and no more error message.

One thing to be aware of: the slowest part on a network share is simply counting the files, before a single song is read, and that part still has to happen once. So there is still one patient pass to get through - but you no longer have to do it in one sitting, and you will be able to see it making progress the whole way.

In the meantime, there is something you can do today that will fix it on your current version: open Music Center once and leave it completely alone until the music appears, however long that takes - do not close it. That one completed pass writes the index, and every start after that will be fast. It is the closing partway through that keeps resetting it.

We will let you know as soon as the update is out.

Thanks again for sticking with this and for sending the logs - they made the difference.