W3C home > Mailing lists > Public > whatwg@whatwg.org > April 2010

[whatwg] Dealing with Stereoscopic displays

From: WeBMartians <webmartians@verizon.net>
Date: Wed, 28 Apr 2010 12:25:35 -0400
Message-ID: <4BD8617F.4080606@verizon.net>
... not to complicate matters, but there is a similar uncertainty 
regarding immersion imaging (Google's StreetView). Currently, it's done 
with plugins (usually Flash, sometimes QuickTime and only occasionally 
other software).

I t-h-i-n-k ... maybe, just maybe ... the newer Javascript engines are 
fast enough, with <canvas>, to do this kind of rendering.

Can something similar be done for 3D? ...as to how to synchronize the 
glasses, I haven't a clue.

Maybe we need a fourth "color" (depth) for JPEG ... hmmm ... make that a 
"fifth color" ... in line behind alpha/transparency.
===
Eoin Kilfeather wrote:
> Hi Rob, all,
>
> Fair enough :-) I'll have to try better. Rob you give some good 
> examples (WebGL and CSS3) of how an application could be built which 
> correctly renders two views with stereopsis. However, with the 
> exception of Anaglyph methods, a user will need specialised display 
> hardware to properly view the image. So, to clarify, the issue is not 
> the rendering of the stereo views (I'll worry about that later) but 
> rather how those views are targeted to the correct virtual display 
> (for example by alternating the left and right views on odd and even 
> frames). If we take the case of the Blu-Ray 3D specification it is 
> neutral about how the hardware is implemented, but the hardware is 
> expected to respect the flags indicating whether a frame is for the 
> left or right virtual display. In order to work with HTML the UA has 
> to have some awareness of the hardware and way of signalling with view 
> is for which virtual display. My question is, how can this be done in 
> a consistent manner? Given that this usually requires some hardware 
> control, is a good approach to use the <device> element?
>
> I hope this is a little clearer.
>
> Best regards,
>
> Eoin.
>
>
> On Tue, Apr 27, 2010 at 10:01 AM, Robert O'Callahan 
> <robert at ocallahan.org <mailto:robert at ocallahan.org>> wrote:
>
>     On Tue, Apr 27, 2010 at 8:38 PM, Eoin Kilfeather
>     <ekilfeather at dmc.dit.ie <mailto:ekilfeather at dmc.dit.ie>> wrote:
>
>            * A user visits the National Museum site and wants to see a
>         time-machine view of objects in the collection with a sense of 3D
>         depth based on their age
>
>
>     I think this is the closest you get to an actual use-case :-). The
>     rest is mixed up with information about possible solutions. Also,
>     it's highly unlikely the a user will visit your site with a fully
>     formed desire to view objects in a collection with a sense of 3D
>     depth based on their age :-).
>
>     But let's say the authors of that site want to visualize objects
>     in the collection with different objects at different depths. It
>     seems to me either WebGL or CSS 3D transforms --- or a mixture ---
>     could be used for this, maybe with some extra information provided
>     to identity the camera positions for rendering the stereo views.
>
>     Actually, I probably shouldn't be involved in this discussion
>     since I'm monocular :-).
>
>
>     Rob
>     -- 
>     "He was pierced for our transgressions, he was crushed for our
>     iniquities; the punishment that brought us peace was upon him, and
>     by his wounds we are healed. We all, like sheep, have gone astray,
>     each of us has turned to his own way; and the LORD has laid on him
>     the iniquity of us all." [Isaiah 53:5-6]
>
>
>
>
> -- 
> Eoin Kilfeather
> Digital Media Centre
> Dublin Institute of Technology
Received on Wednesday, 28 April 2010 09:25:35 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:22 UTC