You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi. Greetings. I just update the IBMTTS to 19.10B2. I notest the bug of the varient setting still exists. For example, I'm now using read. When I change the varient to shelly from the speech setting ring, save the configuration and restart the NVDA, it will back to the read varient but the setting still focus on shelly. If I want it permanent to use shelly or other varient, I must configure it from the speech settings by pressing control+NVDA+v. Another example, now, I already change to shelly from the speech settings. I save configuration and restart NVDA. It now will continue use shelly. Now, I change to bobby from the speech setting ring, save configuration and restart NVDA. After NVDA has restarted, it will use the shelly voice but the setting still focus on bobby. For the rate boost bug is solve. Hope this can be fix. Thanks in advance.
Loh Boon Keat
The text was updated successfully, but these errors were encountered:
Hi. Greetings. I just update the IBMTTS to 19.10B2. I notest the bug of the varient setting still exists. For example, I'm now using read. When I change the varient to shelly from the speech setting ring, save the configuration and restart the NVDA, it will back to the read varient but the setting still focus on shelly. If I want it permanent to use shelly or other varient, I must configure it from the speech settings by pressing control+NVDA+v. Another example, now, I already change to shelly from the speech settings. I save configuration and restart NVDA. It now will continue use shelly. Now, I change to bobby from the speech setting ring, save configuration and restart NVDA. After NVDA has restarted, it will use the shelly voice but the setting still focus on bobby. For the rate boost bug is solve. Hope this can be fix. Thanks in advance.
Loh Boon Keat
The text was updated successfully, but these errors were encountered: