Suggestions for the future: Headless RPi support!

pjv · January 29, 2019, 12:13pm

OK, that got it running.

Not official, but at least semi-usable below.

Here’s the working Dockerfile and docker-compose.yml that I am using with version 2.0.0b2:

Dockerfile:


FROM node:9-stretch

RUN apt-get update && apt-get install -y libasound2 && \
  rm -rf /var/lib/apt/lists/*

RUN wget --no-verbose https://files.plexapp.com/elan/Plexamp-v2.0.0-rPi-beta.2.tar.bz2 && \
  tar xjf Plexamp-v2.0.0-rPi-beta.2.tar.bz2 -C /root && \
  rm Plexamp-v2.0.0-rPi-beta.2.tar.bz2

COPY server.json /root/.config/Plexamp/


ENV LD_LIBRARY_PATH /root/plexamp/resources/helpers/linux-arm
ENV LD_LIBRARY_PATH /root/plexamp/server/node_modules/treble/build/Release/
ENV PLUGIN_PATH /root/plexamp/server/node_modules/treble/build/Release/

EXPOSE 20000
ENTRYPOINT ["node", "/root/plexamp/server/server.prod.js"]

docker-compose.yml:


version: '2'

services:
  plexamp:
    container_name: plexamp
    build:
      context: ./
    image: plexamp:v2.0.0b2
    devices:
      - "/dev/snd:/dev/snd"
    network_mode: host
    restart: unless-stopped

Put both of them in a directory together with the server.json file and then docker-compose up -d.

I am able to run this and it seems to work fine with either the Android plex client or the web client running in my browser. When I try to fling to it from the Mac desktop plexamp it didn’t work. The Mac plexamp throws an error notification telling me that it couldn’t switch to the remote and the logs from the pi plexamp give me this:

plexamp    | error: Unhandled Rejection! Missing attribute value for attribute playQueueVersion of element Timeline
plexamp    | error: Error: Missing attribute value for attribute playQueueVersion of element Timeline
plexamp    |     at new e (/root/plexamp/server/server.prod.js:1:2675564)
plexamp    |     at n.e.exports.n.attribute (/root/plexamp/server/server.prod.js:1:2693270)
plexamp    |     at n.e.exports.n.attribute (/root/plexamp/server/server.prod.js:1:2693167)
plexamp    |     at new n (/root/plexamp/server/server.prod.js:1:2692499)
plexamp    |     at n.e.exports.e.node (/root/plexamp/server/server.prod.js:1:2697055)
plexamp    |     at n.e.exports.e.element (/root/plexamp/server/server.prod.js:1:2696053)
plexamp    |     at n.e.exports.e.ele (/root/plexamp/server/server.prod.js:1:2700037)
plexamp    |     at /root/plexamp/server/server.prod.js:1:749003
plexamp    |     at Generator.next (<anonymous>)
plexamp    |     at r (/root/plexamp/server/server.prod.js:1:746625)
plexamp    |     at /root/plexamp/server/server.prod.js:1:746719
plexamp    |     at <anonymous>
plexamp    |     at process._tickCallback (internal/process/next_tick.js:182:7)

elan · January 29, 2019, 11:30pm

We’ll be adding support for specifying the output sample rate (as well as device).

elan · January 29, 2019, 11:32pm

Hmm, that shouldn’t be a fatal error

Rob_A · January 30, 2019, 11:54am

Thanks for the info.
From previous comments I thought that Plexamp (or MPD) only changed the original sample rate if the output device was not capable of handling the original rate. Is it currently coded so that it always outputs 44.1kHz? Rather than choose the output rate I would prefer that it just used the original rate.

OttoKerner · January 30, 2019, 12:12pm

V2 is not using mpd anymore.

pjv · January 30, 2019, 4:13pm

oops, sorry i wasn’t paying very close attention to what you wrote there since this topic is specifically about running plexamp on a pi. I just noticed that you were asking about running it on a NUC. pretty sure the arm binary architecture of the stuff in this image won’t run on a NUC.

holger · January 31, 2019, 11:28am

Are there any plans of integrating multiroom audio support for plexamp V2?

Przemo · February 2, 2019, 9:51am

Where can I DL v2.0 beta for desktop?

afewyards · February 3, 2019, 10:54pm

After upgrading to the 2.0 all the playback stutters, tried all different bit rates. I was using a altered MPD before:

audio_output {
type “alsa”
name “my ALSA device”
device “plexamp”
format “192000:24:2”
mixer_type “software”
}

bind_to_address “127.0.0.1”
port “36600”
buffer_before_play “20%”
audio_buffer_size “2048”

log_file “/tmp/mpd.log”

chewyf5 · February 10, 2019, 11:40pm

Hello,

i post a small HowTo for my successful setup on raspberry pi in combination with snapcast:
https://forums.plex.tv/t/headless-raspberry-plexamp-paired-with-snapcast/374263?u=chewyf5

Regards
Chewyf5

elan · February 12, 2019, 7:57pm

It’s not available yet.

elan · February 12, 2019, 7:58pm

v2.0 doesn’t use MPD at all, so the configuration wouldn’t impact anything.

afewyards · February 14, 2019, 3:20pm

It was more a point of reference. I did try to adjust my asound config to align bitrates without success. It would be great if we could somehow select our output device and select the bitrate that we want to export it as.

r100gs · March 19, 2019, 1:28pm

@pjv

Hello,

I tried to install it on a raspberry zero w
docker V 1.5-1 is installed
docker-compose is installed

but I get this error

docker-compose.yml Dockerfile server.json
pi@musik-plex:~/plexamp_docker $ sudo docker-compose up -d
ERROR: Couldn’t connect to Docker daemon. You might need to install Docker:

https://docs.docker.com/engine/installation/

What can I do?

Best regards,
r100gs

knifesk · May 7, 2019, 6:48pm

Worked out of the box in RPi2 b+ with Raspbian Stretch! thank you man!

jdefockert · May 23, 2019, 8:23pm

Hi, I managed to install it just fine, but I run into to issues.

Plexamp has exclusive access to the sound card, requiring me to stop the service to allow other programs (in my case Roon Audio) to play music.
Plexamp generates a beep sound every 90 seconds or so when it is running. Whether music is playing or not.

Thank you in advance for your feedback.

MrChriiis · June 19, 2019, 9:55pm

Followed the instructions for the new beta but still having issues with the dependencies. Get this when I run server.prod

I’ve added the new environment variables into the services file so don’t get why this is still a problem, any ideas?

tomsimmons · June 27, 2019, 7:54pm

@jdefockert Did you resolve this issue? I had the same thing.

Tom

tomsimmons · June 27, 2019, 8:03pm

I’ve actually broken it now.

I had a fresh install of Raspbian Desktop without the recommended software, a fresh install of Plex Server, then added Plex Amp v2b2. Initially it worked fine, then a few hours later while I could select PlexAmp from another device to fling to it would instantly drop back to the local device, no error given.

I then found that I could no longer play from the server web client, then found that I couldn’t use VLC either - device/resource busy. Eventually found that by stopping PlexAmp VLC worked.

I tried installing the old version of PlexAmp, that didn’t go well so revert to v2b2. Now despite the service running I can’t select PlexAmp to fling to, and back to VLC not able to play unless I stop PlexAmp.

Where do I find the logs? Any idea how I can remove and clean everyting to get the old v1 version running?

Tom

tomsimmons · June 28, 2019, 7:35pm

OK, currently I’m trying to use v 1.0.5, it’s installed, and from running manually it appears to be working…

debug: DEVICE: Loaded 7 devices.
info: [PUBSUB] Connecting...
debug: CODEC: Checking for device identifier in /home/pi/.local/share/Plexamp/Codecs/.device-id
debug: CODEC: Read 45b9d896-b966-4a8d-bb92-073119f02c54
debug: CODEC: Initialize complete.
debug: DEVICE: Initializing manager.
debug: DEVICE: Fetching latest provider list from cloud.
debug: DEVICE: Fetching latest list from cloud.
debug: DEVICE: Starting connection test.
debug: DEVICE: Finding best connection for LittonPlex
debug: HTTP: Issuing request to https://127.0.0.1:32400/
debug: HTTP: Issuing request to https://192.168.1.110:32400/
debug: HTTP: Issuing request to https://192.168.1.109:32400/
debug: HTTP: Issuing request to https://86.147.151.126:1027/
info: [MPD] Started, now we will connect
info: [MPD] Connecting...
info: [MPD] Ready!
debug: [MPD] Not restoring a play queue.
debug: DEVICE: Server connection worked for LittonPlex ~ https://127.0.0.1:32400
debug: HTTP: Issuing request to https://127.0.0.1:32400/library/sections
debug: DEVICE: Server connection worked for LittonPlex ~ https://192.168.1.109:32400
debug: DEVICE: Server connection worked for LittonPlex ~ https://86.147.151.126:1027
debug: DEVICE: Server connection worked for LittonPlex ~ https://192.168.1.110:32400
info: [CLOUD] Registered device.
debug: DEVICE: 1 libraries at LittonPlex: Music
debug: DEVICE: Fast-path connection testing.
debug: DEVICE: Finding best connection for P20
debug: HTTP: Issuing request to http://192.168.0.2:32500/resources
debug: DEVICE: Finding best connection for Litton PlexAmp
debug: HTTP: Issuing request to http://192.168.1.110:20000/resources
debug: HTTP: Issuing request to http://192.168.1.109:20000/resources
debug: DEVICE: Finding best connection for Chrome
debug: HTTP: Issuing request to https://192.168.1.110:32400/resources
debug: HTTP: Issuing request to https://192.168.1.109:32400/resources
debug: HTTP: Issuing request to https://86.147.151.126:1027/resources
debug: DEVICE: Finding best connection for M4800
debug: HTTP: Issuing request to http://192.168.1.110:20000/resources
debug: HTTP: Issuing request to http://192.168.1.109:20000/resources
debug: DEVICE: Persisting devices.
debug: DEVICE: Initialization finished in 480ms.
debug: METRICS: Initializing.
info: [EXPRESS] Listening on port 20000
debug: DEVICE: Fetched 7 devices from the cloud.
info: [PUBSUB] Connected.
debug: GET /resources 200 325 - 28.036 ms
debug: GET /resources 200 325 - 3.908 ms
debug: GET /resources 200 325 - 2.022 ms
debug: GET /resources 200 325 - 2.031 ms
warn: DEVICE: The player 42c96014-abe2-4340-b9ed-46da8ad0c2a4 wasn't found in available resources at http://192.168.1.110:20000.
warn: DEVICE: The player 42c96014-abe2-4340-b9ed-46da8ad0c2a4 wasn't found in available resources at http://192.168.1.109:20000.
warn: DEVICE: Connection testing failed for Litton PlexAmp
warn: DEVICE: The player d3dd39a1-2507-4498-9aff-99fbc683a08c wasn't found in available resources at http://192.168.1.110:20000.
warn: DEVICE: The player d3dd39a1-2507-4498-9aff-99fbc683a08c wasn't found in available resources at http://192.168.1.109:20000.
warn: DEVICE: Connection testing failed for M4800
warn: DEVICE: The player g3xm4x0g75v64x84l1vo1kps wasn't found in available resources at https://192.168.1.110:32400.
warn: DEVICE: The player g3xm4x0g75v64x84l1vo1kps wasn't found in available resources at https://192.168.1.109:32400.
warn: DEVICE: The player g3xm4x0g75v64x84l1vo1kps wasn't found in available resources at https://86.147.151.126:1027.
warn: DEVICE: Connection testing failed for Chrome
debug: METRICS: Saving latest cloud settings for metrics.
warn: DEVICE: Player connection http://192.168.0.2:32500 didn't work for P20: timeout of 5000ms exceeded
warn: DEVICE: Connection testing failed for P20
debug: DEVICE: Persisting devices because LittonPlex was dirty.
debug: DEVICE: Persisting devices.

However when I open up Chromium on the Pi launch the Plex web interface and click the Select Player the Plex Amp isn’t listed.

Anyone any ideas?

Tom

Topic		Replies	Views
Future of Plexamp on Raspberry Pi? Plex Labs plexamp	250	15049	May 4, 2022
Plexamp 3.0 for Raspberry Pi? Plex Labs plexamp	60	2800	April 11, 2022
Can I cast to PlexAmp For Raspberri Pi From plex app on Mobile? Plex Labs plexamp	29	1733	April 3, 2021
PlexAmp-installer for Raspberry Pi with ARMv7 & ARMv8 HW Plex Labs plexamp	35	1827	July 23, 2021
Plexamp headless not playing music Plex Labs plexamp	63	1385	June 18, 2023

Suggestions for the future: Headless RPi support!

Dockerfile:

docker-compose.yml:

Related topics