d6jg wrote: 
> I do think people would want to see an Echo appear as a pseudo player so
> that it could be controlled by any means available eg Alexa, Material,
> Default GUI, iPeng etc so I do think stream.flac is required to
> establish the audio sink.

I agree. That's they way it works today - the Echo shows up as a network
client in LMS and lag or no lag, it's great to browse the playlist for
the AlexaPlayer in LMS.

Philippe did have a shot at starving the stream so that the lag because
acceptable (see
https://forums.slimdevices.com/showthread.php?111016-Announce-MediaServer-*certified*-Alexa-skill-for-LMS&p=991361&viewfull=1#post991361)
and it certainly resulted in an instant GUI-experience but due to the
quick-and-dirty nature of the hack it resulted in lots of rebuffering.

If the stream.flac route is possible then it would be worth revisiting
the starvation topic. It could be a command line parameter to enable
drip-feed or not, so existing applications not requiring it would not be
adversely affected.


------------------------------------------------------------------------
philchillbill's Profile: http://forums.slimdevices.com/member.php?userid=68920
View this thread: http://forums.slimdevices.com/showthread.php?t=114558

_______________________________________________
ripping mailing list
ripping@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/ripping

Reply via email to