Again, they are NOT “misconceptions”. You seem to miss the entire point I’ve made earlier many times in other threads as well: A TOC for files and dirs on disk already IS a database, denon does not need to re-invent the wheel and think up a virtual TOC on top of the existing one, which it now does. It’s completely useless and very inefficient use of CPU and storage IO, and it adds a heap of extra problems from there. All the metadata you could want to add to audio-files on disk can be added in any database, as long as it points directly to the file. That’s NOT what denon does, denon re-invents a table of content structure on top of the existing one, accesses its own TOC and then ruins all references to the original location on disk as soon as you ‘sync’ this file/dir to your denon device. This is not how all DJ software works, in fact quite the opposite. Most databases reference files directly, so that when you move it or alter it, it is also moved and altered in your DJ controller/software.
Just look at your internal storage of your Prime 4+, if you have it. You’ll see how denon has decided to store files on it, based on how it decided to recreate the wheel for you, completely ignoring ANY prior organisation you’ve done beforehand. The only organisation and metadata and playlist-content exists virtually, for denon’s own reference table, not any existing file/dir structure. Which means that you can never change anything to audio on your storage without ruining denon’s meta/database contents.