Re: Whole House Audio schema

[Stuart Poulton]

Mark,

All seems to make sense to me......

Stuart


----- Original Message -----
From: "mark_harrison_uk2" <<a
href="/group/xap_automation/post?postID=Wa3BDax04wGXXyYnpIKvOGjZ-poZUgBJ8S-hhBbJDXNpW2bV_uR7i_WOreT48saprwuSM75vIUyUaZ5eHZo">mph@a...</a>>
To: <<a
href="/group/xap_automation/post?postID=hkZTRgqet6dzqAGTftA-e1DLkdDe96vGK0HtM472v7rcF0znJQBPcJNxEbv__O7LMg4R2a6SvBbP8gW9LgvONVW8bDejTVXd">xap_automation@xxxxxxx</a>>
Sent: Sunday, February 08, 2004 10:05 AM
Subject: [xap_automation] Whole House Audio schema


Can I propose two changes to the schema:




1: The long name




Current name




- "xAP Schema for MP3 Whole House Audio v2.2"




Proposed name




- "xAP Schema for Audio Control v2.3"




Justifaction: It applies perfectly to transport control of CDs, and
I'd like to implement that, hence the reference to MP3s is
inappropriate. Secondly, the "Whole House" stuff means that we
should
talk about source/destination mapping, which currently isn't there,
hence call it audio for the time being.




2: Extension to audio.audio to include new class




At present, xap-audio.audio contains two allowable blocks:




- audio.mute


- audio.mixer




I would like to add a third




- audio.sourceselect




{


AVSource= <name>


}




<name> is descriptive and configured by the installer, who is also
responsible for creating any mapping between xAP names and
audio-hardware-specific names.




Any comments?




Mark