[eckythump]

Hi all!

Been a while, glad to see this is still quite active and things are moving forward. Congrats on becoming a member of team Kodi, ruuk. I'm glad all your hard work and talent has been officially recognised and rewarded.

I managed to kill my old, updates-disabled, ain't-broke-don't-fix-it raspberry pi and now that I'm trying to use the new version, I've noticed a couple of issues.

My perl speech server no longer works with it. I'm not particularly bothered by this, as it's easy enough to run the python one, too, but probably worth either fixing it, or removing support for it entirely

With the minimal testing I've done, the python one seems to work fine for streaming wav's back to the client, but I can't get the "speak on server" feature working, either from XBMC itself, or attempting to manually interact with the server using python.

ruuk: Can you give me a crash course on how the client communicates with your speech server? Is it just a case of POST'ing engine, voice, rate, text, pitch and volume to either /wav or /say ? Which, if any, of those variables is optional? Using a python shell, I can get the server to throw a wav at me if I post to /wav, but /say does nothing, which no speech eminating from my XP machine that's running the server. The logfile shows:

Code:

speech.server: Mode: WAVOUT
speech.server: [127.0.0.1] SAPI - SAY: one two three
speech.server: Mode: WAVOUT
speech.server: [127.0.0.1] SAPI - WAV: one two three

I'm guessing the mode being WAVOUT for SAY isn't supposed to happen.

Also, does the python speech server save settings at all, or will it happily handle multiple unique clients with unique preferences? I'm hoping the latter, but I'm a little overwhelmed by the code at present as I've not been paying attention and it's been a few months.

Hope everyone is well. Thanks to everyone who's helping, testing and contributing. I'm going to try and be around a bit more again and help out where possible.