philippe_44 wrote: > Understood but if you think the better (and doable) solution is to have > a native slimproto in javascript in the chrome device itself, then doing > my bridge thing lloks like a waste of time, no ?
First - develop solutions for yourself - otherwise you'll never have enough time. You shouldn't be put off by somebody else doing similar as they are probably working to a different set of priorities and preferences. There is nothing wrong with alternatives (e.g. SoftSqueeze, Squeezeslave, Squeezelite) - seeing differences can only stilumate improvements. I don't know if a Receiver application implementing slimproto is entirely possible as there are a number of technical challenges. It need more investigation and that takes time. For example there is a problem about sockets and security - I think socket comms will need to be tunnelled unless a promised update to ChromecastAPI delivered some special features. A stepping stone would be to implement a Squeezelite player in javascript to run on a web page using html5 audio - if this works then it can work on a Chromecast. If people are really really eagar - for Linux with Pulseaudio it is possible to get squeezelite to play out on Chromecast and DLNA devices using pulsealudio-dlna application https://github.com/masmu/pulseaudio-dlna but as you know these solutions make compromises. I see the fundamental issues as making sure it is easy to start/stop casting using a Touch as a controller, minimising latency and allowing the Chromecast device to easily change between services. ------------------------------------------------------------------------ bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=104549 _______________________________________________ Radio mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/radio
