Paul Webster wrote: > The situation I was thinking of is if someone using the LMS web UI or > controller other than Echo to pause (and maybe resume if quick) the > stream to an Echo would want to select the player in the UI via a > friendly name in LMS. > > e.g. household has more than one Echo ... and both are playing different > stuff from LMS ... then someone elsewhere in the house can pause the > stream to an Echo using LMS UI. > > All of the Echo's are playing /stream.mp3 but LMS automatically feeds > them different queues because it has unique players per IP.
Having a list of virtual Echo players in the GUI would give the illusion that playback can be started from the GUI which is not the case. A stream can only be started by voice. Once started it can be modified in the GUI for sure. But skills are not allowed to send audio to an Echo without a voice command preceding. After changing the audio from the GUI you either have to say Alexa, resume to pick up the modified stream or wait for the buffer to empty. That would no longer be necessary with a starved stream. But the initial Stream whatever command would always have to be voice and not GUI. Thats the danger in having persistent virtual players that are always there and is why I only create a GUI entry after a stream was started by voice. ------------------------------------------------------------------------ philchillbill's Profile: http://forums.slimdevices.com/member.php?userid=68920 View this thread: http://forums.slimdevices.com/showthread.php?t=111016
_______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
