The script you’re using just uses Festival’s standard textfile processing – if you look at the code in the “synthAndSaveSentences.scm” scheme code file, you’ll see it just calls “(tts_file text)”. In that text file processing, line breaks have no special meaning, and sentences can span multiple lines. I guess in the example you give above Festival is interpreting “I.” as an abbreviation, and not the end of a sentence. That’s why all those lines get concatenated into a single sentence – this is not a bug, this is how festival is interpreting your text file.

du n no I.
that’s gone.
and somehow allegedly didn’t see anything I I.
you genuinely saw nothing.
like when I.
it’s a picture.

You get this output from Festival, where Lines 1&2, Lines 3&4, and Lines 5&6 are merged into a single utterance:

utt00000001 <{(1 d uu )}{(1 e n )}{(1 n ou )}{(1 ai )}{(1 dh a t s )}{(1 g o n )}> _BB
utt00000002 <{(1 a n d )}{(1 s uh m )(3 h ow )}{(0 @ )(1 l e jh )(0 i d )(0 l iy )}{(1 d i d )(0 n! t )}{(1 s ii )}{(1 e )(0 n i )(0 th i ng )}{(1 ai )}{(1 ai )}{(1 y uu )}{(1 jh e )(0 n y uw )(0 i n )(0 l iy )}{(1 s oo )}{(1 n uh )(0 th i ng )}> _BB
utt00000003 <{(1 l ai k )}{(1 w e n )}{(1 ai )}{(1 i t s )}{(1 ei )}{(1 p i k )(0 ch @ )}> _BB

It looks like you have large files elsewhere. Send me a direct email or Teams message with the output of the du commands in this post above.

(Also, try to avoid screenshots – they are not searchable for others using the forums – it’s better to copy-paste the text into a post.)

This post, and the thread below it, will help you learn how to do that.

Look for an error message from HRest – if it is failing to create any models, it should report an error.

Remember to always wipe all models (from hmm0 and hmm1) before every experiment: this will help you catch errors.

PROTO=5state
set -x

done