Difference between revisions of "Developer:Davaar:Topology"
(Created page with '== Introduction == The Linn DS family of products all have a standard way of presenting themselves to the network. This makes it possible to write generic Control Point software…') |
|||
| Line 1: | Line 1: | ||
== Introduction == | == Introduction == | ||
| − | + | Openhome products all have a standard way of presenting themselves to the network. This makes it possible to write generic Control Point software that is able to control those products independent of Manufacturer or specific features. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
The technologies associated with making this possible are grouped under the term Topology. | The technologies associated with making this possible are grouped under the term Topology. | ||
| − | If a developer wishes to write generic software that participates in the aims described above, then they should write that software in a way that conforms to the strategies and algorithms of | + | If a developer wishes to write generic software that participates in the aims described above, then they should write that software in a way that conforms to the strategies and algorithms of Openhome Topology, which is described below |
== Topology - Room/Source == | == Topology - Room/Source == | ||
| Line 16: | Line 11: | ||
=== Functional Units === | === Functional Units === | ||
| − | + | An Openhome consists of products from a variety of manufacturers each bearing the [[Developer:Davaar:ProductService|Product service]]. | |
| − | |||
| − | |||
| − | + | Amongst other information, each product has: | |
| − | |||
* Room (user configurable, defaults to 'Main Room') | * Room (user configurable, defaults to 'Main Room') | ||
| − | * Name (user configurable, defaults to the | + | * Name (user configurable, defaults to the model name) |
| − | * Source Count (fixed | + | * Source Count (fixed according to the capabilities of the product) |
* List of Sources, each with its own Type, Name, and Visibility | * List of Sources, each with its own Type, Name, and Visibility | ||
| + | |||
| + | * Attributes, identifying additional functionality offered by the product | ||
=== Proper Configuration === | === Proper Configuration === | ||
| − | In a properly configured system a | + | The name of each product represents its audio output. |
| + | |||
| + | The name of each source represents an audio input (either internal or external). | ||
| + | |||
| + | In a properly configured system, if one product is connected to another using a audio cable, then the name of the product sending the audio should match the name of the source receiving the audio. It is by matching these names that a Control Point is able to select the correct input on, for instance, a preamp when a particular source is selected. | ||
| − | + | === Discovering An Openhome System === | |
| − | The | + | The correct way to discover an Openhome system is to: |
| − | + | * search for all units bearing the Product:1 service | |
| − | + | * subscribe to each Product service | |
| − | + | * group these products according to their Room. | |
| − | * | + | * collect the name of all the sources in each product |
| − | * | + | * match the names of the sources to the names of the products to create a set of tree structures in each room. |
| − | + | === Source Functionality === | |
| − | + | To determine the kind of functionality available on each source, inspect its type. | |
| − | + | If it has type Playlist, it additionally contains the [[Developer:Davaar:PlaylistService|Playlist service]] | |
| − | + | If it has type Radio, it additionally contains the [[Developer:Davaar:RadioService|Radio service]] | |
| − | + | If it has type Receiver, it additionally contains the [[Developer:Davaar:ReceiverService|Receiver service]] | |
| − | + | === Volume Control === | |
| − | + | Products that offer volume control include the Volume attribute and the [[Developer:Davaar:VolumeService|Volume service]] | |
| − | + | The primary volume control offered by a control point should be that situated nearest the root in the tree structure that contains the current source. | |
| − | |||
<br> <br> | <br> <br> | ||
Revision as of 15:20, 24 November 2010
Contents
Introduction
Openhome products all have a standard way of presenting themselves to the network. This makes it possible to write generic Control Point software that is able to control those products independent of Manufacturer or specific features.
The technologies associated with making this possible are grouped under the term Topology.
If a developer wishes to write generic software that participates in the aims described above, then they should write that software in a way that conforms to the strategies and algorithms of Openhome Topology, which is described below
Topology - Room/Source
Functional Units
An Openhome consists of products from a variety of manufacturers each bearing the Product service.
Amongst other information, each product has:
- Room (user configurable, defaults to 'Main Room')
- Name (user configurable, defaults to the model name)
- Source Count (fixed according to the capabilities of the product)
- List of Sources, each with its own Type, Name, and Visibility
- Attributes, identifying additional functionality offered by the product
Proper Configuration
The name of each product represents its audio output.
The name of each source represents an audio input (either internal or external).
In a properly configured system, if one product is connected to another using a audio cable, then the name of the product sending the audio should match the name of the source receiving the audio. It is by matching these names that a Control Point is able to select the correct input on, for instance, a preamp when a particular source is selected.
Discovering An Openhome System
The correct way to discover an Openhome system is to:
- search for all units bearing the Product:1 service
- subscribe to each Product service
- group these products according to their Room.
- collect the name of all the sources in each product
- match the names of the sources to the names of the products to create a set of tree structures in each room.
Source Functionality
To determine the kind of functionality available on each source, inspect its type.
If it has type Playlist, it additionally contains the Playlist service
If it has type Radio, it additionally contains the Radio service
If it has type Receiver, it additionally contains the Receiver service
Volume Control
Products that offer volume control include the Volume attribute and the Volume service
The primary volume control offered by a control point should be that situated nearest the root in the tree structure that contains the current source.
