Create the page "Openhome" on this wiki!

• OhNet
  OpenHome Networking (ohNet) is a modern, cross platform UPnP stack. ohNet includes Proxies and Providers are included for all OpenHome and UPnP AV services. If your application uses other services, ohNet inclu
  2 KB (379 words) - 12:28, 7 June 2018
• OhMedia
  OpenHome Media (ohMedia) is an open standard for networked audio devices in the home
  2 KB (326 words) - 15:49, 10 June 2021
• OhMediaDevelopers
  ...e ohPipeline] contains [https://github.com/openhome/ohPipeline/tree/master/OpenHome/Net/Odp reference code] for control point or device stacks. ...The bulk of the code required is also available in the [https://github.com/openhome/ohSongcast ohSongcast] repo.
  5 KB (742 words) - 08:56, 17 August 2018
• OhWidget Technical Overview
  ...ice of hardware configuration used by Node manufacturers is not defined by OpenHome, and is not constrained by the ohWidget software. OpenHome recommend and support a small form-factor to easily introduce Nodes into th
  30 KB (4,786 words) - 15:08, 1 March 2012
• OhWidget Driver Development
  .... Each Widget must have its own driver to allow it to communicate with the OpenHome Nodes. ...t does not contain advice on how to write Widget Service XML. Refer to the OpenHome Widget Service XML definition document for more details.
  48 KB (6,036 words) - 15:28, 1 March 2012
• OhWidget Service XML Definition
  This document is for Widget manufacturers using OpenHome to define Widget services and properties. ...vices and properties are defined in XML, following the schema published by OpenHome.
  20 KB (3,122 words) - 15:34, 1 March 2012
• TidalStreamingService
  ...peak to us for help if you think that your access to the API would benefit OpenHome.
  939 B (163 words) - 10:23, 3 March 2015
• Av:Developer:EriskayServices
  This page describes APIs for Eriskay, the second major release of OpenHome network services. ... is in the <tt>openhome.org</tt> domain; all other services are in the <tt>openhome.org.eriskay</tt> domain. Provision of the device service is mandatory; all
  1 KB (171 words) - 18:44, 14 December 2015
• Av:Developer:Eriskay:TransportService
  ...s provided in a number of levels, each of which have a URI and metadata in OpenHome Metadata format. E.g. A (notional) internet radio service that broadcast i <br>domain: "openhome.org.eriskay"
  18 KB (1,963 words) - 12:09, 15 December 2015
• Av:Developer:Eriskay:ProductService
  ...duct</tt> attribute, control points should begin their interaction with an OpenHome device by using the Product service. Presence of various other services ca * <tt>Playlist</tt> - the <tt>openhome.org.eriskay:Playlist:1</tt> service must be available
  8 KB (904 words) - 12:10, 15 December 2015
• Av:Developer:Eriskay:SenderService
  ...be discovered independently of the Product service by checking for the <tt>openhome.org.sender</tt> attribute on the [[Av:Developer:Eriskay:DeviceService | Dev Provides basic information about the sender in OpenHome Metadata format.
  4 KB (400 words) - 13:15, 15 December 2015
• Av:Developer:Eriskay:ReceiverService
  The metadata of the sender to listen to. In the OpenHome Metadata format provided by the [[Av:Developer:Eriskay:SenderService | Send <br>domain: "openhome.org.eriskay"
  2 KB (228 words) - 13:28, 15 December 2015
• Av:Developer:Eriskay:DeviceService
  ...device and resolving questions of compatibility between that device and an OpenHome control point. ...ce service in order to establish whether the device is compatible with the OpenHome client software with which the control point was built.
  10 KB (783 words) - 14:42, 15 December 2015
• Av:Developer:Eriskay:StreamingServices
  ...peak to us for help if you think that your access to the API would benefit OpenHome.
  3 KB (399 words) - 14:47, 15 December 2015
• Av:Developer:Eriskay:DavaarChanges
  ...o search for this – its presence can be inferred by checking for the <tt>openhome.org.product</tt> attribute in the versions section of the [[Av:Developer:Er <tt>Metadata</tt> format has changed from DIDL-Lite to OpenHome Metadata.
  7 KB (1,073 words) - 14:54, 15 December 2015
• CalmRadioInternetRadio
  ...peak to us for help if you think that your access to the API would benefit OpenHome.
  1 KB (193 words) - 08:26, 2 June 2017
• Av:Developer:Scd
  ...ct (SCD) can be used to send decoded audio from any computing device to an OpenHome device. The Sender device is responsible for decoding audio to PCM, framin [https://github.com/openhome/ohPipeline/tree/master/OpenHome/Av/Scd ohPipeline] contains sample code.
  11 KB (1,661 words) - 10:08, 13 December 2019
• Av:Developer:Odp
  = OpenHome Device Protocol = ...ODP) allows a control point to control and receive evented updates from an OpenHome device using a single TCP socket. This has some advantages over UPnP:
  7 KB (859 words) - 15:45, 17 May 2019
• Av::OhMetadata
  = OpenHome Metadata Format = OpenHome Metadata format describes metadata for an audio track as a series of key-va
  2 KB (244 words) - 14:32, 20 December 2017