I am getting more or less deparate. I am ‘an old time Roon user’. You could even say I am old (67). With some trouble and a little help from my friends I was able to configure my own QNAP TS453. A solid state drive for Roon and two spinning harddisks in RAID 2 for my private music library.
Like many of you, a few weeks ago I was no longer able to use Roon after an update. Support referred me to the community and a step by step instrallation process of Container. As a software end user (and an insecure one for that matter) this was a frustrating experience. The particularities of Container require quite a bit of prerequisite knowledge that (I think) many Roon users lack judging the number of topics started after the aforementioned update.
Although I was able to get Roon running again, I haved not been able to connect Roon with my private music library. I think that by now I have read most of the topics on establishing this, but I just can not succeed! Despite all the kind,patient and elaborate replies on similar questions on this subject I remain at a loss. I just don’t seem to get it.
Can anybody help me out? Harm’s Own is my music folder. What would the exact ‘grammar” of the line connecting Roon to my music library be in my case? And how do I insert this line in the Roon UI to actually make it work. All Ihave been able to attain this far is this:
QNAP is a bit tricky when it comes to compiling the correct share path, for example my experience is that logical volume names like ´DataVol1´ do not work, and top-level folders must be mounted correctly, without duplicate names, then they work without volume names in the path.
From you File Station screenshot, I would try as the second of the three lines, if your second one deviates, this might be the root cause of the problem:
Feel free to share your path in docker generator. If the “´” in the folder name is not part of the script, it should not be a problem, that is why I suggest to share the parent folder /Muziek instead.
“Feel free to share your path in docker generator. If the “´” in the folder name is not part of the script, it should not be a problem, that is why I suggest to share the parent folder /Muziek instead”
Hi Arindal I very much appreciate you effort to help. But I haven’t got a clue about a “docker gebnerator” I am afraid my lack of knwledge on computers and software won’t let me even undertsand trhe explanations I read on this subject on the internet….
You are trying to activate the folders using a wrong method. Sharing a folder path with a container, is not an SMB share over network, but like sharing a local folder. Try instead enabling the “Music Folder” under Settings > Storages, or “add Folder”, NOT “add network share”. If you have previously not altered the docker script, though, this would not work.
Where? In the second share path for the docker script?
Is Docker an application I am supposed to run on my laptop? Idon’t remember having seen the page you sent. I just instlled Roon in Container. Am I so dumb or is this “a little complicated”?
No, Container Station is the app, which is solely meant to be run on a QNAP NAS. It is available in QNAP´s own App Center. This is only applicable if you want the QNAP NAS to be the Roon Server / Core.
On which computer did you install Roon Server in a Container, which operating system (Linux, Windows, MacOS, QTS) does this one have, and with which software did you do the container install?
Your initial post was suggesting you are running Roon Server in a Container on your QNAP NAS under the OS called QTS. Everything I have written, refers to this particular case.
Also, due to the way container folder mappings work, there is a difference between where your music resides on the NAS (outside of the container) and where you have to tell Roon Server it is located (inside the container) since Roon Server runs inside the container.
So for example, once you have configured “/share/Muziek:/Music” (assuming that this is correct) in the docker generator, you will manage your music files (adding, editiing, deleting, re-organising etc using MAC finder [or Windows File Explorer]) exactly as you would have previously using the QNAP share at “/share/Muziek”.
However, for Roon to see these files, Roon Server must be configured to use “/Music”.
I.e. Inside Roon you configure and use the “/Music” mapped folder but outside of Roon you use the QNAP “/share/Muziek” shared folder.
Hi Arindal,
Thank you very much for putting up with this digital dummy!
Yes, I am running Roon Server in a container on a dedicated solid state harddisk in my QNAP. The container app says it is running and I am able to use Roon for streaming Qobuz on my Devialet. My QNAP is running under OTS.
Hi Oram,
This running of aplications in a container is ‘terra incognita’ to me. From your reply I distill that in this particular case sort of have to connect two different digital surroundings with each other. They can work together but under very strictly specified conditions. Am I more or less getting the hang of it???
Then don´t loose hope - the difficult part is done! The only thing left to do is altering the container so that roon sitting in the container, can access the music files.
To achieve this, you have to make a little edit to the original docker script or .YML file or whatever you have given Container Station as a base to get this running. The line which is supposedly wrong, is the second share path, for the music library, which I marked red in the screenshot. The default when generating this docker is /share/Music which is wrong for your folder structure, and must be replaced by:
/share/Muziek/Music
And the container has to be updated/renewed with this altered code line.
Once this is running, you can open roon remote, go to Settings > Storages, and disable the first folder named Music Folder, and click for the folder formerly known as ´Harm´s own´ on
Bewerk deze map
and find the subfolder of the name ´Music´ in the structure under ´Music´. This means you are pointing roon to the different path how to access your music, after moving to the container. Do not open a new folder, and do not try to establish a network location folder, like you have done.
You have already managed to get roon in the container running, and apparently is has restored the database based on backups as well. Don´t worry about the technical aspects of containers, the only thing left to do is giving roon in the container access to your music folder.
“To achieve this, you have to make a little edit to the original docker script or .YML file or whatever you have given Container Station as a base to get this running”
Hi Arin,
In human language this sounds like a very simple task. In this case however it fills me with fright. I haven’t got a clue where and how to perform this minor chore. I don’t know where or how to start. If a screen pops up, I would’nt be able to judge whether it’s the pop up I am supposed to be dealing with. When I alter things I am always afraid that I “screw up”
I once heard of a guy whose wife was in hospital for two days. His wife said he was supposed to cook, which he had never done in his life. He got to boiling potatoes. She had bought him pre-peeled potatoes. He puts them in a pan. and turns on the gas. The potatoes started smoke and to burn. I feel a bit like that guy….
You have to do exactly that what you had done when installing roon in the container. Step by step the same, just the second folder path has to be altered according to my suggestion. I tried to do it for you (including allowing roon in the container to access SMB network share, as you tried it unsuccessfully), open this individual link for your setup and click ´Download to file´ or ´Copy to clipboard´:
and replace the container which is running roon with the new script, or upload the new YML file and update the container. I fully understand you are hesitating, but I can assure you, you have to do the very same thing you had done successfully already, otherwise roon would not be running in the container.
Dear Arindal,
(Wade_Oram,
Jim_F,
DDPS,
Dennis McLauglin)
Thank you all for taking the effort to think along. I finally see that RoonServer is scanning my harddisk library!!!
It is indeed not so extremely difficult, BUT, it never occurred to me that I had to hit “+ Recreate” in Container Station. That is why I never got to the point where I would be able to alter the line! And I don’t remember having ever seen the Windows equvalent of that MAC OS page where I would have been able to specify my Music folder. Maybe I just missed that bit and the container took a default setting?
Anyway, thank you guys for steering me in the right direction!
I think it would have been wise if Roon had thought better about the implications of putting RoonServer in a Container. From my experience as a high end audio sales person I know that perhaps 75% of the more senior streaming audio listeners only have very basic knowledge of the highly comuterized systems they are using. Let alone “the modern way of doing things” in this digitqal world. I think it would have been nice if some effort had been put in in advance to take these Roon users by the hand. I would have appreciated that……
Buenas noches, tengo tu edad y lo que te puedo decir es que conseguí lo del container pero creo que no es lo suyo … despues de estar un poco desesperado compre un mac mini como core y la biblioteca la sigo teniendo en el qnap y funciona y se oye mejor que antes … como dice el refrán “no hay mal que por bien no venga” …
—————
Good evening, I’m the same age as you, and all I can say is that I managed to sort out the container thing, but I don’t think it’s really the right solution… After getting a bit fed up, I bought a Mac mini as the main unit, and I’ve kept the library on the QNAP – it works and sounds better than before… As the saying goes, ‘every cloud has a silver lining’…
.
