Re: [misterhouse-users] Remote speech with festival

[Chris B. <ch...@ba...>]

Hi Greg,

>> BTW is the Rooms parameter that MH includes in the tts.speak packet part 
>> of the schema? It's not in the schema that I found here - 
>> http://www.mi4.biz/modules.php?name=Content&pa=showpage&pid=17
>
> I would have thought that the rooms param is much more of an "addressing" 
> concept and therefore should be mapped into the target field (introduced 
> in xAP v1.2) of the xap header (see 
> http://www.xapautomation.org/modules.php?name=xAP_Content&pa=showpage&pid=xapcurrent).

Yes, based on my VERY limited exposure to xAP, it would seem that MH is not 
complying with the tts.speak schema.

This is the transmission that I captured and used as the basis for my 
changes:

<QUOTE>
xap-header
{
v=12
hop=1
uid=FF123400
source=MHOUSE.mh.MisterHouse
class=tts.speak
}
tts.speak
{
Device=
Priority=
Requestor=192.168.0.2
Rooms=all
Say=this is a test
Voice=male
Volume=100
mode=
}
</QUOTE>

and this is the schema from the mi4 website for the tts.speak class:

<QUOTE>
 tts.speak
{
Say=(text to speak) --- mandatory
Volume=(0-100) --- optional
Voice=(TTS Voice to use) --- optional
Device=(Soundcard to use) --- optional
Priority=(Yes/No To stop current playback and play this text) --- optional
filename=(If the is present then instead of playing the sound through the 
sound card it will be recorded into a wav file specified here) --- optional
}
</QUOTE>

As you can see, the Requestor, Rooms and Mode tags that MH includes are not 
in the schema.  I haven't read enough of the spec yet to know if custom tags 
such as these are permissible.

I'm about to go off air for a while as my wife is due (overdue in fact) to 
give birth to our first child.  You obviously seem to know more about xAP 
than me so is there any chance that you could look in to this issue?  The 
addressing issue for identifying the room seems to be the main one at the 
moment.

Regards,
Chris