07-26-2024, 10:49 AM
(This post was last modified: 07-26-2024, 10:51 AM by Tim Curtis.
Edit Reason: eta
)
Thats because of the issue below described in post #2 in the following thread:
https://moodeaudio.org/forum/showthread....6#pid56046
This means it has to be treated as a connection based player (hogs ALSA output) like Bluetooth, RoonBridge or Squeezelite (w/o the -C option) and not a session based player like Airplay or Spotify Connect.
A fix for this would need to be done by Plexamp devs so that when the player starts it should wait for a play request from the client before opening the ALSA output. Then moode could use the plexamp_status.py utility to detect when play has started or stopped to determine when to display the renderer active overlay.
https://moodeaudio.org/forum/showthread....6#pid56046
Code:
1. When Plexamp initially starts it opens and hogs the ALSA output until something is played and then stopped at which point it then releases the ALSA output after ~15 seconds. Hogging the output on initial start means that it can't be handled a true session based renderer like Airplay or Spotify Connect which initially start w/o opening ALSA output. They only open the output when play initiates.This means it has to be treated as a connection based player (hogs ALSA output) like Bluetooth, RoonBridge or Squeezelite (w/o the -C option) and not a session based player like Airplay or Spotify Connect.
A fix for this would need to be done by Plexamp devs so that when the player starts it should wait for a play request from the client before opening the ALSA output. Then moode could use the plexamp_status.py utility to detect when play has started or stopped to determine when to display the renderer active overlay.
