Oh. I was trying this On The Pi itself. with the idea of displaying a full screen view of plexamp web.
I still want to mainly controll the Pi endpoint from a mobile device, but if the pi displayed what was playing like the plexamp does it would be cool.
Im a noob obviously…so it seems weird to be putting in the ip in the browser of the device im on. i.e. 192.168.1.xxx:32500. Is thatb what should be done if you want the interface on the pi itself?
i don’t understand the question. headless plexamp can be headless (not have any ui). or control it with any other plexamp (including the web app which the headless app can serve up).
Yeah maybe I’m a weirdo. Don’t you love it when your users use your product in a way you never expected
Well yep. My use case…
So my streamer it in my studio wifi only. Both my wife and I work there and we share the plexamp account so we can controll the same playlist from iphone and Android.
We’re artists, we have dirty hands often and dont want to touch the phone when we need to turn volume, see who’s the artist, of this song or mute for a phone call, so I have the hardware encoder so a real volume/mute knob is available.
Then we have a studio assistant who we don’t want controlling our Plex playlist who may want to change the volume or track.
So most of the time headless works, but changing volume I want a real dial to turn. Then I’d like to look and see what’s playing or skip the track without getting out my phone.
So the (non headless) idea of having a touchscreen on the pi streamer that shows me what’s playing and I can skip a track is attractive to me.
If I was back in the city, in an office, at a computer with my phone in front of me things would be different.
that should work, i have another Pi which runs chrome in kiosk mode for something totally different. not sure what the crash you’re seeing is. others may be able to help or maybe in a raspberry pi forum as well.