That is not a bad thing per se, it just means you didn’t link any “cloud players”.
I see. Any idea of what else it could be? I still do not see the headless app in my devices to cast to. Still cannot play anything either. I have tried different browsers and even different devices. Was really hoping to get gapless whole home audio in a headless fashion. I should be able to pipe the audio from Plexamp directly into Snapcast (via an alsa loopback). That is the ultimate goal in all of this.
I believe this is the core of the issue.
Please zip up all the logs on the Pi and send them over, I want to see the startup sequence.
Here are the logs. Also may help, I see this in the firefox developer console when i try to play music from the http://rpi-ip:32500/.
PlayQueue: Exception executing task this.app.audioController.disableStateUpdates is not a function TypeError: this.app.audioController.disableStateUpdates is not a function
log.zip (19.8 KB)
It’s almost 100% guaranteed you haven’t selected the Pi as the player in the cast menu to see that error.
This was using the UI provided by the headless player, sorry for the confusion. I will try to make a video of the issue tomorrow, it may be more clear then. Currently I am just trying to use the UI in the web browser to play music. Beyond that issue the headless device does not show in any plex cast menu.
Being that the logs on the file system show nothing I was hoping that the error from the browser console would help. I am currently checking my server logs for anything that may stick out.
Not at all. There’s an annoying issue with the current version where you have to select the right player before playing, even when the Pi is serving up the UI.
Ok so progress has been made. I was unaware of needing to pick the device even when using the web ui it provided. It kind of worked, the Pi is playing things really garbled, my desktop (which is just to test with) is playing things sounding fine. I have not bothered to look at the Pi audio issues because I will just nuke it and start over and see if that solves it, if not I will beat my head off of it a bit and see what I can figure out.
To make the next part less confusing I will define some things.
Plexamp devices
slaveone: debian 10 desktop
work: windows 10 surface that was provided by my employer
phone: pixel 5a
tablet: some newer fire hd 10 tablet
Plexamp headless devices
foo: rpi 2 with the sole intention of testing plexamp headless
desktop-test: running on slaveone because i testing locally is easier than on the pi
Cast Devices
MU/TH/UR: Chromecast Audio
Living Room TV: Some google tv dongle
I a 5ghz and a 2.4ghz wifi setup but they are on the same network. Most of my house is wired with cat6, this is also the same network as the wireless.
The following are what devices can see what in the cast menu. This is where it gets quite odd.
Phone
- Living Room TV
- MU/TH/UR
- Work
Tablet oddly this can see more than any other device. when i opened the app it was frozen. i force closed and reopened and had to reauth. still it does not see all of the devices it technically should.
- Desktop-Test
- foo
- Living Room TV
- MU/TH/UR
- slaveone
slaveone
- Phone
- Desktop-Test
- foo
Work
- Phone
I had the same exact thing happen to me. Where it says Plexamp is signed in and ready. That doesn’t mean the service has started running yet. Its simple to fix, just go back into the terminal cd plexamp node js/index.js
Then you will see Starting Plexamp 4.3.0 and you will probably see some weird error that says no provider or something similar. Once you see that there should be a white block on the terminal that is Plexamp running. Then go over to the Plexamp on your phone or reach it via the web browser and you should be able to see the device and select it for casting.
Any updates on the garbled audio?
I’m still trying to wrap my mind around a Pi 2B running 64bit raspbian lite.
Any instance I’ve seen of this was a weird install or alsamixer levels set wrong. Plexamp output is bit-perfect with loudness leveling and sweet fades off.
I had this on my pi3 but did not look into it before I wiped it. If it happens again I will let you know so that the needed info can be shared.
So I finally managed to install the headless player on my RPI 4, all went well and the player was working. After rebooting and starting Plexamp again I get the message “DEVICE: No provider for source 170d0cc673e42c89d97c357b89adafce5e78ddf5” and I can’t play anything from it (it is RPI with a 7 inch touch display) Browsing works but no pictures are showing and when I choose a song it’s just an off centered spinner. The strange thing is that I can cast to the device from my phone but no reactions on the actual player.
What am I doing wrong?
To be added I am fairly new to RPI’s but I managed to install Node v12 and the Plexamp, and it worked one time at least so I am pretty pleased with myself so far 
Setup: RPI4 with 7 inch display connected to a USB DAC.
an rPi with a 7" display sounds like an rPi with a head
2 Likes
If you’re using the browser, make sure you’ve selected a player from the cast menu. It should be defaulting but older versions didn’t.
Problem solved, almost. I had disconnect and then reconnect the player. The problem I have now is that no album arts are displayed on the 7 inch monitor. No problems if I connect from another computer…
So true, I like heads
fixed in the next release.
1 Like
an rPi with a 7" display sounds like an rPi with a head
Just because you have a head doesn’t mean you always want to use your head. Maybe your head is otherwise occupied and having an out-of-band interface is useful.
I apologize for trying to make a joke.
