1 / 9

A common protocol for the shelf components

This document outlines a common protocol for integrating multimedia components, designed to streamline connectivity and facilitate data exchange. Key benefits include easy integration of new components, interchangeable parts, and real-time feedback on component functionality. The protocol, based on the Open Sound Control (OSC) standard, supports complex communication patterns and is transport-independent. The proposed system utilizes UDP for message delivery and supports multiple message types, enabling seamless integration of dynamic data streams, event notifications, and control commands for robust multimedia applications.

palmer-maxwell
Télécharger la présentation

A common protocol for the shelf components

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. A common protocol for the shelf components Johannes Wagner (UoA) Adapted by Alessandro Rossi (ENG)

  2. Advantages • Easy to integrate new components • Components can be exchanged • Feedback if component is working • Output can be logged for analyses • Components are compatible to each other Comp A App. Comp B

  3. Open Sound Control (OSC) • Transport-independent and message-based light ware protocol to share data between multimedia devices • Similar to MIDI but more powerful • Free implementations available for all kind of systems and languages • Website: http://opensoundcontrol.org/

  4. OSC Messages • Starts with an OSC Address Pattern followed by an OSC Type Tag Stringand a corresponding number of OSC Arguments • Int32: 32-bit big-endian two's complement integer • Float32: 32-bit big-endian IEEE 754 floating point number • OSC-string: A sequence of non-null ASCII characters followed by a null • OSC-blob An int32 size count, followed by that many 8-bit bytes of arbitrary binary data

  5. Type of data

  6. Proposed Protocol • Based on UDP and OSC • Three type of messages:/strm continuously data stream/evnt event-related data including tags/text text based control messages • Each message has sender id and timestamp in order to synchronize messages • Semantic Items are wrapped as /evnt messages to interact with the Framework

  7. Specification

  8. Stream Example • Sending head position as pair of float32-values sampled at 10 fps, e.g. 0.5s of data (= 5 frames): X 20 20 14 11 10 Y 10 10 11 9 9 • Message:/strm “head_track” 2.0 10.0 2 <data> • Where <data> has 2x4x5 bytes: {40, [20 10 20 10 14 11 11 9 10 9]} • Receiver has to know data type (here: int)!

  9. Event Example • Sending speech event in interval [3.0 5.5]s • Message:/evnt “speech” 3.0 2.5 0 • Sending detected key words and detected emotion in same interval • Message:/evnt “key_words” 3.0 2.5 3 “I” 0.7 “feel” 0.4 “good” 0.9/evnt “emo_voice” 3.0 2.5 1 “happy”, 1.0

More Related