B. Prabhakaran 1

Multimedia Systems Textbook

Any/Most Multimedia Related Books Reference Papers:

Appropriate reference papers discussed in class from time to time.

You can also bring in papers to be discussed.

B. Prabhakaran 2

Contact InformationB. PrabhakaranDepartment of Computer ScienceUniversity of Texas at DallasMail Station EC 31, PO Box 830688Richardson, TX 75083Email: bprabhakaran@utdallas.eduFax: 972 883 2349URL: http://www.utdallas.edu/~prabaPhone: 972 883 4680Office: ES 3.706Office Hours: Fridays 11am – 12noon

Other times by appointments through emailAnnouncements: Made in class and on course web page.TA: TBA.

B. Prabhakaran 3

Course Outline

Introduction to Multimedia Systems Broad characteristics, requirements, and what makes them

different Operating System Requirements

Disk layout, and scheduling. Media Characteristics & Compression Techniques

Audio, Images, Video, 3D Models, and 3D Motions Metadata Generation

Image & Video Segmentation, Shape-based 3D Retrieval

Proposed Outline (Discussion Sequence Might be Differetnt):

B. Prabhakaran 4

Course Outline

Feature Extraction for Metadata Generation Image & video features to be extracted for metadata generation

Indexing Structures R-trees family, Interval trees family, Special structures for 3D

Motion data indexing Streaming Multimedia Data

Video streaming, 3D models streaming, 3D animation streaming Watermarking Techniques & Security

General strategies, emphasis on 3D watermarking, Security Architectures.

Multimedia Server Architectures Focusing on Video-on-Demand architectures

Proposed Outline…:

B. Prabhakaran 5

Programming Projects No copying/sharing of code/results will be tolerated.

Any instance of cheating in projects will be reported to the University.

Understood: you will need to use open software from the web or other sources.

Must: Declaration of all codes from open software or the Internet. Explicit identification of your efforts in the projects.

Deadlines will be strictly followed for projects submissions.

Projects submissions through demo and email. Demo needed for grading “Research” oriented projects allowed.

B. Prabhakaran 6

Projects Typically, programming projects implementing application of

your interest. Mostly individual projects Projects involving 2 persons (no more than 2) should be

sufficiently complex. Each person’s role should be clearly “visible” Preferably overlapping topics: e.g., metadata + index

structures, index structures + query language, etc. Types of Projects:

Programming Projects: Typical expectation MS and most PhD students

Algorithms/Theory Projects: Perhaps, PhD students doing research in a particular topic

Combo Projects: Algorithms + Programming Perhaps, a team of 1 PhD + 1 MS student

B. Prabhakaran 7

Projects .. Reasonable expectation from my side No need for research paper or technical report at

semester end. But a demo will be needed. I encourage you to develop it as a portfolio

project One that can go onto your Resume/CV

Enough support will be provided by me and the TA.

Several resources will be provided Open software Research papers Lab facilities Discussion time

B. Prabhakaran 8

Projects .. No restriction on programming language or operating

system TA and I will be available for discussions related to

your project Your responsibility to learn the language and/or the

open source you would use. Don’t use the project to learn a new

language/platform. Don’t ask TA or me to debug your program!!

Project topics: Suggestions will be given by me next week. You are encouraged to come up with your own

interesting topic.

B. Prabhakaran 9

2-Track Course Considering diverse nature of possible

projects Project discussions will be mostly one-on-one During office hours or by appointment

Class room discussions will be mostly on various techniques and approaches for multimedia systems.

B. Prabhakaran 10

Home works Approximately 2-3 assignments Each assignment

Short questions on Theory discussed in class Programming resources available for the topic May need at most couple of hours effort

Can be turned in using Email Print outs (allowed, if you hate emails).

B. Prabhakaran 11

Evaluation Project -- 60%

For “depth” – in one or two focused areas 15% -- Initial design document (3 – 5 pages)

Within 3+ weeks 20% -- Mid-term update (6th – 7th week)

Show progress in programming (or design in case of research papers) Identify troubles or difficulties Outline completion schedule/steps 2-3 minutes presentation might be needed.

25% -- Final demo + documentation Short presentation in class might be needed

Homework -- 15% For “breadth” 2-3 home works. To “ensure” awareness in topics other than your project topic.

Exam – 25% For “breadth” “Simple” but thought-provoking questions

B. Prabhakaran 12

Schedule Home works will be announced in class and on

course web page. Along with their due dates

Projects schedule (as discussed earlier) 3rd week – Initial design document (3 – 5 pages) 6th or 7th week – Mid-term update End semester – Final demo or presentation Early finish of projects allowed, if needed by you.

Exam Last day of class or per UTD schedule.