ralphy wrote:
> Same buttons on the slimdevices remote, and lirc codes however some of
> the lirc key symbols are different.
>
> 'Squeezelite lircd config'
> (https://raw.githubusercontent.com/ralph-irving/tcz-lirc/master/lircd.conf)
> 'Jivelite lircd config'
>
Thanks for you suggestions. My answers interspersed.
-
Does the same thing happen with radio streaming as locally stored songs
?-
Yes.
-Have you tried with a single Pi and a single touch as the only clients
?-
Yes.
-Are you sure your LMS server is capable of delivering the fourth stream
?-
Cut-Throat wrote:
>
>
-Try changing the "proxied" or "direct" setting for streams and see if
> that makes a difference to internet radio.
> I have the internet streaming option as "direct" because I have a 30mbit
> connection with unlimited data, so I'm unlikely to have issues with
> streams
Since Logitech is not going to add Spotify Connect to their Spotify
app/handler, would it be possible to add this feature as an pCP
extension, such as Shairport?
There's detailed explanation (in german) how this can be done on top of
the Volumio RPi image:
cooppw02 wrote:
> I'd just like to chime in and say thanks to those that made and
> contributed to this thread. The instructions worked pretty much
> flawlessly; the only thing I had to do differently was to change the
> perl 5.20.2 references to 5.20.3.
I tried it, changed the reference and
Meridion wrote:
> Since Logitech is not going to add Spotify Connect to their Spotify
> app/handler, would it be possible to add this feature as an pCP
> extension, such as Shairport?
>
> There's detailed explanation (in german) how this can be done on top of
> the Volumio RPi image:
>
I don't think it has to. In my plugins for remote streams, I use a
function CanDirectPlay which indicates (I think) to LMS if it can tell
players to grab the data directly from the source. It's Indépendant from
synchronization which is handled by LMS through the feedback the player
gives it in
Paul Webster wrote:
> My recollection (possibly faulty) is that when playing sync mode then it
> is always via LMS so that it can manage the sync process.
I think this is the case - as LMS has to create a stream equal to the
capabilities of the "worst" player in the sync group so this may