SmartPlayer%20An%20Intelligent%20Media%20Player

1
SmartPlayerAn Intelligent Media Player

• By Ken Chapple Nick Zuiderveld
• CS 510 Advanced Topics in SE
• Prof. Fei Xie

2
Project Objectives

• Formal Design Process
• Gain experience with UML
• Develop problem scenarios, use cases
• Develop classes, objects, etc.
• Component-Based Development
• How to create reusable components
• How to integrate existing components

3
SmartPlayer Application

• A Media Player with Brains
• Serves two primary purposes
• Allows limited file-sampling via central database
• Automatic feature extraction and classification
• SmartPlayer differs from other media players by
  its ability to analyze data files and classify a
  broad range of features
• Key, BPM, Performers vs. Artists, etc.

4
SmartPlayer Introduction

• High-Level Vision
• Interactive organizational tool for media files
• Rationale
• Current systems support only limited criteria
• Community sharing can be informative
• Stakeholders
• Musicians, Music Collectors, Enthusiasts, Novices

5
SmartPlayer Introduction

• Application Responsibilities
• Feature Extraction
• Information retrieval from raw data analysis
• Feature Classification
• Update file metadata based on feature analysis
• Media Control
• Play / view community files
• Network Community Knowledge

6
SmartPlayer Introduction

• Component-Based Approach to Development
• Highly Object-Oriented Design
• Use Cases
• UML
• Class / Object hierarchy
• Application Goals
• Application Extensibility
• Component Reusability
• User Customizability

7
Application Extensibility

• Reasons for Application Extensibility
• New feature extractors may become available
• Online databases
• Raw data analysis tools
• Media formats are evolving (mp3, ogg, etc.)
• Community members increase in numbers
• Other DBMS may be needed to meet demands

8
Application Extensibility

• Attaining Application Extensibility
• Components
• Use existing components
• JMF, JSYN, etc.
• Develop new extensible components
• feature extractors, classifiers, new media
  support
• Design Patterns
• Encapsulate existing components
• Structural patterns for building extensible
  components

9
Component Reusability

• Reasons for Component Reusability
• Other applications may want to integrate feature
  extractors, classifiers, etc.
• Attaining Component Reusability
• Simple and clearly defined interfaces
• Encapsulation and information hiding

10
Secret Agent Class Diagram

11
User Customizability

• Reasons for User Customization
• Different users have different needs
• Attaining User Customizability
• Customizable user interface
• Plugins supported

12
Design

• Clearly defined Use Cases
• Join Group, Import Files, View Community Files
• System components derived from Use Cases
• User Interface
• File Manager
• Database Manager
• Media Controller
• Secret Agent
• CommunityDB

13
Example IMPORT

• UI Select import from file menu
• UI Choose file from file browser / hit OK
• FM Retrieve file, place in dedicated directory
• SA Apply feature extractors and classifiers to
  get information about file
• UI Display SecretAgent recommendations / accept
  recommendations or modify
• DM Add entry to CommunityDB

14
Prototype

• Implemented a subset of Use Cases

15
Example RETRIEVE PLAY

• Listing tunes from community
• UI Select request from menu
• DM Submit query and retrieve result set
• UI Display results
• Play an available song
• UI Select song from playlist / hit play button
• MC Invoke player to start streaming file

16
Project Summary

• What did we learn from the project?
• Translating requirements to design difficult
• Available components difficult to work with
• Difficult to locate components
• Feature extraction technology still in its
  infancy
• Further Information
• http//www.cs.pdx.edu/nrzuider/smart