Author |
|
nick7920 Senior Member
Joined: March 04 2008 Location: United States
Online Status: Offline Posts: 193
|
Posted: January 08 2015 at 22:13 | IP Logged
|
|
|
after installing 2.1.5c TTS has stopped working. I checked the
dropdown of voice setting and there is no choice to select.
If I run 2.1.5a from backup on same computer drop down voice
has my choices and works fine.
I am running on XP.
Nick
|
Back to Top |
|
|
dhoward Admin Group
Joined: June 29 2001 Location: United States
Online Status: Offline Posts: 4447
|
Posted: January 08 2015 at 23:20 | IP Logged
|
|
|
Nick,
Based upon this post and the one in the 2.1.5c thread where your webserver settings and the like did not move over, it sounds as if you didnt copy/paste your pwrhome.ini file from your old version (pwrhome.ini and pwrhome.db should both be copied over during an upgrade).
Since 2.1.5a is working for you, shutdown PowerHome and copy the pwrhome.ini file from 2.1.5a and overwrite the one in 2.1.5c. Restart PowerHome and everything should be back to working as it was in 2.1.5a.
Dave.
|
Back to Top |
|
|
nick7920 Senior Member
Joined: March 04 2008 Location: United States
Online Status: Offline Posts: 193
|
Posted: January 08 2015 at 23:20 | IP Logged
|
|
|
its is something to do with with new 2.1.5c pwrhome.ini ,
If copy old 2.1.5a pwrhome.ini - I am checking now where is
the problem - I will update this post once I find out.
Dave - we were both posting at the same time.
you are right I did not copy the old pwrhome.ini when first
installed the 2.1.5c - only thing is the Status window comes
wrong on my old .ini which I am working to copy the setting
now.
Thanks
Nick
Edited by nick7920 - January 08 2015 at 23:24
|
Back to Top |
|
|
dhoward Admin Group
Joined: June 29 2001 Location: United States
Online Status: Offline Posts: 4447
|
Posted: January 08 2015 at 23:23 | IP Logged
|
|
|
Nick,
Looks like we posted at the same time and appears that you've discovered the issue as well.
The pwrhome.ini file contains the TTS settings, webserver settings, and a whole host of other settings and should always be copied over along with the pwrhome.db file during any upgrade.
Dave.
|
Back to Top |
|
|
nick7920 Senior Member
Joined: March 04 2008 Location: United States
Online Status: Offline Posts: 193
|
Posted: January 08 2015 at 23:34 | IP Logged
|
|
|
Thanks
Its working -
Also somehow my old Status window setup did not displayed
correctly so I just copied the default status setting from
new file into my old pwrhome.ini file and its seems to work.
when I updated I copied the .ini for my plugin but missed
this one.
Thanks again.
Nick
|
Back to Top |
|
|
Handman Senior Member
Joined: February 02 2009 Location: United States
Online Status: Offline Posts: 229
|
Posted: January 16 2015 at 12:40 | IP Logged
|
|
|
OK, I must be having a similar issue. The TTS isn't working and is generating the following System Message:
_________________
An error occurred while processing the execution queue. Resetting execution queue and trying again.
*** Error Details ***
Error Number: 35
Object Name: uo_tts_sapi5
Class: uo_tts_sapi5
Routine Name: f_speak
Line: 3
Text: Error calling external object function speak at line 3 in function f_speak of object uo_tts_sapi5.
__________________
This is leading to another issue which is that I have a macro to reboot my PLM by cycling the power with an X10 command to the Insteon/X10 wall switch based on a System Message trigger (because 98% of the System messages in the past were due to PLM comm failures, usually no more than once a week). So, in addition to the TTS issue, is there a way to refine the trigger to System messages based on PLM comm failures?
I did copy the powerhome.db and .ini files when I installed 2.15c, and I recopied the powerhome.ini file just now, but no luck. I must be missing something else.
|
Back to Top |
|
|
nick7920 Senior Member
Joined: March 04 2008 Location: United States
Online Status: Offline Posts: 193
|
Posted: January 16 2015 at 18:14 | IP Logged
|
|
|
Mine is working fine in XP and Win7.
does your TTS work from windows sound test ?
in power home voice drop down can you see your TTS voice choices ?
what OS are you using ?
also check your pwrhome.ini TTS section of new and old.
Nick
|
Back to Top |
|
|
Handman Senior Member
Joined: February 02 2009 Location: United States
Online Status: Offline Posts: 229
|
Posted: January 16 2015 at 22:58 | IP Logged
|
|
|
I am using Win7. TTS does work in Windows if I open the Control Panel and select Ease of Access Center. In the PowerHome Voice drop down there is only one choice, Microsoft Anna. This doesn't seem to me to be the voice that used to be there for the TTS I run in PH, but I may be completely wrong about that!
This is what is displayed in the .ini file for TTS.
[TTS]
TTSCONTROL=11
TTSENGINE=0
TTSSPEED=0
TTSPITCH=0
Perhaps speed and pitch should be set to something besides zero? Also, the "Save Settings to Table" box is unchecked on the Voice dropdown.
Finally, for what it's worth, when I select HELP>ABOUT>OTHER, there is a box that says TTS, but nothing happens when I click on it.
Thanks for your help!
Jeff
|
Back to Top |
|
|
nick7920 Senior Member
Joined: March 04 2008 Location: United States
Online Status: Offline Posts: 193
|
Posted: January 17 2015 at 00:03 | IP Logged
|
|
|
your TTSENGINE=0
mine is set at TTSENGINE=1
TTSCONTROL=10
I would change TTSENGINE=1 and then restart Power home
to see if it makes any difference. (may be later
TTSCONTROL)
when I moved from Xp to win7 I had to install my other
voices, Anna is only default for win 7.
there are other voices but in MS SDK - but in your
case first make sure built in voice works.
Start?Control Panel?Ease of Access?Text to Speech do
you have more choices or just Anna
Nick
Edited by nick7920 - January 17 2015 at 00:12
|
Back to Top |
|
|
Handman Senior Member
Joined: February 02 2009 Location: United States
Online Status: Offline Posts: 229
|
Posted: January 17 2015 at 00:56 | IP Logged
|
|
|
That did it. Changing the TTSENGINE=1 brought MS Anna back to life. Maybe she wasn't working at all in the earlier versions of 2.15 and I didn't notice it, but the system logging caught the issue in 2.15c. Anyway, that resolved it. Thank you, Nick. Cheers.
|
Back to Top |
|
|