Solutions to Common Video Artifacts (Windows CE 5.0)
Several problems are inherent in displaying broadcast video on display devices other than televisions. This topic briefly discusses some common problems and describes how DirectDraw video-port extensions tries to solve them.
NTSC Interlaced Display and Interleaved Memory
An NTSC signal broadcasts video at an approximate rate of 30 frames, or 60 fields, per second. Like a frame, a field in an NTSC signal is independent of the other field in a frame and can contain different image data. For more information on this behavior, see Video Frames and Fields.
The problems caused by the independence of fields within a frame become apparent when two fields are interleaved for display. In video with a lot of movement, the two fields of a single frame will contain images that do not match each other, resulting in motion artifacts.
One way that developers have tried to work around this behavior is by discarding one of the fields. This solution causes a loss in image quality by roughly one-half, but provides acceptable results for some purposes.
Another method frequently used is to display fields individually, stretching each vertically by a factor of two when it is displayed. This provides better image quality, but because fields are offset by one pixel in the y-direction, the result is an animation that jitters up and down as it plays.
DirectDraw video-port extensions can employ two, more advanced, techniques for improving image quality, known as Bob and Weave. Both are supported by the DirectDraw overlay surfaces that are used with video-port extensions.
The first algorithm, Bob, is very similar to the method of displaying each field in a frame individually. However, for each field, the overlay's source rectangle is adjusted to accommodate for any jittering effects. Effectively, the source rectangle bounces up and down in time with the fields, negating the jittering on the screen.
The following illustration shows this process.
.gif "ms924639.bob(en-us,MSDN.10).gif")
The Weave algorithm provides the best image quality for material that originates from film by exploiting a common technique used in the video industry for converting motion pictures to television.
Unlike Bob, a video-port object does not Weave by itself; you must combine the default overlay behavior of displaying both fields simultaneously with kernel mode video transport to implement the algorithm.
Here is a synopsis of the algorithm: Motion pictures capture video at a rate of 24 frames per second. When converting a motion picture for television, technicians use a technique called 3:2 pulldown to convert the frame rate to the 30 frames per second required for television broadcasts.
This technique involves inserting a redundant field for every four true fields in the video stream to come up with the required number of fields.
When you weave, you are reversing this process. You detect when 3:2 pulldown is being used, removing any redundant fields to restore the original motion-picture frames. The fields that make up the restored frames can then be interleaved in memory without risk of motion artifacts.
Occasionally, the pattern of redundant frames will change due to edits within the original film or reel breaks. You must monitor when these changes occur and update the behavior to adjust for the new pattern.
By default, an overlay surface displays both fields simultaneously. This works well if you are implementing the Weave algorithm, but prevents the video port from using the Bob algorithm.
You can programmatically change how the overlay treats video data by calling the IDirectDrawSurface5::UpdateOverlay method.
The flags you include in the dwFlags parameter determine the overlay's behavior: if you include the DDOVER_BOB flag, the video port will use the Bob algorithm; if you do not, it displays both fields.
If you display both fields simultaneously, the resulting video will show motion artifacts.
Send Feedback on this topic to the authors