I realise Jriver is a combo solution but it does feel that the world might shift here. if Kazoo server extends its server function to support Alexa. It does seem to me that existing servers might gain by extending to fill that gap and conversely be considered less useful by not doing so. However, it's not clear how the control can easily expand to offer that function to Alexa without in its own right adding server like function (if my understanding/assumptions are correct). There is no doubt that Alexa is handling/parsing the requests but there remains a gap between that and the control function. It does seem that this issues straddles the server and control functionality. All user interaction for playing music would be handled by the control-point portion. JRiver is both a control point and a server. (11-11-2016 14:27)simoncn Wrote: (11-11-2016 13:47)brantome Wrote: Thanks, I obviously phrased that badly - wouldn't the cloud skill be in effect the control point, accepting the voice to text output from Alexa, and in turn generating UPNP requests? The wider implication I was referring to was an account-based web service that could securely pass requests to your personal local instance of minimserver, much as how I expect, in my relative naivety, the HouseBand skill is doing for JRiver.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |