Hi Marc, I use the node.js socket.io <http://socket.io/> module for the transmission of the 3D data to the server - its a library that uses WebSockets.
Richard. > On 02 Aug 2019, at 19:13, Marc Lavallée <m...@hacklava.net> wrote: > > Hi Richard, > > My question was not directly related to the orientation API, but to the > method used to transmit its data to your server. You mentioned https; either > https AJAX or secure WebSockets (WSS) can be initiated by a https request. > Maybe a realtime connection using WebSockets is not required, slow AJAX > requests being fast enough. I was just curious. > > Marc > > > Le 19-08-02 à 12 h 31, Richard Foss a écrit : >> Hi Marc, >> >> The following will give you a better idea of the Web API capabilities that I >> am using: >> >> https://developer.mozilla.org/en-US/docs/Web/API/Detecting_device_orientation >> >> >> Richard. >> >> >> On 2019/08/02 4:38 PM, Marc Lavallée wrote: >>> Hi Richard. >>> >>> Without reading access to the (paywalled) article and (unpublished) code, >>> it's difficult to understand all the effects of this problem. So I >>> wondered: are the events send via AJAX or WebSockets? >>> >>> Marc >>> >>> Le 19-08-02 à 09 h 53, Richard Foss a écrit : >>>> Bo-Erik, we have always been able to open a connection to the web server >>>> and upload code. The problem is that access to the mobile device's device >>>> orientation events by our code on the client is disallowed when using >>>> chrome and an http server - fine with other web browsers. This is a recent >>>> phenomenon. When we make our web server secure (https), we can access the >>>> events. This requires the secure certification process. >>>> >>>> On 2019/08/02 1:17 PM, Bo-Erik Sandholm wrote: >>>>> As long as the hosting server is a local host websocket server chrome can >>>>> open a connection to the server. >>>>> At least the version available a month ago. >>>>> >>>>> Den fre 2 aug. 2019 10:28Richard Foss <r.f...@ru.ac.za> skrev: >>>>> >>>>>> Hi Justin, >>>>>> >>>>>> I have described the use of a mobile device controller in the following >>>>>> paper that is in the AES e-library: >>>>>> >>>>>> http://www.aes.org/e-lib/browse.cfm?elib=19714 >>>>>> >>>>>> Its a client server system, where the server is a node.js server and a >>>>>> browser is used to run client code. This means I can use the Web API >>>>>> device orientation capabilities. One frustrating issue is that Chrome >>>>>> has recently stopped allowing device orientation access unless the >>>>>> server is secure. >>>>>> >>>>>> Richard Foss. >>>>>> >>>>>> On 2019/07/26 9:01 PM, Justin Kuhn wrote: >>>>>>> Hi Everyone, >>>>>>> >>>>>>> I am looking into making a controller in which I harness roll, pitch, >>>>>>> and >>>>>>> yaw from my phone or a vr controller for real-time control of the >>>>>>> orientation of a soundfield. I want to hook it up using OSC to Reaper >>>>>>> or >>>>>>> Supercollider either wirelessly (preferred) or through USB (if I have >>>>>> to). >>>>>>> I have a few reasons I want to do this. >>>>>>> >>>>>>> - I want to do real-time encoding and decoding with a controller that >>>>>> can >>>>>>> add expressive qualities with my hands for 4.0 performance purposes >>>>>>> - I want to better calibrate binaural playback through traditional >>>>>>> headphones for production purposes >>>>>>> - I hope to avoid using a headset for ambisonic production entirely. >>>>>> It's >>>>>>> so much easier to turn my hand around very quickly than it is to use my >>>>>>> head. >>>>>>> - Would make a cool pairing with Wekinator. >>>>>>> >>>>>>> Has anyone done this, or seen it done? I'd love some tips and >>>>>> suggestions >>>>>>> before I get started. >>>>>>> >>>>>>> Thanks! >>>>>>> >>>>>>> >>>>>>> *Justin Kuhn* >>>>>>> 360/VR Video and Audio Production >>>>>>> justinkuhnmedia.com >>>>>>> Cell | 828-403-3171 >>>>>>> He, Him, His >>>>>>> -------------- next part -------------- >>>>>>> An HTML attachment was scrubbed... >>>>>>> URL: < >>>>>> https://mail.music.vt.edu/mailman/private/sursound/attachments/20190726/4239fe96/attachment.html >>>>>> >>>>>>> _______________________________________________ >>>>>>> Sursound mailing list >>>>>>> Sursound@music.vt.edu >>>>>>> https://mail.music.vt.edu/mailman/listinfo/sursound - unsubscribe here, >>>>>> edit account or options, view archives and so on. >>>>>> >>>>>> -- >>>>>> Professor Richard Foss >>>>>> Computer Science Department >>>>>> Rhodes University >>>>>> Grahamstown 6140 >>>>>> South Africa >>>>>> >>>>>> Tel: +27 46 6038294 >>>>>> Cell: +27 83 288 9354 >>>>>> email: r.f...@ru.ac.za >>>>>> >>>>>> _______________________________________________ >>>>>> Sursound mailing list >>>>>> Sursound@music.vt.edu >>>>>> https://mail.music.vt.edu/mailman/listinfo/sursound - unsubscribe here, >>>>>> edit account or options, view archives and so on. >>>>>> >>>>> -------------- next part -------------- >>>>> An HTML attachment was scrubbed... >>>>> URL: >>>>> <https://mail.music.vt.edu/mailman/private/sursound/attachments/20190802/fffac0fd/attachment.html> >>>>> _______________________________________________ >>>>> Sursound mailing list >>>>> Sursound@music.vt.edu >>>>> https://mail.music.vt.edu/mailman/listinfo/sursound - unsubscribe here, >>>>> edit account or options, view archives and so on. >>>> >>> _______________________________________________ >>> Sursound mailing list >>> Sursound@music.vt.edu >>> https://mail.music.vt.edu/mailman/listinfo/sursound - unsubscribe here, >>> edit account or options, view archives and so on. >> > _______________________________________________ > Sursound mailing list > Sursound@music.vt.edu > https://mail.music.vt.edu/mailman/listinfo/sursound - unsubscribe here, edit > account or options, view archives and so on. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://mail.music.vt.edu/mailman/private/sursound/attachments/20190803/22522403/attachment.html> _______________________________________________ Sursound mailing list Sursound@music.vt.edu https://mail.music.vt.edu/mailman/listinfo/sursound - unsubscribe here, edit account or options, view archives and so on.