It’s not ‘restricted’ as such.
NAIM simply advise users not to mess with the structure and the content of that folder.
That is why I wrote - provided one knows what one is doing.
I did successfully add folders under my UnitiServ into RIPS/MQ and they were read fine by the UnitiServe. This was on an advice from a trusted source.
So I’m counting that the Core will behave the same.
I thought the Music/MQ folder was read only, although I dare say that could be tweaked.
Otherwise mcjt1’s approach might be the best way forward, but it depends how many albums would have to be edited.
The Core did have a big change a while after release which was when metadata editing was added and at the same time the Core was supposed to respect user edits imported from Unitiserve etc. So Adam’s suggestion might work even if it didn’t in the past. I will be interested!
Best
David
the mac doesn’t give me the option of creating a folder with the MQ folder - it does permit a ‘smart folder’ but not quite sure how they function - if i create a normal folder on the desktop, name it and attempt to transfer it empty that is also not permitted
just tried creating the new folder in the downloads folder, which worked, transferred the content across and still no tracks visible in the app, despite being visible within the downloads and sub-folders - think it might be time for tech support
Adam: it worked for you as it did me! Cool!
Naim certainly recommends users not fiddling with the MQ folder, but I’ve been very careful and it worked for me. The trick is to pay very close attention to what and where you’re putting folders. If ever there were issues with “Unknown Track, Unknown Artist” in the Naim app, despite being Naim ripped tracks, I just pulled the folders back out, reformatted as metadata-embedded FLAC, and stuck them in Downloads.