1 / 9

Virtual Symphony Orchestra

Virtual Symphony Orchestra. System Design Review: Concurrency. Concurrent Processes. Video subsystem: Decompression of the video files Prefetching of video images Tracking subsystem: Image decompression Image processing Image analysis Audio subsystem:

wdowd
Download Presentation

Virtual Symphony Orchestra

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Virtual Symphony Orchestra System Design Review: Concurrency VSO – Virtual Symphony Orchestra | System Design Review: Concurrency | Christian Klaus Kern <kern@in.tum.de>

  2. Concurrent Processes • Video subsystem: • Decompression of the video files • Prefetching of video images • Tracking subsystem: • Image decompression • Image processing • Image analysis • Audio subsystem: • When compression is used, decompressing VSO | System Design Review: Concurrency | Christian Klaus Kern <kern@in.tum.de>

  3. Realization • Threaded programming • The program can use more than one CPU of a machine at the same time • Usage of different packages • Since the program is devided into subclasses and packages that are independent we are able to use more computers (grid computing) • Because of the observer pattern the program is easily scalable VSO | System Design Review: Concurrency | Christian Klaus Kern <kern@in.tum.de>

  4. Deployment Diagram :Server Orchestra Tracking :AudioClient :VideoClient Orchestra Orchestra Audioapplication Videoapplication VSO | System Design Review: Concurrency | Christian Klaus Kern <kern@in.tum.de>

  5. Possible Problems • Audioprocessing should take place on one local machine because it requires complete synchronization and there must not be any latency between the threads • An external timekeeper has to be established to oversee the synchronization of audio and video • If network traffic increases, the program can easily get out of sync VSO | System Design Review: Concurrency | Christian Klaus Kern <kern@in.tum.de>

  6. Possible Problems(2) • The threads of the tracking application have to be all ready before the gesture can be interpreted correctly • The computer on which the admin-view is running has to be able to playback all the videostreams at the same time (compressed videostreams) VSO | System Design Review: Concurrency | Christian Klaus Kern <kern@in.tum.de>

  7. Hardware- / Softwaremapping • We can have two computers that are providing the video data e.g. for video projectors VSO | System Design Review: Concurrency | Christian Klaus Kern <kern@in.tum.de>

  8. Possible other Scenarios There is a possible configuration with a conductor in one and several listeners in another room, enjoying a virtual trip through the orchestra VSO | System Design Review: Concurrency | Christian Klaus Kern <kern@in.tum.de>

  9. Thank you for your attention E-Mail: kern@in.tum.de VSO | System Design Review: Concurrency | Christian Klaus Kern <kern@in.tum.de>

More Related