Difference between revisions of "Developer:Davaar:Topology"

From LinnDocs
Jump to: navigation, search
m (Volume Control)
 
(8 intermediate revisions by one other user not shown)
Line 3: Line 3:
 
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.
 
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 Openhome 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
 
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 ==
  
=== Functional Units ===
+
=== Products ===
  
An Openhome consists of products from a variety of manufacturers each bearing the [[Developer:Davaar:ProductService|Product service]].
+
An Openhome installation consists of products from a variety of manufacturers each bearing the [[Developer:Davaar:ProductService|Product service]].
  
 
Amongst other information, each product has:
 
Amongst other information, each product has:
Line 31: Line 31:
 
The name of each source represents an audio input (either internal or external).
 
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.
+
In a properly configured system, if one product is connected to another using an 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 ===
 
=== Discovering An Openhome System ===
Line 37: Line 37:
 
The correct way to discover an Openhome system is to:
 
The correct way to discover an Openhome system is to:
  
* search for all units bearing the Product:1 service
+
* search for all units bearing the Product service
  
 
* subscribe to each Product service
 
* subscribe to each Product service
Line 59: Line 59:
 
=== Volume Control ===
 
=== Volume Control ===
  
Products that offer volume control include the Volume attribute and the [[Developer:Davaar:VolumeService|Volume service]]
+
Products that offer volume control include the Volume attribute and the <span class="plainlinks">[http://wiki.openhome.org/wiki/Av:Developer:VolumeService <u>Volume Service</u>]</span> <!-- [[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.
+
The primary volume control offered by a control point should be the one situated nearest the root in the tree structure that contains the current source.
  
 
+
Control points may optionally provide the user with control of the volume of each product within the tree.
<br> <br>
 

Latest revision as of 08:43, 13 March 2020

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 Openhome 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

Products

An Openhome installation 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 an 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 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 the one situated nearest the root in the tree structure that contains the current source.

Control points may optionally provide the user with control of the volume of each product within the tree.