Any chance of Headless Plexamp on other RPi Platforms?
I’ve read through the Headless instructions & find them bewildering in parts. I’ve been a Pi user for a few years now and am very happy with Ropieee (XL). Built as a Roon endpoint for the Pi Harry Ten Berge has incorporated support for Airport, Spotify Connect, Squeezelite as well as UPnp/DLNA. It would be great to see Plexamp Headless up there with the rest as more people would be likely to get on board with Plexamp when they see how great it is.
Current setup; I use the Shairport (Airplay2) on Ropieee to cast Plexamp to it BUT i can see the advantages of Headless and I want them.
The best thing about Ropieee for people like me is that it just works and i don’t have to get under the hood and tinker about with code I don’t understand. Same goes for updates & troubleshooting.
Like, what the ■■■■ is this Nodes business?
How about it?
Hey thanks for replying!
Not as yet. I get partway through the readme and chicken out.
Is it as easy as burning the image with Etcher and then inserting into the Pi?
Anything involving ssh and such is above my confidence level.
I don’t understand this node v.16 business that some people were talking about elsewhere.
Burn image using " Raspberry Pi Imager" from here: Raspberry Pi OS – Raspberry Pi
You need to set a user and a password. Default user is “pi”, but other users will work also, just an extra step to remember/execute when installing/upgrading with script.
Login with your user again, and as your user, run the command “node /home/USER/plexamp/js/index.js”, follow prompt to insert token.
Now, again as your user, run “sudo systemctl enable plexamp.service && sudo systemctl restart plexamp.service” to set plexamp to start on reboot, and to run it immediately.
If you need to set an audio-card, or change other settings, go to “ip-of-plexamp-pi:32500” to configure.
Well don’t I look like a dummy? Got it working yesterday and it sounds much better than using airplay with none of that annoying lag.
Confused about something though. Played music for an hour or so, then shut off SSH and closed the PlexPi GUI in browser. Came back several hours later to play music again and couldn’t find it in the list of players, nor could i get the web gui to open.
At a loss what to do next I reconnected SSH then ran the 'node /home/USER/plexamp/js/index.js script and claimed a token again, naming the player again.
Is this something we have to do every time, to get Plexamp Headless to start up?
Hope you can help,
and thank you for the detailed installation instructions Odinb1!
Is there any chance of getting Plexamp Headless to be incorporated in RopieeeXL? Sounds like Spockfish could manage that “by providing several versions of the libraries that they provide as a binary” but I’m not sure I’m detailing exactly what that means correctly. It would be very nice to have my RopieeeXL’s acting as PlexAmp headless endpoints.
I’m a Plex user and member myself, so I’m looking forward to integrate it.
The only thing that holds the integration back are the pre-build libraries against a specific Node version.
And that’s a no go for me: all software that’s included in RoPieee should have no dependencies on certain software versions.
Now, personally I think this is relatively easy to solve: you provide binaries against 2 or 3 Node versions and the problem is gone.
Another possible solution would be for you to allow SSH/console access to the hosts on which RoPieee runs so that users who desire to can manually install Plexamp and its current Node dependency.
It’s not necessary to use the system’s node installation, and in fact I do not on my own headless Plexamp. You can download and extract Node v16.x to a known location to which your user has access and run Plexamp using the full path to the node binary. Something like:
That’s not an option for me: RoPieee is not meant as a generic Linux distro but is an appliance. There are other options (indeed real distributions) that are better suited for this.
RoPieee is meant for people that now nothing at all about Linux: in fact most RoPieee users are totally unaware of the ‘Linux part’.
Does anyone know who owns the decision on what libraries to include? I’m not sure who in the project team are the right folks to ask / highlight this to, but I bet they aren’t on this thread currently as everyone here is a Plex Pass person, and I bet that there is someone on the core team (or whatever decision making entity there is for the project) who could let us know if this kind of thing is possible.
Thanks for tagging @elan - I know he spends time here, but didn’t think he’d be watching this thread. Hope he can shed some perspective on this kind of includes ask.
We’re trying to make it easier for Plexamp to run on as many systems are possible:
We released ARMv7, ARM64 and x64 builds.
We upgraded node to v16.
However, especially with the upcoming multi-room audio stuff, Plexamp does run best on its own (some real-time processes, etc.) So of course our main priority is to make it work well in a smaller set of known/defined environments (Raspbian and Armbian).
Hey Odin
Updating to v4.6.1
Noticed that I didn’t get an option to set audio output during the install. I’m okay changing via web browser but I’d prefer not to have to remember to do it. Is there any script to change it at root?
The fifth prompt is “Do you want to configure your HifiBerry HAT (or clone) [y/N]:” and the sixth prompt is “Do you want to configure your allo HAT (or clone) [y/N]:” so, please re-run the script, and you should see them.
Just answer No (default) to the parts you do not want to re-run.
Apologies. I should have specified. Is it possible to set Dac connected to usb? I can do it in the web app, of course, I just thought there might be an earlier way i’d missed.
Thanks for your time.
