Digital Video for the Next Millennium


This publication is copyright 1999 by the Video Development Initiative (ViDe). The document may not be reproduced, in whole or in part, without written permission from ViDe, except that a single copy for personal use may be printed by the reader. Please direct all comments to the author of this white paper.

   


Section One: The Digital Video Process
Step Three: Playing at the Desktop

When a streamed video file is received at the desktop, the file type must be recognized, through information provided in the header, and then opened. The file must be cached until sufficient data is received to allow for smooth, continuous playback. Playback includes controls such as forward, reverse, stop and play, as well as freeze-frame, content bookmarking, audio volume control and sizing of the viewing window. Client software, frequently a web-browser plug-in or browser helper-application, provides this functionality. If you visit a web site with audio or video, you are usually alerted to the plug-in viewer needed and provided a link for free download of the plug-in. Windows ActiveMovie (aka NetShow), and QuickTime are common file formats with shareware viewers that are found on Internet web sites with video files.

In the past, different client players were required for different file types. Currently, many standard client players have extended their client capabilities to recognize multiple standard file types, such as MPEG-1 (.mpg), ActiveMovie/Video for Windows (.avi), QuickTime (.mov) and RealVideo (.rm and .ram). Progressive Networks' G2 Real Player, with plug-in extensions, and Microsoft's Windows Media Player can open and playback multiple digital video file formats, for example.

Additional functionality provided at the client, in collaboration with the server, can include permission to save a file to hard drive, maximizing of playback based on network connection (e.g. 28.8 KB, 56 KB, T1, etc.) and auto-selection of video file format for a video asset transcoded in multiple formats, usually based on the bandwidth capability of the client network connection.