No, there is a full DCT decoder in ORBX.js, the encoder is built into the Amazon AMI, and can use CPU or GPU for encoding (the GPU encoder is pure OpenCL - so one day ORBX.js could support encoding in the browser through WebCL). If you send raw data down to the browser, you would need a 1 GB connection . We are targeting 4G/LTE speeds at 8-12 Mbps for HD @ 60 hz, with support going to 1-3 Mbps for 1024x768 @ 30- 60 hz..
If it weren't for Mozilla creating broadway.js, ORBX.js would never have happened. Andreas' work on this libary was they key inspiration for ORBX.js. Since May, Mozilla has helped us optomize the JS code (which was key post FF22 when the JS VM changed), and is helping us move the decoder entirely to the GPU in WebGL2. I think at some point we would like to open source the older ORBX.js codecs as we iterate on this first version, but even that doesn't make much sense until we get a stable file format for video. Right now ORBX.js is tuned for live streaming. That will change with v2, which is we're targeting for early next year with compression close to HEVC - see http://aws.otoy.com/docs/ORBX2_Whitepaper.pdf
It's rendered server side. The decoding is done entirely in JS, so no plug-ins. Not even <video> tag (try doing streaming with that, the latency is +100 ms). So, When you boot an AMI up on Amazon, the web page streams back the host FB as a 60 hz HD stream. Here in Los Angeles, my ping time to EC2 West Coast (NoCal) is 13-16 ms. Encode is 4-6 ms, decode in JS is 4-8 ms - I don't notice any latency. I am very curious to see the experiences others have. BTW I work at OTOY, and my username on the OTOY forums is "Goldorak". I can help anyone out there if they need assistance.
Thanks for the reply. What about the additional latency of sending the rendered framebuffer to the local graphics card after it's received from the cloud? It seems like you're right on the edge of being able to do one-frame latency between input and render at 30 fps (33 ms per frame), but would have at least two-frame latency at 60 fps?
Well if you run Aero in windows 7, that adds 3 frame of latency for example. In my testing, I don't think the decoode->canvas->present is much of an issue, but others might be more sensitive. Of course that last step is also browser specific. Firefox 19+ to me seems the smoothest, but Chrome 26+ an Opera 16+ give very good results too.
Yes the same technology is in Autodesk Remote, which has been out since July, and allows you to do exactly that. The JavaScript component is not out yet, it is just PC to PC or OC to iPad right now.
You have two choices - supply your own GUID in the metadata, and this overrides the randomly assigned one, or look in RDP/ssh for it (which is more work than needed - highly recommended you add your own GUID, this way it doesn't need to be copied or grabbed from RDP/ssg)
