Step 1. Understood. Step 2. I assume I’m logging in to the new Raspberry Pi. Do I need to buy a screen for that too? I’m not ever going to use it for anything else. Also, I assume it won’t recognize my wireless keyboard and mouse. Or can I simply login to some web interface as instructed here for installing PuTTY? Download and Install PuTTY. I have downloaded both the Windows 64-bit version and the Linux version. Which do I use? I know how to install the Windows version - no problem. Will that then work like Balena Etcher and transfer needed files over to the new Raspberry Pi? Or do I need to install that as a Linux program directly onto the Raspberry Pi? I’m not proficient in Linux. Is there some place I can learn how to do that installation (if it must be by Linux)?
I’m trying my hand with a Windows 10 machine before plunking down another $100 or so on a new Raspberry Pi, case, power supply, SD card… So I finally got the Extension Manager to run as a Windows service, and it appears in Roon as “The Appgineer.” I wanted to install Deep Harmony, but The Appgineer only offers an extension known as “Doc Bobo.” That extension does not recognize my Harmony Hub. I have a FLIRC plugged into my Raspberry Pi with a touchscreen. That Touchscreen Pi can and does control Roon music. It shows what’s playing and you can skip songs using it. Not much else. The FLIRC which is plugged into it is as it came from the box. (I have no physical remote to be configured.) The web interface for the Touchscreen Pi “sees” the FLIRC. The Harmony Hub is situated right next to the FLIRC, and it is plugged in. What now?
OK so it seems to me the original point of this thread got lost, installing on ROCK. When I look in my Settings I see Extensions but there are no discovered extensions. So is this because I do not have Extension Manager installed? Seems funny to have the setting but not have it installed. Assuming it comes on ROCK then is there some discovery endpoint that needs to be configured? I cannot find any clear instructions on getting Extensions working on my Intel NUC running ROCK 227 OS, 667 Roon.
Hi @Todd_Haugen I have been where you are and will give you the same advice I got.
Roon Rock is a locked down distribution of Linux that you can not add any extensions to.
Get a Raspberry Pi and install a Linux distro on it.
I use a DietPi solution for running Roon extensions and Roon Bridge to allow me to play to other devices (USB DAC etc).
Works great and you can be up and running in 20-30 minutes.
You can download it from the following link and follow some of the instructions further up in this thread
so I was assuming that either the entry points and gateway can be co-hosted or the core and the gateway. So can the entry point and the gateway be co-hosted or does image 2 need to be updated to show a gateway too?
@Todd_Haugen You are right to be confused as many of us have been and you generally have to read through dozens of messages to get the pointers that it does not work the way we think it does.
If you wanted to install of a Linux distro like Ubuntu on X86 hardware or wanted to run in on Windows then all good. Rock is a locked down distro so you cannot install any other software and the extension manager and extensions are third party.
I am happy with my Rock (Roon Server) & DietPi (Roon Bridge and extensions) combo for my living room, but everyone has slightly different requirements and skill sets.
Glad to hear that you got it sorted. I do not listen to radio stations, I am pretty much an album listener, almost exclusively.
Though some Tidal playlists have really caught me recently and occasionally rune radio can also be good
I don’t see a useful solution here, buying a additional device and feed it with energy can not be the final solution for using extensions in a ROCK driven environment. I changed my NUC from windows 10+roon to ROCK just today, and now I’m a little bit shocked, how (sorry for the harshness, but it’s the way it is:) stupid the extensions “management” is ment to be on a ROCK. Gives the name a truely new interpretation: as flexible as a rock…
Is there any chance, that there will be the opportunity to run extensions on a ROCK? Without it’roXs! the usage of roon is stone-age-style on any android device.
You’re misunderstanding how it works: the core does the dsp weightlifting, and sends a data-stream to the endpoint for rendering. Thus, a pi4 is more than capable of performing under all circumstances.
you misunderstood me: I run one core (ROCK) and one endpoint. The core does the DSP, that’ right, the endpoint renders the stream, correct too. So, where is the pi4, which I acutally don’t need in this setup at all?
Why is roon not capable of managing plugins on their own, self-designed server software? That’s the question, and I don’t want to offend anybody, but I think that question only a roon official could answer.
Rock is designed to be a closed system, an appliance which cannot be tweaked or modified by the user. By definition, hosting extensions which are written by 3rd parties breaks this design goal.
If you want a two device setup which also runs extensions, then you need to either be able to run the extension manager on the Core or on the endpoint. For a Core, you would use an OS which will allows this, Linux or Windows for the core. For an endpoint, the easiest is to have a Pi running DietPi with the appropriate endpoint HAT to feed your DAC.
Through this tread, I started with using Win 10, then switch to a Pi. However, now I use Win 10 not only because I run extensions (actually I run DietPi as the extension manager under a VM under windows, works great), but, also because I like to monitor temps and have the option to run a quick hardware diagnostic if I want.
Also, the extension manager can be run on any Windows 10 machine that is currently on. It doesn’t even have to be part of the audio chain. The device running the extensions just needs to sit on your network somewhere.