You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported by jteh on 2014-06-26 07:45
If you perform a say all with the silence synth driver selected (which might be done particularly for automated testing), you'll only get the first 10 lines or so. This is because it doesn't set lastIndex, so say all thinks it has to wait for the synth to catch up, which won't ever happen. We should set lastIndex as if the speech happened instantaneously.
The text was updated successfully, but these errors were encountered:
Comment 1 by James Teh <jamie@... on 2014-06-26 08:02
In [c48e0ed]:
When running say all with the No speech synthesizer selected (useful for automated testing), say all will now complete instead of stopping after the first few lines.
The driver now sets lastIndex as if the speech occurred immediately.
Re #4225.
Comment 4 by James Teh <jamie@... on 2014-07-17 02:16
In [2089790]:
When running say all with the No speech synthesizer selected (useful for automated testing), say all will now complete instead of stopping after the first few lines.
The driver now sets lastIndex as if the speech occurred immediately.
Fixes #4225.
Reported by jteh on 2014-06-26 07:45
If you perform a say all with the silence synth driver selected (which might be done particularly for automated testing), you'll only get the first 10 lines or so. This is because it doesn't set lastIndex, so say all thinks it has to wait for the synth to catch up, which won't ever happen. We should set lastIndex as if the speech happened instantaneously.
The text was updated successfully, but these errors were encountered: