[ruuk]

First off, sorry for taking so long to reply. I've been extraordinarily busy as of late. I also have the bad tendency when I'm busy of waiting to post a reply until I have more time when if I can't reply quickly, and then forgetting to do it later.

Hi,

I've tried the speech.server again, and sadly now it doesn't work for me at all. When I post to /say I get nothing, and I'm not even seeing anything logged, and when I post to /wav I get a 500 internal server error.

I'm using XP and python 2.7. Is there anything I should check? The server has definitely worked in the past (though I never used the speak-on-server option).

In the meantime, if you can have a looksee and try to ascertain why the perl server no longer works, that'd be good. Also, the speed setting is ghosted out when the perl server is selected in the last few newish releases I've tried. Be good if you can fix that, too, if it's still an issue.

I'll have to give it a go on my XP VM.

Thanks again for all your work. I've just made a small donation to the project.

Thank you, that's very kind of you

Do you have a TODO list? If you're able to post it somewhere, I'd like to try and do my bit to clear some of the entries from it for you. I may also be able to enlist the help of others who wouldn't have much interest in the project, but would probably enjoy the challenges it offers.

The changelog has a TODO and there is also a file in the addon todo.txt which mostly has notes on Traker1001's suggestions. Otherwise, I've just been finding or hearing about what isn't speaking and fixing those as I find them.

Haven't had a chance to do any debugging on the python speech server, but I looked into the issues with the perl server.

The issue related to the perl server not replying to invalid URL's with a 404, but instead it was sending a helper form with a 200 response code. I've made it now return a 404 and commited this change to git, so now it works again.

One issue I did find, though, is that the settings allowed me to set the speed to > 10. The perl server accepts speed rates between -10 and 10 and if you go outside of that, it's not very forgiving.

If you're able to add in a constraint to that range when perlServer is True, that'd probably be a good idea.

I'll do that when I get a chance.