I've been away from the boards for several months and not worked at all on ttsd for about a year so I'm trying to play catch-up now...

IIRC, there's an option to flite "-l" that will cause it to sit in an infinite loop. I'm not sure if it will work as is with ttsd 1.0a3 or not, but if it does, it would be much better than the current shell script. Ideally, you'd be able to use hijack to launch a command like:

flite -l /usr/local/ttsd stdout

and not have the shell script at all... this would reduce the memory footprint (no bash) and decrease the delay time needed to start flite.

I finally got around to setting up my own web server so I'm not limited to 10M of web space. I've put all three releases on line now: ttsd-1.0a1, ttsd-1.0a2, ttsd-1.0a3.

If memory is still an issue, flite does have an 8KHz sample rate option (as was used in 1.0a1) and if you've got the time recompiling 1.0a3 using 8KHz samples would give a 4MB binary as opposed to the 5.9MB binary that uses 16KHz samples.

I'd be glad to answer questions if I can: [email protected]