Since 2.0.6 has only been out for about three weeks do you think you installed it shortly before your problems appeared? If you believe you installed it before your problems began*, did you accept the one-time offer to reset Audacity’s preferences during the install process? Have you tried resetting/initializing Audacity’s preferences since the problem appeared? You may find directions for doing so here:
FYI, when pasting code into this BBS, before doing so click the button just above the text input field which is labeled Code. This will insert a formatting on/off pair:
and set the typing insert point between the pair – paste your code, click after the final close square bracket, press return/enter and continue typing. In this instance, since you had three different scripts you would want to do this three times so that each script was in its own code block.
I know these scripts were working for a long time; however, I note at least a couple of typos. I would also combined the script which opens Audacity and the script which starts it recording.
The first script, if you’re going to use 3 scripts, does not need the “wait for the window to activate” command as there is nothing else for the script to do. If you do use separate Run & Record scripts you stand the chance of running the Record script before Audacity is fully launched and ready to record.
In the second (Record) script
send ("^["); Send Return-to-beginning-of-track command
send ("^u"); Send <ctl>U to mute all tracks
Send("!^+rr"); to start new track recording
The “return to beginning of track” command should be unnecessary as there will be no track at this time; likewise, the mute command is also unnecessary for the same reason. As I pointed out before the “start recording” command has a typo in that there are two of the letter r.
In the third (Stop) script
looks suspicious in light of:
Stop as <ALT + CTRL + SHIFT + S>
if in fact your Stop Recording is not:
the exclamation point (!) means ALT, the carat (^) means CTRL and the plus sign (+) means SHIFT
the trailing s is being sent sequentially so what the program is seeing is:
which is not valid in Audacity (as a single command – it will be interpreted as two commands).
*I’ll go out on a limb here and make a wild guess as to what is really going wrong… When it was working you were running a version of Audacity which did not display a splash screen (pre-2.0.6). At startup 2.0.6 briefly brings up a small window whose name is “Audacity is starting up…”. AutoIT3, when asked to activate (or wait for the activation of) a window called “Audacity”, will happily accept either “Audacity” or “Audacity is starting up…”. So, if the splash screen is active when your second script starts to run the splash screen window gobbles up all the commands including the Record command. The only way you can prove this would be to compile a custom version of 2.0.6 changing the title of one of the windows so that the first word of each was unique. Alternately, you could reinstall 2.0.5 and see if that resolves the issue; if so, while not a proof, it would be a strong indication that this is the problem. I vaguely recall that you have some background as a programmer; I would be inclined to recompile with unique titles if it were me.