<< DiscussionsReply

Feature Request: TTS chaining

9 discussion posts
I'm going to say a bad word: VoiceAttack

okay now that I got that of the way, there's a feature in that application I think you should include in yours.

In VoiceAttack's TTS settings, you can chain multiple TTS phrases in one line.
example: Hello, I'm Voicebot.;Hi, Voicebot here;Hey! What's up? I'm Voicebot.

So with that string, when a macro is executed, Voiceattack cycles through each one (in order) and reads only one statement (which is semicolon delimited). You could take this a step further and add a randomization option too (Voiceattack doesn't have that).
Jun 9, 2015 (modified Jun 9, 2015)  • #1
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Interesting! I've added this to our feature request list, and we'll see what we can do to add it in
Jun 9, 2015  • #2
Keith Lammers (BFS)'s profile on WallpaperFusion.com
VoiceBot 2.0 is now available, and you can now enter multple TTS phrases in the TTS action, separated by commas. VoiceBot will choose one randomly each time the macro runs
Jul 13, 2015  • #3
18 discussion posts
As excited as I am that you have implemented this feature, why did it have to be a comma that separated the text. I used commas for strategic pauses in some longer phrases with TTS so that it would sound less robotic. This feature definitely opened up a more interactive function to VoiceBot, but now I need to go through my many TTS macros and replace the commas.

However, before I do replace the commas, consider changing the separator from a comma to a less common punctuation (i.e. ; or : ). If you don't make the change, I'm sure I will have fun changing my commas to something else, but let me know whether you plan on making the change or not.

Just a suggestion.

EDIT: Forget everything I said here, I'll just change my commas to something else. Keep up the good work!
Jul 14, 2015 (modified Jul 14, 2015)  • #4
8 discussion posts
I too changed my commas to dashes (-) and everything is working just fine.
Jul 16, 2015  • #5
Was this helpful?    
<< DiscussionsReply