fuzzfilth, you're a lifesaver!
Sorry but i'm still behind, i'll dive into your great Presets Tutorial asap.
About the "clickable objects" issue. From what i see, every single CC gets indeed recorded on selected tracks (in recording mode). This always happens, with objects cabled or uncabled, transformed or filtered afterwards. Trasfoming the output CC into another CC, cabling into Sequencer Input and hitting record just duplicates the CC. FF messages get recorded as well in the same conditions (i.e. FF7 gets recorded as a "region automation" volume). Even "spare" Meta messages create strange "#" symbols in Midi regions (i can't even find them out inside Midi draw). I'm sure you already know all this but i'm a noob!
That's not a great issue for me, as i'm planning to use an external controller (Akai MPK Mini MK2, the reason why i'm learning the Environment, but that's another point). SO, i can live with this, as long as i won't need to directly click a lot of Env. objects during record (I think Vector faders and 14-bit Faders & Vector Faders may be the most sought after clicked objects during recording, as i don't own a 14-bit controller or touchpad).
I see that some swiftkick macros use CC81 and above... i presume that's a way of avoiding commonly used CCs in VIs. So: it's impossible not to get them recorded in that condition, but they won't matter.
"Free" FF messages are so many i'm tempted to use higher FF -1- numbers as "privileged messages inside Macros", but still i'll have to take in account when "All faders gets transformed" and so on. It would be nice to have standardized messages between macros for some modular macros (as long as they're all macros i've done myself). I have little experience so maybe i'm doing this all wrong, let's see in the future!
sorry if this post is dumb