Latest revision as of 15:49, 10 June 2021

What is ohMedia?

OpenHome Media (ohMedia) is an open standard for networked audio devices in the home. Devices can implement ohMedia in place of, or alongside of, the UPnP Forum’s AV standards. It offers a number of advantages over the UPnP Forum's AV standards.

Easier to program against.
- UPnP forum services have large numbers of optional features. While this makes it easy for device manufacturers to implement a service, it is hard to write control points and interoperability between devices becomes poor. ohMedia uses options sparingly, typically at a service level. This enables clear, consistent behaviour across devices from different manufacturers.
Better support for playlists
- Playlists are stored on the renderer, allowing playback to continue when the control point leaves the network (e.g. your tablet goes to sleep, runs out of battery, or leaves the wifi zone).
- Multiple control points are supported. A second controller can discover and display a playlist setup by a different device. Edits to the playlist from either controller will be immediately reflected in the other.
- Storing playlists on the renderer also allows for gapless playback, avoiding gaps between tracks that were intended to merge seamlessly. This is particularly important for live albums and classical music.
Control the room, not just a device
- ohMedia topology algorithms allow multi-box systems to be easily managed from a single control point application
Easy to share music
- The Songcast protocol allows an ohMedia renderer to share its content with any other ohMedia device or listen to content from another device. Synchronised audio can be played between any number of devices.
- Desktop songcast applications plus mobile support (Songcast app for Android; Airplay receiver for iOS) allows content from many other devices to be shared.
Richer set of audio sources
- In addition to Playlist, Songcast and external digital and analogue inputs, internet radio and a receiver for Apple's AirPlay are also natively supported.

Developers

If you are interested in ohMedia development, further information is available

@@ Line 1: / Line 1: @@
 =What is ohMedia?=
-ohMedia is an open standard for networked audio devices. Devices can implement it in place of or in addition to the UPnP Forum’s AV standards. It offers a number of advantages over basic UPnP:
+OpenHome Media (ohMedia) is an open standard for networked audio devices in the home.  Devices can implement ohMedia in place of, or alongside of, the UPnP Forum’s AV standards.  It offers a number of advantages over the UPnP Forum's AV standards.
-* Playlists are stored on the renderer, allowing playback to continue when the control point leaves the network (e.g. the control point application closes or its host device powers down).
+* Easier to program against.
-* Storing playlists on the renderer also allows for gapless playback, avoiding gaps between tracks that were intended to merge seamlessly. This is particularly important for live albums and classical music.
+** UPnP forum services have large numbers of optional features.  While this makes it easy for device manufacturers to implement a service, it is hard to write control points and interoperability between devices becomes poor.  ohMedia uses options sparingly, typically at a service level.  This enables clear, consistent behaviour across devices from different manufacturers.
-* Multiple control points are better supported. Storing a playlist on the renderer allows multiple control points to edit the order of tracks and display metadata (including track name and album art) for the entire playlist.
+* Better support for playlists
-* Share music between renderers. The Songcast protocol allows an ohMedia renderer to share its content with any other ohMedia device or listen to content from another device. Synchronised audio can be played between any number of devices. Desktop songcast applications plus mobile support (Songcast app for Android; Airplay receiver for iOS) allows content from many other devices to be shared.
+** Playlists are stored on the renderer, allowing playback to continue when the control point leaves the network (e.g. your tablet goes to sleep, runs out of battery, or leaves the wifi zone).
-* Internet radio and a receiver for Apple's AirPlay are also natively supported.
+** Multiple control points are supported.  A second controller can discover and display a playlist setup by a different device.  Edits to the playlist from either controller will be immediately reflected in the other.
-* Playlists can be more easily & reliably saved and reused. Many popular UPnP media servers change track URIs whenever they rebuild their database (e.g. every time new content is added to the database). ohMedia’s reference server - Songbox - guarantees to retain track URIs across rebuilds, allowing saving and repeated reuse of playlists.
+** Storing playlists on the renderer also allows for gapless playback, avoiding gaps between tracks that were intended to merge seamlessly. This is particularly important for live albums and classical music.
-* Support for multi-product hi-fi systems. E.g. a media renderer with a separate pre-amp. ohMedia topology algorithms allow a control point to select the volume control on the pre-amp.
+* Control the room, not just a device
+** ohMedia topology algorithms allow multi-box systems to be easily managed from a single control point application
+* Easy to share music
+** The Songcast protocol allows an ohMedia renderer to share its content with any other ohMedia device or listen to content from another device. Synchronised audio can be played between any number of devices.
+** Desktop songcast applications plus mobile support (Songcast app for Android; Airplay receiver for iOS) allows content from many other devices to be shared.
+* Richer set of audio sources
+** In addition to Playlist, Songcast and external digital and analogue inputs, internet radio and a receiver for Apple's AirPlay are also natively supported.
-= Reference Implementations =
+= Developers =
+If you are interested in ohMedia development, [[OhMediaDevelopers | further information is available]]