Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Class: Audio
#1
General Description

This thread is for discussion of the Audio device class. Drivers that implement this device class provide volume and mute control on an audio source.

This is one of those 'fractional' device classes. I.e. it's unlikely any driver would just implement this one class. It will be implemented in addition to other things.

Fields Provided
[INDENT]The fields provided by this device class have pre-determined names, and these MUST be implemented as indicated here. They are all prefixed by the device class prefix in one of the forms:

AUD#fieldname
AUD#sub~fieldname

where AUD# indicates it is a field of this device class, and fieldname meets the general requirements of CQC field names. If the device provides more than one audio source, then the sub~ part will be present and will indicate the specific source instances, see the Multi-Unit section below.

The fields provided by this class are:
  • AdjustVolume. This field allows for incremental adjustment up or down of the volume relative to its current value. It MUST be marked with the VolumeAdj semantic field type and conform to the definition of that type.
  • Mute. This field allows the audio stream to be muted or unmuted. It MUST be marked with the Mute semantic field type and conform to the definition of that type.
  • Volume. This field allows control over the volume of the audio source. It MUST be marked with the Volume semantic field type and conform to the definition of that type.
[/INDENT]

Power Management Issues
[INDENT]Any drivers that implements this class MUST also implement Power.[/INDENT]

Multi-Unit Considerations

[INDENT]Though in the bulk of cases a given driver will only control one media source, there are exceptions, such as multi-zone audio systems or multi-zone A/V receivers.

It is RECOMMENDED that the sub-unit names be user definable, as that provides the most self-documenting field names. However they MAY be just assigned based on zone numbers, e.g. Z1, Z2, etc... or some other appropriate scheme, perhaps gotten from the device itself.[/INDENT]


Backdoor Commands/Queries

[INDENT]None are required at this time.[/INDENT]
Dean Roddey
Explorans limites defectum
Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  Class: Security Dean Roddey 34 35,414 01-02-2019, 12:26 PM
Last Post: Dean Roddey
  Class: Weather Dean Roddey 6 6,687 10-11-2018, 11:09 AM
Last Post: Dean Roddey
  Class: Thermostat Dean Roddey 17 26,466 01-29-2016, 10:15 AM
Last Post: Dean Roddey
  Class: SceneCtrl Dean Roddey 20 20,826 03-31-2015, 12:38 PM
Last Post: Dean Roddey
  Class: Irrigation Dean Roddey 8 9,526 01-28-2015, 12:09 PM
Last Post: Dean Roddey
  Class: NowPlaying Dean Roddey 8 9,780 09-23-2014, 02:01 PM
Last Post: Dean Roddey
  Class: Switcher Dean Roddey 9 10,621 08-20-2014, 08:17 AM
Last Post: Dean Roddey
  Class: Projector Dean Roddey 29 27,001 08-11-2014, 08:56 AM
Last Post: Dean Roddey
  Class: Lock Dean Roddey 5 7,189 07-31-2014, 01:24 PM
Last Post: Dean Roddey
  Class: ContactClosure Dean Roddey 7 8,738 07-31-2014, 10:14 AM
Last Post: Dean Roddey

Forum Jump:


Users browsing this thread: 1 Guest(s)