couple of things. first, i tried to mute a track using:
MuteTracks:
found that in the manual but it throws an error:
Your batch command of MuteTracks was not recognized.
same for ‘unmutetracks.’
i did find that MuteAllTracks and UnmuteAllTracks both worked, as did TrackMute. problem with TrackMute, though, is that it is a toggle and requires focus to be set. i was hoping for a simple command to set the state either on or off.
second, somewhere in the manual i found a note that i could comment in macros with the # symbol but that also threw up an error.
editing my post before i even am posting it, here. found that i can use ‘set track,’ turning all options off except the ‘mute’ checkboxes. still new enough at this that i’m confused as to why i have to check two (both) boxes to have the mute apply. it seems that selecting both checkboxes selects ‘mute’ and selecting only the left checkbox selects ‘unmute.’ confusing but seems to work.
as for commenting with #, seems i can’t use it to comment out a command as the command is read even if it follows the # symbol. seems to work for making notes but not for commenting out test commands.
thanks for all the info, steve. yeah, funnily enough, hahaha, that detailed description of checkboxes was also in response to me. obviously i remain confused. it does seem a pretty klunky way of handling things. i like the direct text entry for now. looks like at least one other user was also confused about the checkboxes too. wish there was a label or something like ‘engage’ or ‘active’ over one column of the boxes and ‘value’ over the other. might make things a little more transparent.
unfortunately, for now, i have to stick with 2.3.3 as i’m helping someone figure out how to do some of these things in audacity and this is the version she’s on. need to maintain as much compatibility as i can.