Issues with Ableton Track Activator and State Example

That's a nasty bug you've found.

It is triggered by the fact that the cc commands are run when you set the cc value in the press commands.

You can bypass the problem by adding the following command anywhere in the script:

[(config){TriggerOnLocalMidiEvents:No}]

mboldisc wrote:

Code:

[(config){TriggerOnLocalMidiEvents:No}]

{@Channel:1}
{@Note:1}
{@On:127}
{@Off:0}
{@StandardDrumsState:0}
{@ElectricDrumsState:1}

[(press){cc:@Channel,@Note,@On}]
[(release){state:@ElectricDrumsState}]
[(press){cc:@Channel,@Note,@Off}]
[(release){state:@StandardDrumsState}]
[(cc:@Channel,@Note,@Off){state:@StandardDrumsState}{nextpress:1}{text:Electric}]
[(cc:@Channel,@Note,@On){state:@ElectricDrumsState}{nextpress:2}{text:Standard}]

I noticed that "state" and "cc:channel" do not work well with variables.  Even with constants inserted, I couldn't get the variables to work well.

I don't know the purpose of the "{@Channel:1}" rows; since they are not in commands, they are ignored by the script engine. If you need default values for variables, you can set them in an Init command:

Code:

[(Init){@Channel:1}{@Note:1}{@On:127}{@Off:0}{@StandardDrumsState:0}{@ElectricDrumsState:1}]

The "{state:@ElectricDrumsState}" action did not work since I didn't expect anyone to use variables to set the state.    I have added this to the next release.

The "(cc:@Channel,@Note,@Off)" events did not work since variables can only be set in events, not referenced, and this will not change. Variable references in events would introduce immense complexity that, besides me getting it all right, requires that you get it all right.    Instead, you need to add multiple commands if you have multiple situations to react to.

When everything else fails, read the manual.  

From the manual:

Please remember the following syntax rules:

• Commands are enclosed in square brackets. [ ]
  
• Events are enclosed in parentheses. ( )
  
• Actions are enclosed in curly brackets. { }