Hello,
I would like to toggle the leslie control every key press from a controller (Note on ?).
At the moment I can only do one state, either toggle on or toggle off.
What’s the best way to do this ?
Thanks !
Frederic
Wow! I was just composing a question about finding a better way to do this exact thing. What I’m doing now is using a MIDI Filter Sticky Note then binding the note to a CC:
- Input from MIDI (Note or on/off CC)
- If Midi, map to note
- Follow with MIDI Sticky Note Filter (this will be the “toggler”)
- Map note to desired CC then route to MIDI as needed
The method takes a midi route with Filters. Surely, with all the binding expressions/conditions/modifiers, there is a more eloquent way to accomplish this with a single binding in each song’s binding pane.
This works but it is parameter specific and not a MIDI cc message. To do it it with the common CC1 message do this
1 Like
Well… $h|+. That’s pretty slick, @dave_dore. I looked in the mirror and said, “How could you not know this?”
I’ve been playing with the new toy (for me), and it appears the input action (in your case C36) always bumps the Mapping to the second number in the sequence, even if the sequence is more than 2 numbers (I’m running up to five for S&G). Seems to scroll through the list starting after the first comma and loop to first number is list, infinitum. And, the sequence values do not need to be in any particular order (ascending/descending).
For me, the issues with the toggle always was at the start of a song to ensure that the condition was proper. Say, for instance, I want CC11 to be 127 at the start of the song then toggle between 0 and 127 with each C36 note press. I would “On Song Load” force CC11 to 127, then use the Mapping (Command to values) at 127,0. That way, the first C36 note would bind to the second number in the sequence (0), then loop.
Thanks again. I’ll start working on substituting this quick binding for the filters in my songs and see what happens.
UPDATE: I was playing with this concept and now the sequence is starting at the FIRST number in the sequence. I don’t want to wipe out what I just wrote fifteen minutes ago, but something changed. I’m absolutely positive when the song was opened and C36 was pressed, the SECOND number in the sequence was activated. Now it’s the first number in the sequence.
So which it is? Open the song, hit the C36 note, when what is results? 1st or 2nd value in the sequence of Mapping Values?
Here is what I’m finding out.
-
In @dave_dore example of mapping to a CC in a list, pressing the C36 Note starts on the SECOND value in the list, If I press C48 (my example below), CC11 becomes a 10.
-
When mapping to a VST parameter, pressing the C36 Note starts on the FIRST value in the list. Press C48 and Rise time is 0, note 0.2.
That is very confusing…
Thanks a lot for these tips !!
I will be out a few days, with no possibility to test these infos.
Regards
When mapping to VST parameter values, Cantabile can look at the current state of that value and choose the mapping value accordingly. So if the VST parameter is currently at 0.2, Cantabile can identify that, and automatically step to the next value (0.4).
When mapping to CC values, there is no reference to a “current value” outside the binding, so the binding should keep its own state of the position in the sequence. This should start with the first value and iterate through them in sequence.
If your first example (CC values output) starts with the second value, this would not be according to spec - maybe something is triggering that binding a first time without you knowing it?
Thank you for your comments @Torsten.
In my case, MG-1 VSTi is saved in song with Rise Time at 0.4. Refer to the following binding.
Close and reopen song. If C3 is pressed, the Rise Time moves to 0.0, not up to 0.6.
If MG-1 is saving with Rise Time at 0.0, close/open again, press C3, Rise Time moves to 0.2.
Good, bad, or indifferent, this behavior is very repeatable.
Hmm, that’s not quite what it is supposed to do - possible rounding error issues (Cantabile not recognizing the float representation of 0.4)?
That’s one for @brad, I guess…
I was thinking rounding issues, too. I just happy to have learned this method! It’s much cleaner than what I was doing.
Thanks for reporting - fixed for the next build.