First time here? Check out the FAQ!

Can I change PresetNumber in PresetChange with a Capytalk expression?

0 votes

I have had success changing the PresetNumber with a simple VCS generated hotvalue such as !PresetNumber, but I can't seem to get it to change with a Capytalk expression. 

Should this work for example?


asked May 6, 2016 in Capytalk & Smalltalk by cristian-vogel (Master) (8,410 points)
I discovered that this particular expression doesn't work if the !BPM is set to 120. It seems the trigger and the change in PresetNumber are happening simultaneously and seem to cancel each other out.

1 Answer

0 votes

As a workaround, try setting PresetNumber to

!LocalTime floor mod: 6

answered May 6, 2016 by ssc (Savant) (125,820 points)
And you should probably add 1 to that expression (since Preset Number = 0 means "do nothing'").