KoljaB
commented
2 months ago Is there any way to adjust tokenizer parameters that how the tokenizer(?) divides the sentences?
Yes, please look into the code that performs the sentence splitting. Most of the parameters of this method which customize the sentence splitting are also present in the play and play_async methods of RealtimeTTS.
For example there is the context_size parameter of the play method, which is used to establish context for sentence boundary detection by the tokenizers. It sets the number of characters that are additionally presented to the tokenizer after a sentence boundary like a punctuation. A larger context improves the accuracy of detecting sentence boundaries, lower context would make it faster.
May I ask how sentence-splitting is done when the program is configured to (being~by) feed generator iterators?
When calling play or play_async method RealtimeTTS will start to consume the generator(s) and retrieved textchunks. It will present the accumulated chunks to the tokenizer, which then tries to detect a full sentence from those.
Will the tokenizer be able to split the two sentences?
Yes it should, at least that's its job :)
If so, is there any way to adjust the tokenizer for its way to divide the sentences?
Not more than in these parameters.
Simply put, I would want to know if there is a way to make stream output faster when feeding the engine with generator iterators.
fast_sentence_fragment parameter "overwrites" the tokenizers by also searching for delimiters like "," or "-" which would not mark a full sentence but a "somewhat synthesizable fragment". So if you use these you can speed up TTS generation in the first retrieved sentence, which can be quite crucial for generating a really fast answer. Gives up a bit on synthesis quality of course. If you don't mind, you can also finetune all other parameters to "fast" settings. Like setting context_size to 2 instead of default 12. Or minimum_sentence_length to 3 or 4 instead of 10.
FivespeedDoc
Is there any way to adjust tokenizer parameters that how the tokenizer(?) divides the sentences? May I ask how sentence-splitting is done when the program is configured to (being~by) feed generator iterators?
For example, if I feed this string(or whatever you call it) word by word(punctuation counts as one word).
"Hello, can you tell me how the sentence splitting works? I want to know the performance difference between ntlk and stanza."
Will the tokenizer be able to split the two sentences? If so, is there any way to adjust the tokenizer for its way to divide the sentences? Or perhaps it just waits until the entire string is received and calls the TTS engine then.
I am using language which is not English, but I noticed little difference between tokenizer as "nltk" or "stanza"
Simply put, I would want to know if there is a way to make stream output faster when feeding the engine with generator iterators.
Really appreciate if you could help! Thanks