SMIL - Synchronized Multimedia Integration Language

Overview

The Synchronized Multimedia Integration Language (SMIL, pronounced "smile") enables simple authoring of interactive audiovisual presentations.

SMIL is typically used for "rich media"/multimedia presentations which integrate streaming audio and video with images, text or any other media type.

SMIL is an easy-to-learn HTML-like language (XML based), and many SMIL presentations are written using a simple text-editor.

Uses

[Screen capture - a captioned QuickTime Video]

SMIL can be used to:

Status / History

SMIL 1.0 - W3C Recommendation - June, 1998
[http://www.w3.org/TR/REC-smil]

SMIL 2.0 - W3C Recommendation - January, 2005
[http://www.w3.org/TR/2005/REC-SMIL2-20050107/]

SMIL 2.1 - W3C Recommendation - December, 2005
[http://www.w3.org/TR/2005/REC-SMIL2-20051213/]

Why Captioning is Important

Captioned video is important for a number of different reasons. There is a legal and moral imperative to ensure equal access to material, especially when access to that material is critical to a user completing a task or understanding a fundamental lesson. A number of current accessibility standards and guidelines mandate captioned video for this reason:

Equally important is that, when implemented in certain ways, SMIL text transcripts are searchable and index-able by various search engines and other data-management tools.

Options:

Captioned videos can be streamed in a number of different formats:

Each format has it's strengths and weaknesses, as we shall see.

QuickTime

[Screen capture - a captioned QuickTime Video]

The QuickTime player supports captioning (using SMIL) in two ways; "embedded" captioning and "linked" captioning.

Method 1 (Embedded)

This method involves creating what is called a QuickTime text track and making it a part of your QuickTime movie. You will end up with one QuickTime movie file that contains audio, video, and your captions. This method requires QuickTime Pro, which can be purchased and downloaded from Apple.

Method 2 (Linked)

The second method involves creating a text track movie as a separate file. The QuickTime audio/video movie and the text track are put together with SMIL. You will end up with three files:

  1. The QuickTime movie containing audio and video
  2. The text (caption) track
  3. The SMIL file that puts them all together

How-to/Tutorial: http://www.webaim.org/techniques/captions/QuickTime/

RealMedia

[Screen capture - a captioned RealMedia Video]

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.

RealText files are text files that have an .rt extension. They can be created using a text editor or a tool such as MAGpie or HiCaption.

How-to/Tutorial: http://www.webaim.org/techniques/captions/real/

SAMI

[Screen capture - a captioned WindowsMedia Video]

SAMI (Synchronized Accessible Media Interchange) is similar to SMIL but was developed by Microsoft and is supported solely by Microsoft products, including Microsoft Encarta® Encyclopedia, Windows Media™ Player, and some Microsoft multimedia titles.

Unlike SMIL, which points to an external caption file (.rt for RealPlayer and .mov or .txt for QuickTime - linked), SAMI files contain the captions themselves.

Windows Media Player uses an ASX (or sometimes WVX or WAX) to combine the SAMI captions with the media file. The captions can also be automatically added to a media file when they are both embedded within a web page.

Note

For captions to display in the stand-alone Windows Media Player, they must usually be turned on manually. This can be done by selecting View > Captions or View > Now Playing Tools > Captions in older versions of Windows Media Player. In Windows Media Player 9 or newer, select Play > Captions and Subtitles > On if Available (or English). In Windows Media Player 10, you may have to enable Tools > Options > Security > Show local captions when present to view local caption files.

Adding SAMI Closed Captions to Digital Media: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwmt/html/wmp7_sami.asp

Flash

[Screen capture - Flash Player]

SMIL as XML can also be incorporated into Flash videos using third party extensions. However, without a fair bit of post-production, the index-ability of captioned Flash files is still poor.

Additional Resources

Tools for adding captioning to Flash videos include HiSoftware's Hi-Caption viewer Component, Camtasia and Captionate's captioning skins.

Issues & Problems

Media Players:

Currently the biggest issue for deploying SMIL is that while files may use the .smil file extension (Mime-type), more than one media player supports the mime-type, but each player supports it differently, and due to their construction files are not inter-operable. Thus, serving up a raw .smil file may potentially fail for a significant portion of your audience.

There are easy solutions for this however - you can use a real player meta file (.rpm) to contain a reference to the .smil file - RealPlayer will play the .rpm which points it to the .smil (or .smi). For QT, you can create a QT reference movie to accomplish the same task; Apple provides a free tool to do this (MakeRefMovie). The reference movie is a .mov file that just references the .smil (or .sml - another recognized smil file).

Embedded vs. Linked:

As mentioned earlier, embedded captioning is not searchable by the major search engines or file management tools. For this reason, linked transcripts are preferable, although they may also need to be processed via XSLT style sheets for re-purposing on the web.

Recommendations

Indexing & Searchability

  • QuickTime SMIL
  • RealMedia SMIL

QuickTime SMIL and RealMedia SMIL with separate text files are the better solution, as text files remain index-able and readable to users unable to access the media content, or devices that do not support the media stream.

Accessibility

  • Windows Media Player
  • RealOne Player

The standalone versions of the three media players are far more accessible than the embedded versions. Of the three standalone players, Windows Media Player and RealOne Player presented a high level of accessibility. In all cases, newer versions of media players were at least as accessible as their predecessors, if not exponentially so. When possible, it is probably a good idea to provide the user with multiple options for accessing your media content. [ http://www.webaim.org/techniques/captions/mediaplayers/]

User-acceptance

  • Flash
  • Windows Media

Captioned Flash media avoids media-player conflicts.

Tools

Tools (cont.)

Services

SOAP

Stanford Online Accessibility Program

[Screen Capture - the Stanford Online Accessbility Program web site]