Mapping Discussion

[XORadmin]

Hey! Finally diving into the mappings, but getting stuck on a seemingly easy task while trying to set things up for a live performance.

I want to use an external midi controller to do ratcheting on a modular track when pressing a button on the controller, e.g. to create fills on the fly. So I want to transform a single trigger playing in the pattern into e.g. two or more triggers (time between retriggers tbd).

I figured it might be elegant and flexible to use tables to program custom retrigger behaviors, and I'd love to use the same technique to arpegiate the notes on demand from the controller as well (which would only require using other tables).

MIDI CC messages are properly received in the mapping source, so no issues there. I've set up several tables with different retrig behaviors (firing once mode, and using FX to do the custom retrigger), it is playing as expected when setting the table manually from the pattern.

I am absolutely clueless what the "proper" way of doing the rest would be; I can't find any way to directly set (or overrule) the active table of a track from the mapping screen. As far as I understand, all the TABL destinations are for editing tables using the mapping, which is not what I am trying to do. I've tried using FX overrule (TRCK TRK1 FX1), but can't get anything out of it (what values translate into which FX?). I used static variables as source for testing, but also no useful results from that - I don't hear anything going on other than the pattern playing without any FX.

Do I fundamentally misunderstand how tables are executed maybe? Should I learn how to play the guitar instead?
Still can't figure it out after 2+ hours reading the manual and searching the forum, so any help appreciated

PS: FW 3.0, manual 3.0, and yes I am aware of mapping play/stop 

Go for the guitar!!!

Hehe, no but you are right. There is no direct way currently to trigger tables externally. I have also trouble to think about an indirect way.
However, in the upcoming version there will be a 'start (and stop) table on track' destination for the mapping where you can simply do what you want to do.