First of all, thanks for the update! The new functions sound very interesting : emphasize, speedpitch, etc... unfortunately, they don't work on my PC, so is behaving Play() too
I've tried the examples from the SpeechResponder help documentation, no effect. It is like SSML is disabled somewhere deep in my PC for EDDI. In all cases, when I've tried these functions to test, there was no error message, just no effect at all.

I have Win7, VoiceAttack, Ivona Kimberley voicepack, in EDDI the 'disable phonetic speech' box is UNchecked. The G19 Companion App also uses these SSML tricks, they work there.

First of all, thanks for the update! The new functions sound very interesting : emphasize, speedpitch, etc... unfortunately, they don't work on my PC, so is behaving Play() too
I've tried the examples from the SpeechResponder help documentation, no effect. It is like SSML is disabled somewhere deep in my PC for EDDI. In all cases, when I've tried these functions to test, there was no error message, just no effect at all.

I have Win7, VoiceAttack, Ivona Kimberley voicepack, in EDDI the 'disable phonetic speech' box is UNchecked. The G19 Companion App also uses these SSML tricks, they work there.

These new functions rely on the compliance of your installed voice to documented SSML standards so your mileage may vary. Cereproc voices, for example, are not particularly good with SSML compliance.
If phonetic speech is enabled and you have a compliant voice then you should be able to use these new functions.

What J. Calvert said. The text variable should be named 'Personality', and it should set to a value equal to the actual name of your personality (so the variable 'Personality' contains a value of “Infinity 2.0”) before the plugin is called.

First of all, thanks for the update! The new functions sound very interesting : emphasize, speedpitch, etc... unfortunately, they don't work on my PC, so is behaving Play() too
I've tried the examples from the SpeechResponder help documentation, no effect. It is like SSML is disabled somewhere deep in my PC for EDDI. In all cases, when I've tried these functions to test, there was no error message, just no effect at all.

I have Win7, VoiceAttack, Ivona Kimberley voicepack, in EDDI the 'disable phonetic speech' box is UNchecked. The G19 Companion App also uses these SSML tricks, they work there.

What J. Calvert said. The text variable should be named 'Personality', and it should set to a value equal to the actual name of your personality (so the variable 'Personality' contains a value of “Infinity 2.0”) before the plugin is called.

Umm, are you sure? When I was using Windows 7 Pro I was able to use all 3rd party voices.

It is a buyer decision, but as a developer I can say that the CereProc voices have always required workarounds and still do, because not only do they not meet industry standards (such as support for the PLS+XML lexicon format and the IPA alphabet), but they obstruct supporting industry standards by crapping out when valid data (such as the xml:lang tag) is supplied.

jgm also said as much in the old thread. The Ivona voices are in my experience much more compliant with industry standards.

It is a shame that the text-to-speech market is so lax about meeting documented standards. We will endeavour to support all vendors for as long as is feasible, but make no mistake, if push comes to shove we will focus our limited time on supporting voices that are standards-compliant.

As a developer just trying to maintain a standards-compliant text-to-speech app, my personal opinion of CereProc is that I would like them to DIE IN THE FIRE OF A MILLION SUNS. Just sayin'

I wish I had known about the trouble developers are having trying to get the folks at CereProc to work with everyone before I made a purchase from them.

Yes, I am certain. Since I am running Windows 7 64 my choices are limited and I am forced to look at 3rd party voices. You can download and install Microsoft Speech Server v11 but in order for it to work properly in Windows 7 64, you need to do a couple of simple registry modifications. (Basically change the registry folder path of the TTS tokens in two locations). It has something to do with the way Windows 7 64, (and 2008 Server R2), requires various entries in the Speech Token section of HKLM.

Purchasing a 3rd party voice for $34 is an easy alternative if folks don't want to mess around changing the registry. *EDIT* - I just searched, and although I missed it the other day, end users can also purchase voices from Ivona that work with other SAPI5 applications for $45. http://www.textaloud.com/englishbritish.shtml

But I am just an end user and have no idea (until recently), what SAPi (x) was.
Great work you've done with EDDI 2.x, btw. It really helps with immersion.

First of all, thanks for the update! The new functions sound very interesting : emphasize, speedpitch, etc... unfortunately, they don't work on my PC, so is behaving Play() too
I've tried the examples from the SpeechResponder help documentation, no effect. It is like SSML is disabled somewhere deep in my PC for EDDI. In all cases, when I've tried these functions to test, there was no error message, just no effect at all.

I have Win7, VoiceAttack, Ivona Kimberley voicepack, in EDDI the 'disable phonetic speech' box is UNchecked. The G19 Companion App also uses these SSML tricks, they work there.

With Ivona Amy, I can't detect any change in the speech pattern from the Emphasize() function (thought the others work nicely). But with Microsoft Hazel, I can hear a definite difference when using the Emphasize() function.
In spite of the variation from voice to voice, I'm keen to see what people do with these new speech functions.

I was wondering if the two variable could be for the EngineerBlueprint, and EngineerLevel. I would like to use those to trigger an action in a script i'm writting but this the only way I believe I can detect the engineering status of a weapon. If there is another way I'd love to know I haven't been able to find a way to detect if a module has been engineered or not.

I'm the representative standalone user on the dev team but I'm sure that VoiceAttack users T'kael and Hoodathunk will chime in if I get anything wromg.

It is entirely straightforward: tweaks to your HCS voice pack shouldn't be an issue. If VoiceAttack is in the default location "C:\Program Files (x86)\VoiceAttack" then the installer will do the right thing. Otherwise, please see https://github.com/EDCD/EDDI/wiki/VoiceAttack-Integration.