bsp
40
The new trig condition feature is nice, although I’m not 100% sure I am going to use the advanced condition types (x:y and probability) a lot (for clarification: I’ll definitely use FILL and !FILL)
Sequencer features like that are great for creating happy accidents but I prefer recording the output of such a sequencer so I can edit it manually afterwards (not sth you can do with the AR).
Here’s how I like to do fill-ins:
A nice trick on the AR is to use the performance controllers as additional scenes.
In case you did not know: Hold down a performance controller, and while doing that, select e.g. the mute page, then release the pad.
The performance controller is not reset and stays like this permanently until you touch the pad again after you go back to the PERF page.
This alone is quite awesome (I think this was introduced with a firmware update, the original AR could not do this, IIRC)
You can then use this to have up to 12 different fill variations per pattern, that can also be combined (!):
[ol]
[li]Set the triggers for the regular notes[/li]
[li]Set the triggers for the fill notes and plock the volume to 0[/li]
[li]Use a performance controller to pull up the volume of the fill notes to the normal volume (e.g. 100)[/li]
[/ol]
Combine this with aforementioned performance controller “lock” and there you have it!
Much more flexible than the new “FILL” condition type. Does not replace the other condition types, of course.
(note by: It would be incredibly useful if multiple “scenes” could be active at the same time…!)