GA_VideoBufferFormatsType
Declaration
typedef enum {
gaVideoRGB332 =
0x00000001,
gaVideoRGB555 =
0x00000002,
gaVideoRGB565 =
0x00000004,
gaVideoRGB888 =
0x00000008,
gaVideoRGB8888 =
0x00000010,
gaVideoYUV9 =
0x00000020,
gaVideoYUV12 =
0x00000040,
gaVideoYUV411 =
0x00000080,
gaVideoYUV422 =
0x00000100,
gaVideoYUV444 =
0x00000200,
gaVideoYCrCb422 =
0x00000400,
gaVideoYUYV =
0x08000000,
gaVideoYVYU =
0x10000000,
gaVideoUYVY =
0x20000000,
gaVideoVYUY =
0x40000000
} GA_VideoBufferFormatsType
Prototype In
snap/graphics.h
Description
Flags for hardware video input formats defined in the VideoInputFormats member of the GA_videoInf structure. These flags define the hardware video capabilities of the particular video overlay window, and are only valid if the gaHaveAccelVideo flag is defined in the Attributes member of the GA_modeInfo structure.
The gaVideoRGB332 flag is used to determine whether the video overlay window can support hardware video playback of frames stored in the RGB 3:3:2 format (8 bits per pixel).
The gaVideoRGB555 flag is used to determine whether the video overlay window can support hardware video playback of frames stored in the RGB 5:5:5 format (16 bits per pixel, 1 ignored).
The gaVideoRGB565 flag is used to determine whether the video overlay window can support hardware video playback of frames stored in the RGB 5:6:5 format (16 bits per pixel).
The gaVideoRGB888 flag is used to determine whether the video overlay window can support hardware video playback of frames stored in the RGB 8:8:8 format (24 bits per pixel). Only one RGB format is supported, and the Blue byte is always stored first in memory (ie: B:G:R).
The gaVideoRGB8888 flag is used to determine whether the video overlay window can support hardware video playback of frames stored in the RGB 8:8:8:8 format (32 bits per pixel). Only one RGB format is supported, and the Blue byte is always stored first in memory (ie: B:G:R:A).
The gaVideoYUV9 flag is used to determine whether the video overlay window can support hardware video playback of frames stored in the YUV9 format. For more information on different YUV formats and how they are actually stored in the framebuffer, see the section titled 'Overview of YUV pixels'.
The gaVideoYUV12 flag is used to determine whether the video overlay window can support hardware video playback of frames stored in the YUV12 format. For more information on different YUV formats and how they are actually stored in the framebuffer, see the section titled 'Overview of YUV pixels'.
The gaVideoYUV411 flag is used to determine whether the video overlay window can support hardware video playback of frames stored in the YUV 4:1:1 format. The YUV 4:1:1 data can be stored with the YUV values in varying formats, and you should check the gaVideoYUYV etc flags to determine which formats are supported by this controller. For more information on different YUV formats and how they are actually stored in the framebuffer, see the section titled 'Overview of YUV pixels'.
The gaVideoYUV422 flag is used to determine whether the video overlay window can support hardware video playback of frames stored in the YUV 4:2:2 format. The YUV 4:2:2 data can be stored with the YUV values in varying formats, and you should check the gaVideoYUYV etc flags to determine which formats are supported by this controller. For more information on different YUV formats and how they are actually stored in the framebuffer, see the section titled 'Overview of YUV pixels'.
The gaVideoYUV444 flag is used to determine whether the video overlay window can support hardware video playback of frames stored in the YUV 4:4:4 format. The YUV 4:4:4 data can be stored with the YUV values in varying formats, and you should check the gaVideoYUYV etc flags to determine which formats are supported by this controller. For more information on different YUV formats and how they are actually stored in the framebuffer, see the section titled 'Overview of YUV pixels'.
The gaVideoYCrCb422 flag is used to determine whether the video overlay window can support hardware video playback of frames stored in the YCrCb 4:2:2 format. The YCrCb 4:2:2 data can be stored with the YUV values in varying formats, and you should check the gaVideoYUYV etc flags to determine which formats are supported by this controller. For more information on different YUV formats and how they are actually stored in the framebuffer, see the section titled 'Overview of YUV pixels'.
The gaVideoYUYV, gaVideoYVYU, gaVideoUYVY and gaVideoVYUY flags are used to determine what YUV pixel layouts is supported for the above suppored YUV pixel formats.
Note: These flags are also passed to the AllocVideoBuffer function to determine the video input data type being displayed for the video window.
Note: The gaVideoYUYV and related flags define the YUV pixel layouts that are supported by the hardware for the YUV input format it supports. For instance the hardware may report gaVideoYUV422 and the gaVideoYUYV flags, which means it supports the YUV422 format with the format 4:2:4:2 (Y:U:Y:V) in video memory. See the section titled 'Overview of YUV Pixels' for more information.
Members
gaVideoRGB332 |
Supports RGB 3:3:2 input format |
gaVideoRGB555 |
Supports RGB 5:5:5 input format |
gaVideoRGB565 |
Supports RGB 5:6:5 input format |
gaVideoRGB888 |
Supports RGB 8:8:8 input format |
gaVideoRGB8888 |
Supports RGB 8:8:8:8 input format |
gaVideoYUV9 |
Supports YUV9 input format |
gaVideoYUV12 |
Supports YUV12 input format |
gaVideoYUV411 |
Supports YUV411 input format |
gaVideoYUV422 |
Supports YUV422 input format |
gaVideoYUV444 |
Supports YUV444 input format |
gaVideoYCrCb422 |
Supports YCrCb422 input format |
gaVideoYUYV |
Supports the YUYV pixel layout (for the above YUV formats) |
gaVideoYVYU |
Supports the YVYU pixel layout (for the above YUV formats) |
gaVideoUYVY |
Supports the UYVY pixel layout (for the above YUV formats) |
gaVideoVYUY |
Supports the VYUY pixel layout (for the above YUV formats) |
Copyright © 2002 SciTech Software, Inc. Visit our web site at http://www.scitechsoft.com