<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Design&gt;Accessibility&gt;Multimedia&gt;Video</title>	<link>http://tc.eserver.org/dir/Design/Accessibility/Multimedia/Video</link>
	<description>A listing of the most recently indexed works about Design and Accessibility and Multimedia and Video in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Design&gt;Accessibility&gt;Multimedia&gt;Video</title>
		<link>http://tc.eserver.org/dir/Design/Accessibility/Multimedia/Video</link>
	</image>
	<item>
		<title>Best Practices in Online Captioning</title>
		<link>http://tc.eserver.org/30603.html</link>
		<guid>http://tc.eserver.org/30603.html</guid>
		<description>Use of online video has grown faster than the use of accessibility in online video. Though bandwidth costs for video files can still be high compared to ordinary text-and-graphics Web pages, it is nonetheless easy to digitize video and post it online. It&apos;s easier to broadcast your video to the world via the Internet than it is to get the same video on television. Online multimedia are a useful and valid new medium of communication - for most people.</description>
	</item>
	<item>
		<title>Captioning for QuickTime</title>
		<link>http://tc.eserver.org/22988.html</link>
		<guid>http://tc.eserver.org/22988.html</guid>
		<description>There are two methods for adding captions in QuickTime. There are advantages and disadvantages to each approach. The first allows you to maintain a single file, making the captioned video easier to distribute. The second approach allows you to easily deliver a captioned and non-captioned version of your movie, but requires an understanding of SMIL (it&apos;s not too hard).</description>
	</item>
	<item>
		<title>Captioning for RealPlayer</title>
		<link>http://tc.eserver.org/22990.html</link>
		<guid>http://tc.eserver.org/22990.html</guid>
		<description>RealPlayer uses SMIL to combine media content with a RealText (.rt) file. The .rt file contains the captions themselves and information about how and when they should appear. The SMIL file is really just a pointer file. It contains information about where and how your captions and media content should display.</description>
	</item>
	<item>
		<title>Captioning for Windows Media</title>
		<link>http://tc.eserver.org/22989.html</link>
		<guid>http://tc.eserver.org/22989.html</guid>
		<description>Windows Media Player adds captions using Microsoft&apos;s Synchronized Accessible  Media Interchange (SAMI). SAMI, like SMIL, which is used by Quicktime  and RealPlayer, is an XML-based text language. A  SAMI file contains the captions and definitions for how and when the captions  should display.</description>
	</item>
	<item>
		<title>Media Player Accessibility</title>
		<link>http://tc.eserver.org/22991.html</link>
		<guid>http://tc.eserver.org/22991.html</guid>
		<description>When delivering multimedia content for the three major media players (Windows Media Player, Quicktime and RealMedia Player), the developer must choose whether to have the viewer access the content through a player embedded in a Web page or through a standalone player. Both methods have their advantages. Embedding the player in a Web page allows the user to access the content without another application opening. The standalone players usually have more control options.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Design/Accessibility/Multimedia/Video.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>