-
Notifications
You must be signed in to change notification settings - Fork 452
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Plexamp support for audio playback #1165
Comments
This would be awesome! Just set up a mopidy server with snapcast and plexamp as well. Mopidy streams fine, but has issues loading my large plex library - so streaming plexamp directly through snapserver (without going through mopidy) would be fantastic. |
Yea i wanted to set up mopidy with iris to have a nice webui but i couldn't find a way to connect plex to mopidy so i ended up using a vm with the desktop plexamp client and snapserver |
+1 for this issue EDIT: @chicco-carone on an unrelated note, how did you integrate the two? Looking to switch over to Plexamp soon and can't figure out a FIFO pipe from anatosun/plexamp-docker |
For me since I don't have a Plex pass I have a VM in proxmox without audio so there is only a loopback and it captures the audio from the standard client via Alsa. For Plexamp I think that you can pass into the container /dev/snd which should give it access to Alsa and then also in the docker container for snapserver or the native package capture the default Alsa playback device |
@kerta1n I just found a method that should work for a FIFO from Plexamp. In both pipewire and pulseaudio there is a way to transform a normal output into a Fifo that snapcast can read so you can add a script that creates the Fifo when you launch the container and then use a volume to pass it to the host and then mount the same volume for the snapserver container. |
Something to note though, UNRAID has no alsa support. I'll have to go try to compile something |
Use music assistant and connect it to Plex |
Currently doing this. Unfortunately, while Plexamp is very quick (using regular plex app and chosing plexamp player), Music Assistant takes ages to find library updates and searching it is nowhere near as quick as in plex itself. I needed two Plex connections in Music Assistant because music and audiobooks are two different libraries. Music is 10655 tracks, audio books 39836 tracks. So workflow if plexamp was possible: open plex on phone, chose plexamp player, find track, play. Music assistant: open home assistant app, go to music assistant tab, find track, chose desired output to play, play. While this is a valid solution and works fine, it would still be nice if there was a way to "natively" do it through snap. @chicco-carone do you have a script like this that you would share with us? I'm sure it's possible to rtfm and create an individual one, but if there was a solution already, it'd be better for spaghetti coders such as myself. |
You could Add the MA to your homescreen. That safes some time or you use MA for Music and not Plex. |
This is my current workflow. |
In case sombody is interested, this is my setup now: |
What guide did you use to setup your Alsa loopback |
If you have a system without any sound card (like a VM) there is a default loopback one that gets created and you can then capture it with alsa by using the default option in snapcast. If you need to create it there is the snd-aloop kernel module that you can activate or create with pipewire a fifo that snapcast can capture and then point your music source to playback into it |
I used the trial and error howto ;) In /etc/modprobe.d/alsa-base.conf I added: and in /etc/modules-load.d/snd_aloop.conf This gives me 5 loopback devices on the start, unfortunately I haven't found a way to give them proper names for Plexamp. In snapserver.conf I configured them like: |
I've stopped using Spotify as my music player to use plex with the plexamp app and it would be great to be able to play back from that one. I know that plexamp has a headless version too so probably I can capture the audio from that and redirect it into Snapcast but a native implementation would be great
The text was updated successfully, but these errors were encountered: