Facilitating interaction between video renderers and graphics device drivers

Π

Facilitating Interaction between Video Renderers and Graphics Device Drivers

RELATED PATENT APPLICATIONS

This U.S. Non-provisional Application for Letters Patent claims the benefit of priority from, and hereby incorporates by reference herein the entire disclosure of, eo-pending U.S. Provisional Application for Letters Patent Serial No. 60/413,060, filed September 24, 2002, and titled “Methods for Hardware Accelerating the Troc Amp’ Adjustments of Video Images on a Computer Display”.

This U.S. Non-provisional Application for Letters Patent also claims the benefit of priority from, and hereby incorporates by reference herein the entire disclosure of, co-pending U.S. Provisional Application for Letters Patent Serial No. 60/376,880, filed April 15, 2002, and titled “Methods and Apparatuses for Facilitating De-Interlacing of Video Images”.

This U.S. Non-provisional Application for Letters Patent is related by subject-matter to U.S. Non-provisional Application for Letters Patent Serial No. 10/273,505, filed on October 18, 2002, and titled “Methods And Apparatuses For Facilitating Processing Of Interlaced Video Images For Progressive Video Displays”. This U.S. Non-provisionaS Application for Letters Patent Serial No. 10/273,505 is also hereby incorporated by reference herein in its entirety.

Atty Docket No. MSI-IWUS PAT APP

CA 02425360 2003-04-14

I

TECHNICAL FIELD

This disclosure relates in general to processing image/graphics data for display and in particular, by way of example but not limitation, to facilitating interaction between video Tenderers and graphics device drivers using a protocol for communicating information therebetween, as well as consequential functionality. Such information may include queries, responses, instructions, etc. that are directed to, for example, ProcAmp adjustment operations.

BACKGROUND

In a typical computing environment, a graphics card or similar is responsible for transferring images onto a display device and for handling at least part of the processing of the images. For video images, a graphics overlay device and technique is often employed by the graphics card and the overall computing device. For example, to display video images from a DVD or Internet streaming source, a graphics overlay procedure is initiated to place and maintain the video images.

A graphics overlay procedure selects a rectangle and a key color for establishing the screen location at which the video image is to be displayed. The rectangle can be defined with a starting coordinate for a comer of the rectangle along with the desired height and width. The key color is usually a rarely seen color such as bright pink and is used to ensure that video is overlain within the defined rectangle only if the video is logically positioned at a topmost layer of a desktop on the display screen.

In operation, as the graphics card is providing pixel colors to a display device, it checks to determine if a given pixel location is within the selected

Ally Docket No. MSl-l3d7LS.PAT.APP

CA 02425360 2003-04-14

H η

graphics overlay rectangle. If not, the default image data is forwarded to the display device. If, on the other hand, the given pixel location is within the selected graphics overlay rectangle, the graphics card checks to determine whether the default image data at that pixel is equal to the selected key color. If not, the default image data is forwarded to the display device for the given pixel. If, on the other hand, the color of the given pixel is the selected key color, the graphics card forwards the video image data to the display device for that given pixel.

There are, unfortunately, several drawbacks to this graphics overlay technique. First, there is usually only sufficient hardware resources for a single graphics overlay procedure to be in effect at any one time. Regardless, reliance on the graphics overlay technique always results in constraints on the number of possible simultaneous video displays as limited by the hardware. Second, the pink or other key color sometimes becomes visible (i.e., is displayed on an associated display device) when the window containing the displayed video is moved vigorously around the desktop on the display screen.

Third, a print screen command does not function effectively inasmuch as the video image that is displayed on the display device is not captured by the print screen command. Instead, the key color is captured by the print screen command, so the printed (or copied and pasted) image includes a solid rectangle of the key color where the video is displayed on the display device.

Another technique for displaying video images entails using the host microprocessor to perform video adjustments prior to transferring the video image to the graphics processor for forwarding to the display device. There are also several drawbacks to this host processor technique. First, the host microprocessor and associated memory subsystem of a typical computing environment is not

Any Docket No. MSN! 347US. P AT APP

CA 02425360 2003-04-14

It

Ιό optimized for the processing of large video images. Consequently, the size and number of video images that can be displayed are severely restricted. Second, for the host microprocessor to work efficiently, the video image must reside in memory that is directly addressable by the host microprocessor. As a result, other types of hardware acceleration, such as decompression and/or de-interlacing, cannot be performed on the video image.

In short, previous techniques such as the graphics overlay procedure and reliance on the host processor result in visual artifacts, are too slow and/or use memory resources inefficiently, are hardware limited, constrain video presentation flexibility, and/or do not enable a fully-functional print screen command. Accordingly, there is a need for schemes and/or approaches for remedying these and other deficiencies by, inter alia, facilitating interaction between video Tenderers and graphics device drivers.

SUMMARY

Facilitating interaction between video Tenderers and graphics device drivers may be enabled through communication protocols and/or application programming interfaces (APIs) that permit information regarding image processing capabilities of associated graphics hardware to be exchanged between a graphics device driver and a video render Image processing capabilities include video processing capabilities; video processing capabilities include by way of example, but not limitation, process amplifier (ProcAmp) control adjustments, deinterlacing, aspect ratio corrections, color space conversions, frame rate conversions, vertical or horizontal mirroring, and alpha blending.

Alty Docket No. M.SM347US PAT.APP

CA 02425360 2003-04-14

In an exemplary method implementation, a method facilitates interaction between one or more video Tenderers and at least one graphics device driver, the method including actions of: querying, by a video render of the one or more video Tenderers, the at least one graphics device driver regarding video processing capabilities; and informing, by the at least one graphics device driver, the video render of at least a subset of video processing capabilities that the at least one graphics device driver can offer to the video Tenderer.

In a first exemplary media implementation, electronically-executable instructions thereof for a video Tenderer precipitate actions including: issuing a query from a video render towards a graphics device driver, the query requesting information relating to ProcAmp capabilities; and receiving a response at the video tenderer from the graphics device driver, the response including the requested information relating to ProcAmp capabilities.

In a second exemplary media implementation, electronically-executable instructions thereof for a graphics device driver precipitate actions including: receiving a query at a graphics device driver from a video Tenderer, the query requesting information relating to ProcAmp capabilities; and sending a response to the video Tenderer from the graphics device driver, the response including the requested information that relates to ProcAmp capabilities.

In an exemplary system implementation, a system facilitates interaction between a video Tenderer and a graphics device driver, the system including: video rendering logic that is adapted to prepare queries that request information relating to ProcAmp capabilities that can be applied to video that is to be displayed; and graphics device driving logic that is adapted to prepare responses

Atty Docket No. MS1-1J47US .PAT APP

CA 02425360 2003-04-14 that indicate what ProcAmp capabilities can be applied to video that is to be displayed.

Other method, system, apparatus, protocol, media, arrangement, etc.

implementations are described herein.

BRIEF DESCRIPTION OF THE DRAWINGS

The same numbers are used throughout the drawings to reference like and/or corresponding aspects, features, and components.

FIG. 1 is a first video processing pipeline that includes a ProcAmp adjustment operation.

FIG. 2 is a second video processing pipeline that includes two video processing operations to arrive at an RGB render target.

FIG 3 is a third video processing pipeline that includes one video processing operation to arrive at an RGB render target.

FIG. 4 is a block diagram that illustrates certain functional elements of a computing or other electronic device that is configured to facilitate interaction between video Tenderers and graphics device drivers.

FIG. 5 is a communications/signaling diagram that illustrates an exemplary protocol between a video Tenderer and a graphics device driver.

FIG 6 is a flow diagram that illustrates an exemplary method for facilitating interaction between a video tenderer and a graphics device driver.

FIG. 7 illustrates an exemplary computing (or general electronic device) operating environment that is capable of (wholly or partially) implementing at least one aspect of facilitating interaction between video Tenderers and graphics device drivers as described herein.

Atty Docket No. MS 1 -1347US.PAT. APP

CA 02425360 2003-04-14 ό

Ί

S

DETAILED DESCRIPTION

Exemplary Video Processing Pipelines and ProcAmp Adjustments

Exemplary Video Processing Pipeline with a ProcAmp Adjustment

FIG. 1 is a first video processing pipeline 100 that includes a ProcAmp adjustment operation 104. First video processing pipeline 100 may be implemented using graphics hardware such as a graphics card. It includes (i) three image memory blocks 102, 106, and 108 and (ii) at least one image processing operation 104. Image memory block 102 includes a YUV video image offscreen plain surface. Image processing operation 104, which comprises a ProcAmp adjustment operation 104 as illustrated, is applied to image memory block 102 to produce image memory block 106. Image memory block 106 includes a YUV offscreen plain surface or a YUV texture, depending on the parameters and capabilities of the graphics hardware that is performing the image adjustment operations.

After one or more additional image processing operations (not explicitly shown in FIG. 1), the graphics hardware produces image memory block 108, which includes an RGB render target. The RGB render target of image memory block 108 may be displayed on a display device by the graphics hardware without additional image processing operations. Also, image memory block 108 includes image data for each pixel of a screen of a display device such that no image data need be retrieved from other memory during the forwarding of the image data from image memory block 108 to the display device.

ProcAmp adjustment operation 104 refers to one or more process amplifier (ProcAmp) adjustments. The concept of ProcAmp adjustments originated when

Atty Docket No. MS1-1347US.PAT APP '>/// j/.· ;*.<?* ·Ί>,:-.··'/'··CA 02425360 2003-04-14 video was stored, manipulated, and displayed using analog techniques. However, ProcAmp adjustment operations 104 may now be performed using digital techniques. Such ProcAmp adjustment operations 104 may include one or more operations that are directed to one or more of at least the following video properties: brightness, contrast, saturation, and hue.

Exemplary ProcAmp-Related Video Properties

The following descriptions of brightness, contrast, saturation, and hue, in conjunction with possible and/or suggested settings for manipulating their values, are for an exemplary described implementation. Other ProcAmp adjustment guidelines may alternatively be employed.

Brightness: Brightness is alternatively known as Black Set”; brightness should not be confused with gain (contrast). It is used to set the viewing black’ level in each particular viewing scenario. Functionally, it adds or subtracts the same number of quantizing steps (bits) from all the luminance words in a picture. It can and ‘ generally does create clipping situations if the offset plus some luminance word is less than 0 or greater than full range. It is usually interactive with the contrast control.

Contrast: Contrast is the ‘Gain’ of the picture luminance. It is used to alter the relative light to dark values in a picture. Functionally, it is a linear positive or negative gain that maps the incoming range of values into a smaller or a larger range. The set point (e.g,, no change as gain changes) is normally equal to a code 0, but it is more appropriately the code word that is associated with a nominal viewing black set point. The contrast gain structure is usually a linear transfer ramp that passes through this set point. Contrast functions usually involve rounding of the computed values if the gain is set is anything other than 1-to-l,

Any Docket No. MS I -1347US PAT. APP

CA 02425360 2003-04-14 δ

ίϋ ΐΐ

IS and that rounding usually includes programmatic dithering to avoid visible artifact generation 'contouring’.

Saturation; Saturation is the logical equivalent of contrast. It is a gain function, with a set point around “zero chroma” (e.g., code 128 on YUV or code 0 on RGB in a described implementation).

Hue; Hue is a phase relationship of the chrominance components. Hue is typically specified in degrees, with a valid range from —180 through +180 and a default of 0 degrees. Hue in component systems (e.g., YUV or RGB) is a three part variable in which the three components change together in order to maintain valid chrominance/luminance relationships.

Exemplary Proc Amp-Related Adjusting in the YUV Color Space

The following descriptions for processing brightness, contrast, saturation, and hue in the YUV color space, in conjunction with possible and/or suggested settings for manipulating their values, are for an exemplary described implementation. Other adjustment guidelines may alternatively be employed. Generally, working in the YUV color space simplifies the calculations that are involved for ProcAmp adjustment control of a video stream.

Y Processing: Sixteen (16)' is subtracted from the Y values to position the black level at zero. This removes the DC offset so that adjusting the contrast does not vary the black level. Because Y values may be less than 16, negative Y values should be supported at this point in the processing. Contrast is adjusted by multiplying the YUV pixel values by a constant. (If U and V are adjusted, a color shift will result whenever the contrast is changed.) The brightness property value is added (or subtracted) from the contrast-adjusted Y values; this prevents a DC offset from being introduced due to contrast adjustment. Finally, the value 16 is

Atty Docket No. MSl-îJ47US.PATAPP

CA 02425360 2003-04-14 i added back to reposition the black level at 16. An exemplary equation for the i processing of Y values is thus:

Y’ = ((Y-16)xC) + B +16, where C is the Contrast value and B is the Brightness value.

UV Processing; One hundred twenty-eight (128) is first subtracted from both U and V values to position the range around zero. The hue property alone is implemented by mixing the U and V values together as follows:

IT = (U-128) x Cos(H) + (V-128) x Sin(H), and V’ = (V-128) x Cos(H) - (U-128) x Sin(H), where H represents the desired Hue angle.

Saturation is adjusted by multiplying both U and V by a constant along with the saturation value. Finally, the value 128 is added back to both U and V. The combined processing of Hue and Saturation on the UV data is thus:

U’ = (((U-128) x Cos(H) (V-128) x Sin(H)) x C x S) + 128, and V’ = (((V-128) x Cos(H) - (U-128) x Sin(H)) xCxS)+ 128, where C is the Contrast value as in the Y’ equation above, H is the

Hue angle, and S is the Saturation.

Exemplary Video Processing Pipeline with Two Processing Operations

FIG 2 is a second video processing pipeline 200 that includes two video processing operations 202 and 206 to arrive at RGB render target 108. Second video processing pipeline 200 includes (i) three image memory blocks 102, 204, and 108 and (ii) two image processing operations 202 and 206.

For second video processing pipeline 200 generally, image memory block 204 includes an RGB texture. Image memory block 204 results from image memory block 102 after application of image processing operation 202. Image

Atty Docket No. MSUJ47US-PAT.ÀPP

CA 02425360 2003-04-14 memory block 108 is produced from image memory block 204 after image processing operation 206.

Other image processing operations, in addition to a ProcAmp control adjustment, may be performed. For example, any one or more of the following exemplary video processing operations may be applied to video image data prior to its display on a screen of a display device:

1. ProcAmp control adjustments;

2. De-interlacing;

3. Aspect ratio correction;

4. Color space conversion; and

5. Vertical or horizontal mirroring and alpha blending.

When possible, the desired video (and/or other image) processing operations are combined into as few operations as possible so as to reduce the overall memory bandwidth that is consumed while processing the video images. The degree to which the processing operations can be combined is generally determined by the capabilities of the graphics hardware. Typically, color space conversion processing and aspect ratio correction processing are applied to many, if not most, video streams. However, vertical/horizontal mirroring and alpha blending are applied less frequently.

For second video processing pipeline 200, ProcAmp adjustment processing and color space conversion processing are combined into image processing operation 202. Aspect ratio correction processing is performed with image processing operation 206. Optionally, vertical/horizontal mirroring and/or alpha blending may be combined into image processing operation 206. As illustrated, the graphics hardware that is implementing second video processing pipeline 200

Atty Docket No MSÎ-1 Î47US.PAT APP

CA 02425360 2003-04-14

W

Π uses two image processing operations and three image memory blocks to produce image memory block 108 as the RGB render target. However, some graphics hardware may be more efficient.

Exemplary Video Processing Pipeline with One Processing Operation

FIG. 3 is a third video processing pipeline 300 that includes one video processing operation 302 to arrive at an RGB render target 108. Generally, third video processing pipeline 300 is implemented with graphics hardware using one image processing operation 302 and two image memory blocks 102 and 108. Specifically, image memory block 108 is produced from image memory block 102 via image processing operation 302. Image processing operation 302, as illustrated, includes multiple video processing operations as described below.

Third video processing pipeline 300 is shorter than second video processing pipeline 200 (of FIG. 2) because image processing operation 302 combines ProcAmp adjustment processing, color space conversion processing, and aspect ratio correction processing. The number of stages in a given video processing pipeline is therefore dependent on the number and types of image processing operations that are requested by software (e.g., an application, an operating system component, etc.) displaying the video image as well as the capabilities of the associated graphics hardware. Exemplary software, graphics hardware, and so forth are described further below with reference to FIG. 4.

Exemplary Video-Related Software and Graphics Hardware

FIG. 4 is a block diagram 400 that illustrates certain functional elements of a computing or other electronic device that is configured to facilitate interaction between a video Tenderer 410 and a graphics device driver 422. These various exemplary elements and/or functions are implementable in hardware, software,

Atty Docket No. MS I-I347US.PAT APP

CA 02425360 2003-04-14

S

IS firmware, some combination thereof, and so forth. Such hardware, software, firmware, some combination thereof, and so forth are jointly and separately referred to herein generically as logic.

The configuration of block diagram 400 is only an example of a video data processing apparatus or system. It should be understood that one or more of the illustrated and described elements and/or functions may be combined, rearranged, augmented, omitted, etc. without vitiating an ability to facilitate interaction between video Tenderers and graphics device drivers.

Apparatus or system 400 includes transform logic 408, which, for example, may include instructions performed by a central processing unit (CPU), a graphics processing unit, and/or a combination thereof. Transform logic 408 is configured to receive coded video data from at least one source 406. The coded video data from a source 406 is coded in some manner (e.g., MPEG-2, etc.), and transform logic 408 is configured to decode the coded video data.

By way of example, source 406 may include a magnetic disk and related disk drive, an optical disc and related disc drive, a magnetic tape and related tape drive, solid-state memory, a transmitted signal, a transmission medium, or other like source configured to deliver or otherwise provide the coded video data to transform logic 408. Additional examples of source 406 are described below with reference to FIG. 7. In certain implementations, source 406 may include multiple source components such as a network source and remote source. As illustrated, source 406 includes Internet 404 and a remote disk-based storage 402.

The decoded video data that is output by transform logic 408 is provided to at least one video Tenderer 410. By way of example but not limitation, video Tenderer 410 may be realized using the Video Mixer and Renderer (VMR) of a

Atty Docket No. MS M347US.PAT APP

CA 02425360 2003-04-14 ?

S

Microsoft® Windows® Operating System (OS). In a described implementation, video Tenderer 410 is configured to aid transform logic 408 in decoding the video stream, to cause video processing operations to be performed, to blend any other auxiliary image data such as closed captions (CCs) or DVD sub-picture images with the video image, and so forth. And, at the appropriate time, video Tenderer 410 submits or causes submission of the video image data to graphics interface logic 412 for eventual display on a display device 436.

The resulting rendered video data is thus provided to graphic interface logic 412. By way of example but not limitation, graphic interface logic 412 may include, for example, DirectDraw®, Direct3D®, and/or other like logic. Graphic interface logic 412 is configured to provide an interface between video Tenderer 410 and a graphics device 424. As illustrated, graphics device 424 includes a graphics processor unit (GPU) 426, a video memory 432, and a digitai-to-analog converter (DAC) 434. By way of example but not limitation, graphics device 424 may be realized as a video graphics card that is configured within a computing or other electronic device.

The image data output by graphic interface logic 412 is provided to a graphics device driver 422 using a device driver interface (DDI) 414. In FIG. 3, device driver interface 414 is depicted as having at least one application programming interface (API) 416 associated therewith. Device driver interface 414 is configured to support and/or establish the interface between video Tenderer 410 and graphics device driver 422.

As illustrated at apparatus/system 400 and for a described implementation, device driver interface 414 and graphics device driver 422 may further be categorized as being part of either a user mode 418 or a kernel mode 420 with

Any Docket No. MSM34?U$ PAT.APP

CA 02425360 2003-04-14

U •Μ respect to the associated operating system environment and graphics device 424. Hence, video Tenderer 410 and device driver interface 414 are part of user mode 418, and graphics device driver 422 is part of kernel mode 420. Those communications occurring at least between device driver interface 414 and graphics device driver 422 cross between user mode 418 and kernel mode 420.

In this described implementation, the video image data that is output by video Tenderer 410 is thus provided to graphics processor unit 426. Graphics processor unit 426 is configurable io perform one or more image processing operations. These image processing operations include ProcAmp adjustments and/or other video processing operations as indicated by ProcAmp adjustment logic 428 and/or other video processing operations logic 430, respectively. ProcAmp adjustment operations and other exemplary video processing operations, such as de-interlacing and frame rate conversion, are described further below as well as above.

The output from graphics processor unit 426 is provided to video memory 432. When video memory 432 is read from, the resulting image data can be forwarded to a digital-to-analog converter 434, which outputs a corresponding analog video signal that is suitable for display on and by display device 436. In other configurations, display device 436 may be capable of displaying the digital image data from video memory 432 without analog conversion by a digital-toanalog converter 434.

Exemplary Protocol between a Video Renderer and a Graphics Device

Driver

FIG. 5 is a communications/signaling diagram 500 that illustrates an exemplary protocol between a video renderer 410 and a graphics device driver

Atty Docket No MSM347US PAT.APP

CA 02425360 2003-04-14 η

422. The exemplary protocol facilitates the performance of video (or other image) processing operations such as a ProcAmp adjustment. Such video processing operations may include those that are requested/specified by a user activated and controlled video display application (e.g., an instigating application).

Communications/signaling diagram 500 includes multiple communication exchanges and communication transmissions between video Tenderer 410 and graphics device driver 422. Optionally, the communications may be enabled and/or aided by graphic interface 412 (of FIG. 4) and/or device driver interface 414, along with any applicable APIs 416 thereof.

A communications exchange 502 is directed to establishing video processing (VP) capabilities. Specifically, video Tenderer 410 requests or queries at transmission 502A graphics device driver 422 regarding video processing capabilities that are possessed by and that are to be provided by graphics device driver 422. In response 502B, graphics device driver 422 informs video Tenderer 410 of the allotted video processing capabilities.

The allotted video processing capabilities include those video processing operations that graphics device driver 422 is capable of performing. These may include one or more of ProcAmp control adjustment operations, de-interlacing operations, aspect ratio correction operations, color space conversion operations, vertical/horizontal mirroring and alpha blending, frame rate conversion operations, and so forth. Graphics device driver 422 may choose to provide all or a portion of the remaining video processing operational bandwidth. By allotting less than all of the remaining video processing operations bandwidth, graphics device driver 422 is able to hold in reserve additional video processing operations bandwidth for subsequent requests.

A’.ty Dockcï No. MSI-U47LS.PAT.APP

CA 02425360 2003-04-14

S η

A communications exchange 504 is directed to establishing control property capabilities for a specified video processing operation. In a request 504A that is sent from video Tenderer 410 to graphics device driver 422, video Tenderer 410 specifies a particular video processing operation allotted in response 502B. Request 5 04A may also include an inquiry as to what or which property capabilities graphics device driver 422 is able to perform with respect to the particular video processing operation. In a response 504B, graphics device driver 422 informs video Tenderer 410 as to the property capabilities that are available for the specified particular video processing operation. Communications exchange 504 may be omitted if, for example, there are not multiple control property capabilities for the particular video processing operation.

A communications exchange 506 is directed to establishing which of the other allotted video processing operations may be performed simultaneously with the particular video processing operation as specified. In a request 506A, video Tenderer 410 issues a query to graphics device driver 422 to determine which video processing operations, if any, may be performed simultaneously with the particular video processing operation. Graphics device driver 422 informs video Tenderer 410 in response 506B of the video processing operations that is possible for graphics device driver 422 to perform simultaneously with the particular video processing operation. By way of example, it should be noted that (i) transmissions 504A and 506A and/or (ii) transmissions 504B and 506B may be combined into single query and response transmissions, respectively.

A communications exchange 508 is directed to establishing values for a specified control property of the particular video processing operation. In a request 508A, video Tenderer 410 specifies in an inquiry a control property for the

Any Docket No. MS 3- ! 347US.PAr.APP

CA 02425360 2003-04-14

Î0 particular video processing operation. The specified control property may be selected from the available control properties provided in response 504B. Graphics device driver 422 provides values that are related to the specified control property for the particular video processing operation to video Tenderer 410. These values may be numerical set points, ranges, etc. that video Tenderer 410 can utilize as a framework when instructing graphics device driver 422 to perform the particular video processing operation. Communications exchange 508 may be repeated for each available control property that is indicated in response 504B. Alternatively, one such communication exchange 508 may be directed to multiple (including all of the) control properties of the available control properties.

A communications exchange 510 is directed to initiating a video processing stream object. In an instruction 510A, video Tenderer 410 sends a command to graphics device driver 422 to open a video processing stream object. This command may be transmitted on behalf of an application or other software component that is trying to present video images on display device 436. in a response 510B, graphics device driver 422 returns a handle for the video processing stream object to the requesting video Tenderer 410.

In a transmission 512A, video Tenderer 410 instructs graphics device driver 422 to perform the particular or another allotted video processing operation. The perform video processing operation command may include selected numerals to set and/or change values for one or more control properties for the particular video processing operation. In response, graphics device driver 422 performs a video processing operation 512B as requested in transmission 512A. Typically, at least one video Tenderer 410 is assigned to each application that is to be displaying video. Whenever such an instigating application requests a video processing

Any Docker No. MS1-Î347US.PAT APP

CA 02425360 2003-04-14 operation, for example, video renderer 410 forwards such request as a video processing operation instruction, optionally after re-formatting, translation, and so forth, to graphics device driver 422.

Perform video processing operation commands 512A and resulting video processing operations 512B may be repeated as desired while the video processing stream object is extant. When the video is completed or the relevant software is terminated, a close video processing stream object instruction 514 is transmitted from video renderer 410 to graphics device driver 422.

The approaches of FIGS. 4, 5, and 6, for example, are illustrated in diagrams that are divided into multiple blocks and/or multiple transmissions. However, the order and/or layout in which the approaches are described and/or shown is not intended to be construed as a limitation, and any number of the blocks/transmissions can be combined and/or re-arranged in any order to implement one or more systems, methods, media, protocols, arrangements, etc. for facilitating interaction between video Tenderers and graphics device drivers. Furthermore, although the description herein includes references to specific implementations such as that of FIG. 4 (as well as the exemplary system environment of FIG. 7) and to exemplary APIs, the approaches can be implemented in any suitable hardware, software, firmware, or combination thereof and using any suitable programming language(s), coding mechanism(s), protocol paradigm(s), graphics setup(s), and so forth.

Exemplary General API Implementation

FIG. 6 is a flow diagram 600 that illustrates an exemplary method for facilitating interaction between a video renderer 410 and a graphics device driver 422. Although a described implementation as reflected by FIG. 6 is directed to a

Atty Docket Na. MSM347US.FAT APP

CA 02425360 2003-04-14 η

ProcAmp adjustment operation, it is not so limited, instead, at least certain aspects of this exemplary general API implementation may be used with one or more other video (or general image) processing operations.

In flow diagram 600, video Tenderer 410 is associated with nine (9) blocks 602-618, and graphics device driver 422 is associated with six (6) blocks 620-630. Each of blocks 602-618 and 620-630 corresponds to at least one action that is performed by or on behalf of video Tenderer 410 and graphics device driver 422, respectively.

Flow diagram 600 is described below in the context of exemplary general APIs. These general APIs as described herein can be divided into two functional groups of methods, apparatus logic, etc. The first group can be used to determine the video processing capabilities of a graphics device. The second group can be used to create and use video processing operation stream objects.

These exemplary general APIs may correspond to APIs 416 (of FIG. 4) that are illustrated as being part of device driver interface 414, which supports graphic interface 412 and interfaces with graphics device driver 422. APIs 416 are thus illustrated as being part of device driver interface 414 that is in user mode portion 418. However, such APIs 416 may alternatively be located at and/or functioning with other logic besides device driver interface 414. Such other logic includes, by way of example only, video Tenderer 410, graphic interface 412, some part of kernel mode portion 420, and so forth,

The general APIs described below in this section may be used to extend/enhance/etc. Microsoft® DirectX® Video Acceleration (VA), for example, so as to support any of a number of video processing operations (e.g., ProcAmp adjustments, frame rate conversions, etc.) for video content being displayed in

Atty Docket No MSI-l347GS.PAr.APP

CA 02425360 2003-04-14 ί

Ί

Π conjunction with a graphics device driver. Additional related information can be found in a Microsoft® Windows® Platform Design Note entitled “DirectX® VA:

Video Acceleration API/DDI”, dated January 23, 2001. “DirectX® VA: Video

Acceleration API/DDI” is hereby incorporated by reference in its entirety herein.

Although the actions of flow diagram 600 are described herein in terms of APIs that are particularly applicable to the current evolution of Microsoft® Windows® operating systems for persona] computers, it should be understood that the blocks thereof, as well as the other implementations described herein, are also applicable to other operating systems and/or other electronic devices.

In the following examples, the output of the video processing operation(s) is provided in an RGB render target format such as a target DirectDraw® surface. Doing so precludes the need for conventional hardware overlay techniques. Additionally, an entire screen as viewable on a display device, including any video images, exists and, furthermore, is present in one memory location so that it can be captured by a print screen command. This print screen capture can then be pasted into a document, added to a file, printed directly, and so forth.

In flow diagram 600, video tenderer 410 may have already been informed by graphics device driver 422 that associated graphics hardware is capable of performing ProcAmp adjustment video processing operations or video Tenderer 410 may determine the existence of ProcAmp capabilities, or the lack thereof, as follows. At block 602, video Tenderer 410 provides a description of the video to be displayed and requests graphics processing capabilities with respect to ProcAmp control properties.

Video Tenderer 410 makes the video description provision and/or the control properties request to graphics device driver 422 via one or more

Any Docket No. MShl347US.PAT.APP

CA 02425360 2003-04-14

L

Π

B

24' transmissions as indicated by the transmission arrow between block 602 and block

620. The description of the video enables graphics device driver 422 to tailor the available/possible/etc. video processing capabilities based on the type of video.

For example, a predetermined set of capabilities may be set up for each of several different types of video.

At block 620, graphics device driver 422 provides video Tenderer 410 a listing of the available ProcAmp control properties. This list may include none or one or more of brightness, contrast, hue, and saturation. At block 604, video Tenderer 410 receives the available ProcAmp control properties from graphics device driver 422. Actions of blocks 620 and 622 may be performed responsive to the communication(s) of block 602. Alternatively, video Tenderer 410 may make a separate inquiry to elicit the actions of block 622.

At block 622, graphics device driver 422 provides video Tenderer 410 with those video processing operations that may possibly be performed simultaneously/concurrently with ProcAmp adjustment operations. Such video processing operations may include none or one or more of YUV2RGB, StretchX, StretchY, SubRects, and AlphaBlend. Other such video processing operations may include de-interlacing, frame rate conversion, and so forth. At block 606, video Tenderer 410 receives the possible simultaneous video processing operations from graphics device driver 422.

An exemplary general API for implementing at least part of the actions of blocks 602, 604, 606, 620, and 622 is provided as follows:

ProcAmpControlQueryCaps

This API enables video Tenderer 410 to query graphics device driver

422 to determine the information related to the input requirements of a

Atly Docket No. MSI-I347VS.PAT APP

CA 02425360 2003-04-14

ProcAmp control device and any additional video processing operations that might be supported at the same time as ProcAmp adjustment operations are being performed.

HRESULT

ProcAmpControlQueryCaps(

[in] DXVAVideoDesc* IpVideoDescription,

[out] DXVA__ProcAmpControlCaps* IpProcAmpCaps );

Graphics device driver 422 reports its capabilities for that mode in an output DXVA_ProcAmpControlCaps structure for IpProcAmpCaps.

typedef struct _DXVA_ProcAmpControlCaps {

DWORD Size;

DWORD InputPool;

D3DFORMAT OutputFrameFormat;

DWORD ProcAmpControlProps;

DWORD VideoProcessingCaps;

} DXVA_ProcAmpControlCaps;

The Size field indicates the size of the data structure and may be used, inter alia, as a version indicator if different versions have different data structure sizes.

The InputPool field indicates a memory pool from which the video source surfaces are to be allocated. For example, the memory pool may be

Aity Ducket No MSM347US MT APP

CA 02425360 2003-04-14 located at local video memory on the graphics card, at specially-tagged system memory (e.g., accelerated graphics port (AGP) memory), general system memory, and so forth. The D3D and DirectDraw documentations also provide a description of valid memory pool locations.

The OutputFrameFormat field indicates a Direct3D surface format of the output frames. The ProcAmp device can output frames in a surface format that matches the input surface format. This field ensures that video Tenderer 410 will be able to supply the correct format for the output frame surfaces to the ProcAmp control hardware. Note that if the DXVA_VideoProcess_YUV2RGB flag (see below) is returned in the VideoProcessingCaps field, video Tenderer 410 can assume that valid output formats are specified by this field as well as an RGB format such as RGB32. RGB32 is an RGB format with 8 bits of precision for each of the Red, Green, and Blue channels and 8 bits of unused data.

The ProcAmpControlProp field identifies the ProcAmp operations that the hardware is able to perform. Graphics device driver 422 returns the logical of the combination of the ProcAmp operations that it supports:

• DXVA__ProcAmp_None. The hardware does not support any ProcAmp control operations.

• DXVAJProcAmpBrightness. The ProcAmp control hardware can perform brightness adjustments to the video image.

• DXVA__ProcAmp_Contrast. The ProcAmp control hardware can perform contrast adjustments to the video image.

• DXVA_ProcAmp_Hue. The ProcAmp control hardware can perform hue adjustments to the video image.

Atty Docket No MSl-iJ47US.PAT.APP

CA 02425360 2003-04-14 δ

Π • DXVA_ProcAmp_Saturation. The Proc Amp control hardware can perform saturation adjustments to the video image.

The VideoProcessingCaps field identifies other operations that can be performed concurrently with a requested Proc Amp adjustment. The following flags identify the possible operations:

• DXVA_VideoProcess_YUV2RGB. The ProcAmp control hardware can convert the video from the YUV color space to the RGB color space. The RGB format used can have 8 bits or more of precision for each color component, if this is possible, a buffer copy within video Tenderer 410 can be avoided. Note that there is no requirement with respect to this flag to convert from the RGB color space to the YUV color space, • DXVA_VideoProcess_StretchX. If the ProcAmp control hardware is able to stretch or shrink horizontally, aspect ratio correction can be performed at the same time as the video is being ProcAmp adjusted.

• DXVA_VideoProcess_StretchY. Sometimes aspect ratio adjustment is combined with a general picture re-sizing operation to scale the video image within an application-defined composition space. This is a somewhat rare feature. Performing the scaling for resizing the video to fit into the application window can be done at the same time as the scaling for the ProcAmp adjustment. Performing these scalings together avoids cumulative artifacts.

DXVAJVideoProcess SubRects. This flag indicates that hardware is able to operate on a rectangular (sub-)region of the

Atty Docket No MSI-1347US.PAT.APP

CA 02425360 2003-04-14 image as well as the entire image. The rectangular region can be identified by a source rectangle in a BXVAJProcAmpControlBlt data structure.

* DXVA_VideoProcess_AlphaBlend. Alpha blending can control how other graphics information is displayed, such as by setting levels of transparency and/or opacity. Thus, an alpha value can indicate the transparency of a color - or the extent to which the color is blended with any background color. Such alpha values can range from a fully transparent color to a fully opaque color.

in operation, alpha blending can be accomplished using a pixel-by-pixel blending of source and background color data. Each of the three color components (red, green, and blue) of a given source color may be blended with the corresponding component of the background color to execute an alpha blending operation. In an exemplary implementation, color may be generally represented by a 32-bit value with 8 bits each for alpha, red, green, and blue.

Again, using this feature can avoid a buffer copy with video renderer 410. However, this is also a rarely used feature because applications seldom alter the constant alpha value associated with their video stream.

At block 608 of flow diagram 600, video renderer 410 selects a ProcAmp control property from those received at block 604. At block 610, video renderer 410 requests one or more values for the selected ProcAmp control property from graphics device driver 422. At block 624, graphics device driver 422 sends to video renderer 410 values for the requested ProcAmp control property. Such

Atty Docker No. MSM347US.PATAP?

CA 02425360 2003-04-14 values may relate to one or more of a default value, an increment value, a minimum value, a maximum value, and so forth.

At block 612, video Tenderer 410 receives from graphics device driver 422, and is thus informed of, one or more values for the selected ProcAmp control property. As indicated by the flow arrow from block 612 to block 608, the actions of blocks 608, 610, 612, and 624 may be repeated for more than one including all of the available ProcAmp control properties. Alternatively, video Tenderer 410 may query graphics device driver 422 for more than one including ail of the available ProcAmp control properties in a single communication exchange having two or more transmissions.

An exemplary general API for implementing at least part of the actions of blocks 608, 610, 612, and 624 is provided as follows;

ProcAmpControlQueryRange

For each ProcAmp property (brightness, contrast, saturation, hue, etc.), video Tenderer 410 queries graphics device driver 422 to determine the minimum, maximum, step size (increment), default value, and so forth. If the hardware does not support a particular ProcAmp control property, graphics device driver 422 may return ^<4E_NOTIMPL” in response to the ProcAmpControlQueryRange function.

Although graphics device driver 422 can return any values it wishes for the different ProcAmp control properties, the following settings values are provided by way of example (all tabulated values are floats):

Any Docket No. MSt-I347US.PAT.AP?

CA 02425360 2003-04-14

<td> Property</td><td> Minimum</td><td> Maximum</td><td> Default</td><td> Increment</td>

<td> Brightness</td><td> -100.0F</td><td> 100.0F</td><td> 0.0F</td><td> 0.1F</td>

<td> Contrast</td><td> 0.0F</td><td> 10.0F</td><td> 1.0F</td><td> 0.01F</td>

<td> Saturation</td><td> 0.0F</td><td> 10.0F</td><td> 1.0F</td><td> 0.01F</td>

<td> Hue</td><td> -180.0F</td><td> 180.0F</td><td> 0.0F</td><td> 0.1F</td>

Ί

Ιό

Π

If the default values result in a null transform of the video stream, video renderer 410 is allowed to bypass the ProcAmp adjustment stage in its video pipeline if the instigating application does not alter any of the ProcAmp control properties.

HRESULT

ProcAmpControlQueryRange(

[in] DWORD VideoProperty,

[in] DXVA_VideoDesc* lpVideoDescription, [out] DXVA_VideoPropertyRange* IpPropRange );

VideoProperty identifies the ProcAmp control property (or properties) that graphics device driver 422 has been requested to return information for. In a described implementation, possible parameter values for this Field are:

• DXVA_ProcAmp_Brightness;

• DXVA_ProcAmp_Contrast;

• DXVA ProcAmp Hue ; and • DXVAJProcAmpJSaturation.

Atty Docket No. MSI-1347US PAT APP

CA 02425360 2003-04-14

Π lpVideoDescription provides graphics device driver 422 with a description of the video that the Proc Amp adjustment is going to be applied to. Graphics device driver 422 may adjust its ProcAmp feature support for particular video stream description types.

IpPropRange identifies the range (min and max), step size, and default value for the ProcAmp control property that is specified by the VideoProperty parameter/field.

typedef struct DXVA VideoPropertyRange {

FLOAT MinValue;

FLOAT MaxValue;

FLOAT DefaultValue;

FLOAT StepS ize ;

} DXVAJVideoPropertyRange, *LPDXVAJVideoPropertyRange;

At block 614 of flow diagram 600, video Tenderer 410 sends an open ProcAmp stream object command to graphics device driver 422. In response, graphics device driver 422 opens a ProcAmp stream object at block 626. At block 616, video Tenderer 410 instructs graphics device driver 422 to perform a ProcAmp adjustment operation. In response, graphics device driver 422 performs the requested ProcAmp adjustment operation at block 628.

As indicated by the curved flow arrow at block 616, video Tenderer 410 may continue to send perform ProcAmp adjustment operation instructions to graphics device driver 422 as long as desired (e.g., whenever required by an instigating application displaying the video stream). At block 618, video Tenderer

Atty Docket No. MS1-IJ47US.PAT.APP

CA 02425360 2003-04-14

410 instructs graphics device driver 422 to close the ProcAmp stream object.

Graphics device driver 422 then closes the ProcAmp stream object at block 630.

An exemplary general API for implementing at least part of the actions of blocks 614, 616, 618, 626, 628, and 630 is provided as follows:

The ProcAmpStream Object

After video renderer 410 has determined the capabilities of the ProcAmp control hardware, a ProcAmpStream object can be created. Creation of a ProcAmpStream object allows graphics device driver 422 to reserve any hardware resources that are required to perform requested ProcAmp adjustment operation(s).

ProcAmpOpènStream

The ProcAmpOpenStream method creates a ProcAmpStream object.

HRESULT

ProcAmpOpenStream(

[in] LPDXVA_VideoDesc lpVideoDescription,

[out] HDXVA_Proc Amp Stream* IphCcStrm );

The HDXVA_ProcAmpStream output parameter is a handle to the ProcAmpStream object and is used to identify this stream in future calls that are directed thereto.

ProcAmpBlt

Atty Docket No. MSI-J347US PAT APP

CA 02425360 2003-04-14

It

The ProcAmpBlt method performs the ProcAmp adjustment operation by writing the output to the destination surface during a bit block transfer operation.

HRESULT

ProcAmpBlt(

[in] HDXVA_Proc Amp Stream hCcStrm [in] LPDDSURFACE IpDDSDstSurface,

[in] LPDDSURFACE IpDDSSrcSurface,

[in] DXVA_ProcAmpBlt* ccBlt );

The source and destination rectangles are used for either subrectangle ProcAmp adjustment or stretching. Support for stretching is optional (and is reported by Caps flags). Likewise, support for subrectangles is not mandatory.

The destination surface can be an off-screen plain, a D3D render target, a D3D texture, a D3D texture that is also a render target, and so forth. The destination surface may be allocated in local video memory, for example. The pixel format of the destination surface is the one indicated in the DXVAJProcAmpCaps structure unless a YUV-to-RGB color space conversion is being performed along with the ProcAmp adjustment operation. In these cases, the destination surface format is an RGB format with 8 bits or more of precision for each color component.

ProcAmpCloseStream

Any Docket No MSI-I347US.PAT APP

CA 02425360 2003-04-14

The ProcAmpCloseStream method closes the ProcAmpStream object and instructs graphics device driver 422 to release any hardware resource associated with the identified stream.

HRESULT

ProcAmpCloseStream(

HDXVA_ProcAmpStream hCcStrm );

Î6

Exemplary Specific API Implementation

The particular situation and exemplary APIs described below in this section are specifically applicable to a subset of existing Microsoft® Windows® operating systems for personal computers. However, it should nevertheless be understood that the principles, as well as certain aspects of the pseudo code, that are presented below may be utilized (as is or with routine modifications) in conjunction with other operating systems and/or other environments.

DPI Mapping for a ProcAmp Interface

For compatibility with the DPI infrastructure for a subset of existing Microsoft® Windows® operating systems, the API described above in the previous section can be “mapped” to the existing DPI for DirectDraw and DirectX VA. This section describes a ProcAmp interface mapping to the existing DirectDraw and DX-VA DDL

The DX-VA DDI is itself split into two functional groups: the “DX-VA container” and the “DX-VA device.” The purpose of the DX-VA container DDI group is to determine the number and capabilities of the various DX-VA devices

Any Docket No MSM347US PAT.APP

CA 02425360 2003-04-14 ό

S

IS contained by the display hardware. Therefore, a DX-VA driver can only have a single container, but it can support multiple DX-VA devices.

It is not feasible to map the ProcAmpQueryCaps call on to any of the DDI entry points in the DX-VA container group because, unlike the rest of DX-VA, the container methods use typed parameters. However, the DX-VA device DDI group does not use typed parameters, so it is feasible to map the ProcAmp control interface to the methods in the device group. This section describes a specific example of how the ProcAmp interface can be mapped to the DX-VA device DDI.

De-interlace Container Device

The DX-VA device methods do not use typed parameters, so these methods can be reused for many different purposes. However, the DX-VA device methods can only be used in the context of a DX-VA device, so a first task is to define and create a special “container device.”

U.S. Non-provisional Application for Letters Patent Serial No. 10/273,505, which is titled “Methods And Apparatuses For Facilitating Processing Of Interlaced Video Images For Progressive Video Displays” and which is incorporated by reference herein above, includes description of a de-interlace container device. That Application’s described de-interlace container device is reused here for the ProcAmpQueryCaps function.

The DX-VA de-interiace container device is a software construct only, so it does not represent any functional hardware contained on a physical device. The ProcAmp control sample (device) driver pseudo code presented below indicates how the container device can be implemented by a driver.

Calling the DDI from a User-Mode Component

Atty Docket No. MSI-1347VS.PAT.APP

CA 02425360 2003-04-14

An exemplary sequence of eight (8) tasks to use the DDI from a user-mode component such as a (video) Tenderer is as follows:

1. Call GetMoCompGuids to get the list of DX-VA devices supported by the driver

2. If the “de-interlace container device” GUID is present, call

CreateMoComp to create an instance of this DX-VA device. The container device

GUID is defined as follows:

DEFINE_GUID(DXVA_DeinterlaceContainerDevice,

0x0e85cb93,0x3046,0x4ffû,0xae,0xcc,0xd5,0x8c,0xb5,0xf0, Ox35,Oxfc);

3. Call RenderMocomp with a dwFunction parameter that identifies a ProcAmpControlQueryModeCaps operation. Again, the IpInputData parameter is used to pass the input parameters to the driver, which returns its output through the IpOutputData parameter.

4. For each ProcAmp adjustment property supported by the hardware the Tenderer calls RenderMocomp with a dwFunction parameter that identifies a ProcAmpControlQueryRange operation. The IpInputData parameter is used to pass the input parameters to the driver, which returns its output through the IpOutputData parameter.

5. After the Tenderer has determined the ProcAmp adjustment capabilities of the hardware, it calls CreateMocomp to create an instance of the ProcAmp control device. The ProcAmp control device GUID is defined as follows:

Atiy Docket No. MSM347US.PATAPP

CA 02425360 2003-04-14

DEFINE_GUID(DXVA_ProcAmpControlDevice₅

0x9f200913,0x2ffd,0x4056,0x9f,0xle,0xel₅0xb5,0x08,0xf2,0x2d_j()xcf);

6. The renderer then calls the ProcAmp control device’s RenderMocomp with a function parameter of DXVAProcAmpControlBltFnCode for each ProcAmp adjusting operation,

7. When the renderer no longer needs to perform any more ProcAmp operations, it calls DestroyMocomp.

8. The driver releases any resources used by the ProcAmp control device.

ProcAmpControlQueryCaps

This method maps directly to a call to the RenderMoComp method of the de-interlace container device. The DD_RENDERMOCOMPDATA structure is completed as follows:

• dwNumBuffers is zero.

• IpBufferlnfo is NULL.

• dwFunction is defined as

DXVA_ProcAmpControlQueryCapsFnCode.

• lpInputData points to a DXVAVideoDesc structure.

• IpOutputData points to a DXVA_ProcAmpCaps structure.

Note that the DX-VA container device’s RenderMoComp method can be called without BeginMoCompFrame or EndMoCompFrame being called first.

ProcAmpControlQuery Range

Atty Docket No. MSI-I347US PAT.APP

CA 02425360 2003-04-14

Ο

z.

g

Ιό

IS

This method maps directly to a call to the RenderMoComp method of the de-interlace container device. The DD RENDERMOCOMPDATA structure is completed as follows:

• dwNumBuffers is zero.

• lpBufferlnfo is NULL.

• dwFunction is defined as

DXVAProcAmpControlQueryRangeFnCode.

• IpInputData points to a

DXVA_ProcAmpControlQueryRange structure.

typedef struct DXVA ProcAmpQueryRange {

DWORD Size;

DWORD VideoProperty;

DXVAVideoDesc VideoDesc;

} DXVA_ProcAmpControlQueryRange, *LPDXVA_ProcAmpControlQueryRange;

• IpOutputData will point to a DXVAVideoPropertyRange structure.

Note that the DX-VA container device’s RenderMoComp method can be called without BeginMoCompFrame or EndMoCompFrame being called first.

ProcAmpControlOpenStream

This method maps directly to a CreateMoComp method of the DDMOTIONCOMPCALLBACKS structure, where the GUID is the

A«y Docket No. MS1-I347US PAT APP

CA 02425360 2003-04-14 ό

il

IS

ProcAmp Device GUID, pUncompDaîa points to a structure that contains no data (all zeros), and pData points to a DXVAVideoDesc structure.

If a driver supports accelerated decoding of compressed video, the Tenderer can call the driver to create two DX-VA devices — one to perform the actual video decoding work as defined by the DirectX VA Video Decoding specification and another to be used strictly for ProcAmp adjustments.

**Example: Mapping CreateMoComp to ProcAmpCcntrolOpenStream**

The exemplary pseudo code below shows how a driver can map the CreateMoComp DDI call into calls to ProcAmpControlOpenStream. The pseudo code shows how the CreateMocComp fonction is used for ProcAmp. If a driver supports other DX-VA functions such as decoding MPEG-2 video streams, the sample code below can be extended to include processing of additional DX-VA GUIDs.

DWORD APIENTRY

CreateMoComp(

LPDDHAL__CREATEMOCOMPDATA IpData ) {

// Make sure its a guid we like, if (!ValidDXVAGuid(lpData-&gt;lpGuid)) {

DbgLog((LOG_ERROR, 1,

TEXT(No formats supported for this GUID)));

lpData-&gt;ddRVal = EJNVALIDARG;

A:ty Dockei No. MSI-13471JS PAT.APP

CA 02425360 2003-04-14 return DDHALJDRIVER_ HANDLED;

it Look for the deinterlace container device GUID if (*lpData-&gt;lpGuid == DXVA_DeinterlaceContainerDevice) {

DXVA DeinterlaceContainerDeviceClass* lpDev = new DXVA_DeinterlaceContainerDeviceClass( *lpData-&gt;lpGuid,

DXVADeviceContainer);

if(îpDev) { lpData-&gt;ddRVal = DDJDK;

} else { lpData-&gt;ddRVal - EJ3UTOFMEMORY;

} lpData-&gt;lpMoComp-&gt;IpDriverReserved 1 = (LPVOID)(DXVA_DeviceBaseClass*)lpDev;

return DDHAL_DRIVER_HANDLED;

} // Look for the ProcAmp Control device GUID if (*lpData-&gt;lpGuid == DXVAJProcAmpControlDevice) {

DXVAProcAmpControlDeviceClass* lpDev = new DXVA_ProcAmpControlDeviceClass( *lpData-&gt;lpGuid,

Any Docket No MS1-1347US PAT APP

CA 02425360 2003-04-14

2!

DXVA_DeviceProcAmpControl);

if (IpDev) {

LPDXVAJVideoDesc lpVideoDescription = (LPDXVA_VideoDesc)lpData-&gt;lpData;

lpData-&gt;ddRVal = lpDev-&gt;ProcAmpControlOpenStream( lpVideoDescription);

if (lpData-&gt;ddRVal !=DD_OK) { delete IpDev;

IpDev = NULL;

} }

else { lpData-&gt;ddRVal = EJDUTOFMEMORY;

} lpData-&gt;lpMoComp-&gt;lpDriverReservedl = (LPVOID)(DXVA_DevieeBaseClass*)lpDev; return DDHALDRIVERHANDLED;

} lpData-&gt;ddRVal = DDERRCURRENTLYNOTAVAIL; return DDHAL_DRIVER_HANDLED;

**Example: Implementing GetMoCompGuids**

Atty Docket No MS M347US PAT.APP

CA 02425360 2003-04-14

In addition to the CreateMoComp DDI function, a driver can also be capable of implementing the GetMoCompGuids method of the

DD_MOTIONCOMPCALLBACKS structure. The following exemplary pseudo code shows one manner of implementing this function in a driver.

H This is a list of DV-VA device GUIDs supported by // the driver - this list includes decoder, ProcAmp and

H the de-interlacing container device. There is no significance to // the order of the GUIDs on the list.

DWORD g dwDXVANumSupportedGUIDs = 2; const GUID* gJDXVASupportedGUIDs[2] - { &amp;DXVA_DeinterlaceContainerDevice, &amp;DXVA__ProcAmpControlDevice };

DWORD APIENTRY

GetMoCompGuids(

PDDGETMOCOMPGUIDSDATA lpData ) {

DWORD dwNumToCopy;

// Check to see if this is a GUID request or a count request if (lpData-&gt;lpGuids) { dwNumToCopy = min(g dwDXVANumSupportedGUlDs, lpData-&gt;dwNumGuids);

for (DWORD i 0; i &lt; dwNumToCopy; i++) {

Alty Docket No. MSI-1347US.PAT APP

CA 02425360 2003-04-14

S

W

Π η

π

Ιό lpData-&gt;lpGuids[i] = *g_DXVASupportedGUIDs[i] ;

} }

else { dwNumToCopy = g dwDXVANumSupportedGUIDs;

} lpData-&gt;dwNumGuids - dwNumToCopy;

lpData-&gt;ddRVal - DDJ3K;

return DDHAL_DRIVER_HANDLED;

}

ProcAmpControlBlt

This method maps directly to a RenderMoComp method of the DDMOTIONCOMPCALLBACKS structure, where:

« dwNumBuffers is two.

• lpBufferlnfo points to an array of two surfaces. The first element of the array is the destination surface; the second element of the array is the source surface.

• dwFunction is defined as

DXVAProcAmpControlBItFnCode.

• lpInputData points to the following structure:

typedef struct _DXVA_ProcAmpControlBlt {

DWORD Size;

RECT DstRect;

Ally Docket No MS 1-1 J47VS.PAT. APP

CA 02425360 2003-04-14 i

<td> RECT</td><td> SrcRect;</td>

<td> FLOAT</td><td> Alpha;</td>

<td> FLOAT</td><td> Brightness;</td>

<td> FLOAT</td><td> Contrast;</td>

<td> FLOAT</td><td> Hue;</td>

<td> FLOAT</td><td> Saturation;</td>

} DXVA_ProcAmpControlBlt;

• IpOutputData is NULL.

Note that for the DX-VA device used for ProcAmp, RenderMoComp can be called without calling BeginMoCompFrame or EndMoCompFrame. **Example: Mapping RenderMoComp to ProcAmpControlBlt**

The exemplary pseudo code below shows how a driver can map the RenderMoComp DDI call into calls to ProcAmpBlt. The sample code shows how the RenderMoComp function is used for ProcAmp adjustment. If the driver supports other DX-VA functions such as decoding MPEG-2 video streams, the sample code below can be extended to include processing of additional DX-VA GUIDs.

DWORD APIENTRY

RenderMoComp(

LPDDHALRENDERMOCOMPDATA IpData ) {

if (lpData-&gt;dwFunction — DXVAJProcAmpControlBltFnCode) {

DXVA_ProcAmpControlDeviceClass* pDXVADev =

Atty Docket No MS1-Î347US.PAT APP

CA 02425360 2003-04-14

U (DXVA_ProcAmpControlDeviceClass*)pDXVABase;

DXVAJProcAmpControlBlt* IpBlt = (DXVAJProcAmpControlBlt*)lpData-&gt;lpInputData;

LPDDMCBUFFERINFO lpBufflnfc - lpData-&gt;lpBufferInfo;

lpData-&gt;ddRVal = pDXVADev-&gt;ProcAmpControlBlt( lpBuffinfo[0],lpCompSurface, lpBufflnfo[l].lpCompSurface,

IpBlt);

return DDHAL_DRIVER_HANDLED;

j lpData-&gt;ddRVal - E JNVALÏDARG; return DDHAL DRIVER HANDLED;

}

ProcAmpControlCloseStream

This method maps directly to a DestroyMoComp method of the DDMOTIONCOMPCALLBACKS structure.

**Example: Mapping DestroyMoComp to ProcAmpControlCloseStream** The following exemplary pseudo code shows how a driver can map the DestroyMoComp DDI call into calls to ProcAmpControlCloseStream.

The sample code shows how the DestroyMoComp function is used for ProcAmp control. If the driver supports other DX-VA functions such as decoding MPEG-2 video streams, the sample code below can be extended to include processing of additional DX-VA GUIDs.

Atty Docket No. MSI-I347ÜS.PAT.APP

CA 02425360 2003-04-14

DWORD APIENTRY

DestroyMoComp( ³ LPDDHALDESTROYMOCOMPDATA lpData ⁴ ) ⁵ { ₅ DXVAJDeviceBaseClass* pDXVABase = ₇ (DXVADeviceBaseClass*) lpData~&gt;lpMoComp-&gt;lpDri verReserved 1 ;

⁸1 if (pDXVABase === NULL) { ¹⁰ lpData-&gt;ddRVal = EJPOINTER;

return DDHAL_DRIVER HANDLED;

} switch (pDXVABase-&gt;m DeviceType) { case DXVADeviceContainer:

¹⁵ lpData-&gt;ddRVal = S_OK;

¹⁶ delete pDXVABase;

¹⁷ break;

IS _]9 case DXVA_DeviceProcAmpControl:

» f

DXVAJProcAmpControlDeviceClass* pDXVADev = (DXVA_ProcAmpControlDeviceClass*)pDXVABase;

²² lpData-&gt;ddRVal = pDXVADev²³ &gt;ProcAmpControlCloseStream();

delete pDXVADev;

}

Atty Docket No. MS1-I347US PAT APP

CA 02425360 2003-04-14

1ί break;

} return DDHALJDRIVERHANDLED;

}

Exemplary Operating Environment for Computer or Other Electronic Device

FIG. 7 illustrates an exemplary computing (or general electronic device) operating environment 700 that is capable of (fully or partially) implementing at least one system, device, component, arrangement, protocol, approach, method, process, some combination thereof, etc. for facilitating interaction between video Tenderers and graphics device drivers as described herein. Computing environment 700 may be utilized in the computer and network architectures described below or in a stand-alone situation.

Exemplary electronic device operating environment 700 is only one example of an environment and is not intended to suggest any limitation as to the scope of use or functionality of the applicable electronic (including computer, game console, television, etc.) architectures. Neither should electronic device environment 700 be interpreted as having any dependency or requirement relating to any one or to any combination of components as illustrated in FIG. 7.

Additionally, facilitating interaction between video Tenderers and graphics device drivers may be implemented with numerous other general purpose or special purpose electronic device (including computing system) environments or configurations. Examples of well known electronic (device) systems, environments, and/or configurations that may be suitable for use include, but are not limited to, personal computers, server computers, thin clients, thick clients,

Atty Docket No. MSM347L'S.PAT.APP

CA 02425360 2003-04-14 tl personal digital assistants (PDAs) or mobile telephones, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, video game machines, game consoles, portable or handheld gaming units, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, some combination thereof, and so forth.

Implementations for facilitating interaction between video tenderers and graphics device drivers may be described in the general context of electronicallyexecutable instructions. Generally, electronically-executable instructions include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Facilitating interaction between video Tenderers and graphics device drivers, as described in certain implementations herein, may also be practiced in distributed computing environments where tasks are performed by remotely-linked processing devices that are connected through a communications link and/or network. Especially in a distributed computing environment, electronically-executable instructions may be located in separate storage media, executed by different processors, and/or propagated over transmission media.

Electronic device environment 700 includes a general-purpose computing device in the form of a computer 702, which may comprise any electronic device with computing and/or processing capabilities. The components of computer 702 may include, but are not limited to, one or more processors or processing units 704, a system memory 706, and a system bus 708 that couples various system components including processor 704 to system memory 706.

Any Docket No. MS M 347US PAT.APP uz

-. i ^; ' &lt; ........ “

CA 02425360 2003-04-14 ί 1

System bus 708 represents one or more of any of several types of wired or wireless bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, such architectures may include an industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MCA) bus, an Enhanced ISA (EISA) bus, a Video Electronics Standards Association (VESA) local bus, a Peripheral Component Interconnects (PCI) bus also known as a Mezzanine bus, some combination thereof, and so forth.

Computer 702 typically includes a variety of electronically-accessible media. Such media may be any available media that is accessible by computer 702 or another electronic device, and it includes both volatile and non-volatile media, removable and non-removable media, and storage and transmission media.

System memory 706 includes electronically-accessible storage media in the form of volatile memory, such as random access memory (RAM) 710, and/or nonvolatile memory, such as read only memory (ROM) 712. A basic input/output system (BIOS) 714, containing the basic routines that help to transfer information between elements within computer 702, such as during start-up, is typically stored in ROM 712. RAM 710 typically contains data and/or program modules/instructions that are immediately accessible to and/or being presently operated on by processing unit 704.

Computer 702 may also include other removable/non-removable and/or volatile/non-volatile storage media. By way of example, FIG. 7 illustrates a hard disk drive or disk drive array 716 for reading from and writing to a (typically) non-removable, non-volatile magnetic media (not separately shown); a magnetic disk drive 718 for reading from and writing to a (typically) removable, non47

Atty Docket No. MSI-I347US.PAT.APP

CA 02425360 2003-04-14 volatile magnetic disk 720 (e.g., a “floppy disk”); and an optical disk drive 722 for reading from and/or writing to a (typically) removable, non-volatile optical disk 724 such as a CD-ROM, DVD, or other optical media. Hard disk drive 716, magnetic disk drive 718, and optical disk drive 722 are each connected to system bus 708 by one or more storage media interfaces 726. Alternatively, hard disk drive 716, magnetic disk drive 718, and optical disk drive 722 may be connected to system bus 708 by one or more other separate or combined interfaces (not shown).

The disk drives and their associated electronically-accessible media provide non-volatile storage of electronically-executable instructions, such as data structures, program modules, and other data for computer 702. Although exemplary computer 702 illustrates a hard disk 716, a removable magnetic disk 720, and a removable optical disk 724, it is to be appreciated that other types of electronically-accessible media may store instructions that are accessible by an electronic device, such as magnetic cassettes or other magnetic storage devices, flash memory, CD-ROM, digital versatile disks (DVD) or other optical storage, RAM, ROM, electrically-erasable programmable read-only memories (EEPROM), and so forth. Such media may also include so-called special purpose or hardwired integrated circuit (IC) chips. In other w^rords, any electronically-accessible media may be utilized to realize the storage media of the exemplary electronic system and environment 700.

Any number of program modules (or other units or sets of instructions) may be stored on hard disk 716, magnetic disk 720, optical disk 724, ROM 712, and/or RAM 710, including by way of general example, an operating system 728, one or more application programs 730, other program modules 732, and program data

Aav Docket So. MSI 1347US.PAT.APP

CA 02425360 2003-04-14 !

734. By way of specific example but not limitation, video Tenderer 410, graphic interface 412, and device driver interface 414 (all of FIG. 4) may be part of operating system 728. Graphics device driver 422 may be part of program modules 732, optionally with a close linkage and/or integral relationship with operating system 728. Also, an instigating program such as Windows® Media® 9 is an example of an application program 730. Image control and/or graphics data that is currently in system memory may be part of program data 734.

A user that is changing ProcAmp or other video settings, for example, may enter commands and/or information into computer 702 via input devices such as a keyboard 736 and a pointing device 738 (e.g., a “mouse”). Other input devices 740 (not shown specifically) may include a microphone, joystick, game pad, satellite dish, serial port, scanner, and/or the like. These and other input devices are connected to processing unit 704 via input/output interfaces 742 that are coupled to system bus 708. However, they and/or output devices may instead be connected by other interface and bus structures, such as a parallel port, a game port, a universal serial bus (USB) port, an IEEE 1394 (“Firewire”) interface, an IEEE 802.11 wireless interface, a Bluetooth® wireless interface, and so forth.

A monitor/view screen 744 (which is an example of display device 436 of FIG. 4) or other type of display device may also be connected to system bus 708 via an interface, such as a video adapter 746. Video adapter 746 (or another component) may be or may include a graphics card (which is an example of graphics device 424) for processing graphics-intensive calculations and for handling demanding display requirements. Typically, a graphics card includes a GPU (such as GPU 426), video RAM (VRAM) (which is an example of video memory 432), etc. to facilitate the expeditious performance of graphics operations.

Atty Docket No. MSl-iJ47US.PAT.APP

CA 02425360 2003-04-14 ]

ό η

In addition to monitor 744, other output peripheral devices may include components such as speakers (not shown) and a printer 748, which may be connected to computer 702 via input/output interfaces 742.

Computer 702 may operate in a networked environment using logical connections to one or more remote computers, such as a remote computing device 750. By way of example, remote computing device 750 may be a personal computer, a portable computer (e.g., laptop computer, tablet computer, PDA, mobile station, etc.), a palm or pocket-sized computer, a gaming device, a server, a router, a network computer, a peer device, other common network node, or another computer type as listed above, and so forth. However, remote computing device 750 is illustrated as a portable computer that may include many or all of the elements and features described herein with respect to computer 702.

Logical connections between computer 702 and remote computer 750 are depicted as a local area network (LAN) 752 and a general wide area network (WAN) 754. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets, the Internet, fixed and mobile telephone networks, other wireless networks, gaming networks, some combination thereof, and so forth.

When implemented in a LAN networking environment, computer 702 is usually connected to LAN 752 via a network interface or adapter 756. When implemented in a WAN networking environment, computer 702 typically includes a modem 758 or other means for establishing communications over WAN 754. Modem 758, which may be internal or external to computer 702, may be connected to system bus 708 via input/output interfaces 742 or any other appropriate mechanism(s). It is to be appreciated that the illustrated network

Atty Docket No. MSl-l34jUS.PAT.APP

CA 02425360 2003-04-14 connections are exemplary and that other means of establishing communication link(s) between computers 702 and 750 may be employed.

In a networked environment, such as that illustrated with electronic device environment 700, program modules or other instructions that are depicted relative to computer 702, or portions thereof, may be fully or partially stored in a remote memory storage device. By way of example, remote application programs 760 reside on a memory component of remote computer 750 but may be usable or otherwise accessible via computer 702. Also, for purposes of illustration, application programs 730 and other electronic-ally-executable instructions such as operating system 728 are illustrated herein as discrete blocks, but it is recognized that such programs, components, and other instructions reside at various times in different storage components of computing device 702 (and/or remote computing device 750) and are executed by data processor(s) 704 of computer 702 (and/or those of remote computing device 750).

Although systems, media, methods, protocols, approaches, processes, arrangements, and other implementations have been described in language specific to structural, logical, algorithmic, and functional features and/or diagrams, it is to be understood that the invention defined in the appended claims is not necessarily limited to the specific features or diagrams described. Rather, the specific features and diagrams are disclosed as exemplary forms of implementing the claimed invention.

Atty Docket No M$t-1.»4?U$.PAT APP