[ibash]

What do you mean by rendered with pure JS? It's rendered server side, isn't it?

[asdfs]

Apparently the video decoding and other client-side stuff is done purely in JavaScript (and in particular using WebGL), no <video> tag or plugins or anything like that. I presume that all the server-side stuff is still native code.

I'd still like to see a demo page with their JavaScript decoder.

[tonyplee]

Are you sure it is not just as simple as opening up a websocket and pipe the frame data as texture data directly into the webgl instant?

[sandyman]

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..

[asdfs]

How would video compression work in that case?

[1qaz2wsx3edc]

> The two parts of the announcement, JS+WebGL decoder and the GPU cloud driving the encoder, combine to make a whole greater than the sum of the parts.

So, it's some client JS WebGL code, and something else driving the encoder in the cloud

I like the idea of scriptable VNC like streams.

[prawn]

Is the JS handling the streaming or whatever that aspect of it might be called?

[smaili]

They have a JavaScript library called ORBX.js that handles all the streaming and encoding in the browser.

You can read more about it here -> http://www.otoy.com/130501_OTOY_release_FINAL.pdf