Unit 1
Unit 1
Unit 1
INTRODUCTION
The connection between computers and ideas about multimedia covers what is
actually only a short period:
1945 - Vannevar Bush wrote a landmark article describing what amounts to a
hypermedia system called Memex.
1960 - Ted Nelson coined the term hypertext.
•1967 - Nicholas Negroponte formed the Architecture Machine Group.
•1968 - Douglas Engelbart demonstrated the On-Line System (NLS), another very
early hypertext program.
•1969 - Nelson and van Dam at Brown University created an early hyper text editor
called FRESS.
•1976 - The MIT Architecture Machine Group proposed a project entitled Multiple
Media - resulted in the Aspen Movie Map, the first hypermedia videodisk, in 1978.
1985 - Negroponte and Wiesner co-founded the MIT Media Lab.
•1989 - Tim Berners-Lee proposed the World Wide Web
Cont.
Distributed Networks
Temporal relationship between data
Render different data at same time — continuously.
Sequencing within the media
playing frames in correct order/time frame in video
Synchronisation — inter-media scheduling
E.g. Video and Audio — Lip synchronisation is clearly important
for humans to watch playback of video and audio and even animation
and audio.
Key Issues for Multimedia Systems
The key issues multimedia systems need to deal with here are:
How to represent and store temporal information.
back/retrieval
What process are involved in the above.
Components of a Multimedia System
Now let us consider the Components (Hardware and Software) required for a
multimedia system:
Capture devices — Video Camera, Video Recorder, Audio Microphone,
Intranets, Internets.
Computer Systems — Multimedia Desktop machines, Workstations,
MPEG/VIDEO/DSP Hardware
Display Devices — CD-quality speakers, HDTV,SVGA, Hi-Res monitors,
and nonlinearity.
It allows users to navigate through information in a non-sequential
hyperlinks.
It allows users to access related information by clicking on hyperlinked
XML: a markup language for the WWW in which there is modularity of data,
structure and view so that user or application can be able to define the tags
(structure).
Example of using XML to retrieve stock information from a database according to a
user query:
First use a global Document Type Definition (DTD) that is already defined.
The server side script will abide by the DTD rules to generate an XML document
according to the query using data from your database.
Finally send user the XML Style Sheet (XSL) depending on the type of device used to
display the information
The following XML related specifications are also standardized:
XML Protocol:used to exchange XML information between processes.
XML Schema:a more structured and powerful language for defining XML data types (tags).
XSL: basically CSS for XML.
SMIL: synchronized Multimedia Integration Language
a particular application of XML (globally predefined DTD) that allows for
specification of interaction among any media types and user input, in a
temporally scripted manner
Purpose of SMIL: it is also desirable to be able to publish multimedia
presentations using a markup language.
A multimedia markup language needs to enable scheduling and synchronization
of different multimedia elements, and define their interactivity with the user.
The W3C established a Working Group in 1997 to come up with specifications
for a multimedia synchronization language
Designed to:
For all skill levels of WWW authors
Schedule audio, video, text, and graphics files across a timeline
Cont.
No need to master development tools or complex programming languages.
HTML-like need a text editor only
Links to media — media not embedded in SMIL file
Drawbacks of SMIL:
Good Points:
A powerful tool for creating synchronized multimedia presentations on the web
Deals with low bandwidth connections.
Bad Points:
Meant to work with linear presentations
Several types of media can be synchronized to one timeline.
Does not work well with non-linear presentations
Ability to skip around in the timeline is buggy.
For slideshow style mixed media presentations it the best the web has to offer.
SMIL supports:
SMIL supports:
The W3C recommended SMIL in June 1998
Quicktime 4.0 supports SMIL (1999)
Not universally supported across the Web.
No Web browser directly support SMIL
RealPlayer G2 supports SMIL
Many other SMIL-compliant players, authoring tools, and servers available.
Running SMIL Applications
For this course there are basically three ways to run SMIL applications (two
use the a Java Applet) so there are basically two SMIL supported mediums:
Quicktime — supported since Quicktime Version 4.0.
RealPlayer G2 — integrated SMIL support
Web Browser — use the SOJA SMIL applet viewer with html wrapper
Applet Viewer — use the SOJA SMIL applet viewer with html wrapper