2014-04-16, 01:17
Yeah, its definitely slow, LOL.
(2014-04-15, 23:57)ruuk Wrote: Just FYI, I installed Strawberry Perl and that was all I needed to run the script.
I'm running XP in a virtual machine and Cygwin was a bit larger than I wanted
(2014-04-16, 07:57)VIJO Wrote: Hey Ruuk, If possible, How about adding a toggle to the keymap to enable/disable TTS. Say F12 or something like that. You know for the rare occasion my poor sighted friends want to use it without me knowing what they are doing, lol.
(2014-04-16, 05:58)eckythump Wrote: When the new version started, it then was trying to use 127.0.0.1 and that caused things to really break, to the point that xbmc would completely crash and restart.I tried it just now with the IP set to 127.0.0.1. I can hammer away changing controls. I get the same error, but I can't get XBMC to crash on me. What platform is this happening on?
The last line in the xbmc log file when it died was:
11:53:36 T:2809132112 NOTICE: service.xbmc.tts: ERROR: SJHttsdTTSBackend: wav.write - <urlopen error [Errno 111] Connection refused>
(2014-04-16, 05:58)eckythump Wrote: I edited that error output to include self.httphost just to confirm where it was trying to connect, and then rolled back to the old version, changed to espeak, then upgrade again, changed back to ttsd and configured it properly. After that it was happy.Well, I've been thinking we need some sort of fallback mechanism, and perhaps a dialog that confirms that you hear speech after a backend change and reverts if you don't confirm.
If we trap that exception better, how easy would it be to fall back to the highest priority backend that's available?
(2014-04-16, 05:58)eckythump Wrote: I don't know enough about xbmc to know why that's making it barf so spectacularly, but hopefully it's easily fixed.I can't duplicate this either. It works fine for me. Hmmm.....
The only other issue I noticed, and this is very minor, is that when I changed voices, it didn't switch when I went OK. It did take affect when I rebooted, though. I didn't try any other things to see if I could get it to take.
(2014-04-16, 20:39)ruuk Wrote: eckythump: There is a small bug in the Perl server. If you pass the text '0' it triggers a 403 error. Typing a 0 in a keyboard dialog will cause this. I suspect that this is being interpreted as a number and and evaluating false on the test for $text. It's been a while since I've done much coding in Perl so this is just a guess.
if ($voice and defined($rate) and $text) {
if ($voice and defined($rate) and $text ne '') {