In the latest beta (2e), the text to speech engine is reading things differently than it used to.  not a bug, just a little annoying.  like when it reads off the wind info on take off, it pronounces "winds" as w-eye-nds.  also reads back flight numbers strangely too.  Not sure if this changed on 2e specifically.  I was a few versions behind before i upgraded.

  Thanks,

  Joe

 

Edited December 28, 20214 yr by mihalich

Pronunciation is different with different voices.  With most Desktop installed voices, Winds is pronounced as "winds a watch".  Whinds is pronounced as "winds are 340 degrees...", like we want.

Polly voices from Amazon, pronounce the two spellings correctly.  So for a version or two, the spellings were changed.  However, as most users are using installed desktop voices, we changed it back to the misspelling, for now.

Dave

Oy...lol.  Thanks for the info.

Joe

 

On 12/28/2021 at 10:13 PM, Dave-Pilot2ATC said:

Pronunciation is different with different voices.  With most Desktop installed voices, Winds is pronounced as "winds a watch".  Whinds is pronounced as "winds are 340 degrees...", like we want.

Polly voices from Amazon, pronounce the two spellings correctly.  So for a version or two, the spellings were changed.  However, as most users are using installed desktop voices, we changed it back to the misspelling, for now.

Dave

Any chance of making this a config option so those of us using Polly can get the correct pronunciation? Since 'whinds' is not going to occur except in place of 'winds', presumably you could do a replace in the string you send to the speech synthesis engine where the text has 'whinds' to correct it back, which would avoid having to limit things to one or the other.

That is possible.  I'll look at doing that.

Dave

This option is now included in 2.6.3.0 Public Beta 1f.  On the Speech tab of Config.

Dave