This is really a limitation, rather than a bug. The problem occurs with the --stdout option. Writing to a file using the -w <filename> option is OK.
eSpeak doesn't know the length of the speech data when it writes the header at the start of the output stream. Unlike writing to a file, it can't rewind and fill in the length when it's finished. Therefore the length fields in the wav header remain at zero. Should eSpeak omit the wav header completely when writing to stdout? Or should it keep the header which contains the sample rate and format information, so that the output can be automatically fixed by sox? I'm the eSpeak developer, but I only found this bug report by accident. Is there a procedure which passes Debian eSpeak bugs to me, or to the project bug tracker on SourceForge, so that I can see them? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
