From bdaadd435250ad549cdcebfd383d89bc9ebd9032 Mon Sep 17 00:00:00 2001 From: Wim Taymans Date: Thu, 24 Dec 2009 15:13:49 +0100 Subject: [PATCH] docs: add some more buffer2 ideas --- docs/design/draft-buffer2.txt | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/docs/design/draft-buffer2.txt b/docs/design/draft-buffer2.txt index 37215c5373..2abb4adb21 100644 --- a/docs/design/draft-buffer2.txt +++ b/docs/design/draft-buffer2.txt @@ -378,5 +378,28 @@ We would like to think of the GstCaps containing the information needed to functionally negotiate the format between two elements. The Metadata should then only contain variables that can change between each buffer. +For example, for video we would have width/height/framerate in the caps but then +have the more technical details, such as stride, data pointers, pan/crop/zoom +etc in the metadata. + +A scheme like this would still allow us to functionally specify the desired +video resolution while the implementation details would be inside the metadata. + + +Notes: +------ + +Some structures that we need to be able to add to buffers. + + Clean Aperture + Abitrary Matrix Transform + Aspect ratio + Pan/crop/zoom + Video strides + +Some of these overlap, we need to find a minimal set of metadata structures that +allows us to define all use cases. + +