1 files changed, 6 insertions, 0 deletions

diff --git a/NewGstVideo.moin b/NewGstVideo.moin
index 5aa837f..b2e72fc 100644
--- a/NewGstVideo.moin
+++ b/NewGstVideo.moin
@@ -30,3 +30,9 @@ Some features like rowstride can be added somewhat transparently, because it is
 Open points:

  * some formats, like I420, could have two differing definitions of rowstride. (1) U and V planes have same stride in bytes as Y, or (2) U and V planes have 1/2 stride as Y.

  * in some cases, it might be nice to have some flexibility to allow support for non-packed planar/semi-planar formats.  In some cases where decoder requires padding or cropping for edges, or certain alignment requirements, the U and V planes may not start immediately after the previous frame.

+

+= Stereo video support in an existing branch =

+

+Stereo caps have been proposed in a Google Summer of Code development branch (see [[http://gitorious.org/video3d/video3d]]).  One of the important points in choosing how to extend existing caps to support a way to specify whether the video stream was stereo or not was the fact that we don't want existing plugins to accept silently a stereo stream and treat it as normal stream, as the interpretation of a {{{width x height}}} buffer is totally different if the buffer is stereo or not.  Therefore, the addition of a field such as {{{"stereo=true"}}} or {{{"channels=2"}}} to existing video caps was not used.

+

+Instead, the new caps use new mymetypes : {{{video/x-raw-{yuv,rgb,gray}-stereo}}}.  The addition of the {{{"-stereo"}}} to the mymetype makes sure that existing plugins won't accept these caps.  The new caps that are to replace {{{video/x-raw-{yuv,rgb,gray,etc}}}} could add something like {{{-full}}} during integration of these new caps in order to keep compatibility with existing plugins.