kinderale

Maybe this helps? 1) Hit play 2) Manually change the value of the bus feeding into Q-capture (here, it's Bus 1) 3) Activate Input

This is annoying... my solution was to configure each device with a different MIDI channel, and create a macro loop in Keyboard Maestro to switch Midi input to "Any" in each controller assignment. This way i can "reset" Controller assignement's inputs when they get messed up :\

Thanks a lot David!

Out of curiosity, i've inspected the free (but not-unpackable) AppKats Environment Modules with the "recording on track always records any clickable object's interactions" trick. Lots of "unorthodox" Meta messages on the interactive elements! AppKats modules are very instructive, it's a pity their interface gets messed up by the conversion.

Many thanks for the GS script, works beatifully!

Hy everyone! Resurrecting an old thread... Is there any new information about high number (-1-) Faders? It would be interesting to know. No expert here, i'm experimenting. In LPX 10.3 the monitor displays F numbers below 10000. But transforming F numbers greater than 127 lead to odd behaviours. No specific problems or needs here.

Part 2 completed! That's great... i'll look into this example again and possibily learn to rebuild it from the scratch, by hearth. There was something i didn't understand: all my left faders were set with input "--------", yet if a message matches the Out definition of the fader... the fader is set to the new value. Didn't know this, i thought that a fader was controlled by the Input definition only... the Environment never ceases to amaze me. Thanks again Christian, great information here

Part 1 of the tutorial done! Works perfectly! No problems so far, because this is a great tutorial! Wondering when i'll be able to put together a full-fledged pc-like "save/copy/paste/undo" and "factory vs user" preset manager

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

Thanks fuzzfilth! This is a great tutorial for me and for everyone, i'll apply it asap to my Macro and get back when i've learned how to use these useful informations

Hy fuzzfilth! That's a great piece of advice! Future compatibility is a good point. I thought it was easier to use Meta messages, but it seems it's best to whitelist/blacklist different messages IN/OUT rather than keeping everything open to every possibile conversion of different messages. I want to learn preset saving and loading as well! Extra good advice on clickable objects! That's the kind of major errors i want to avoid... I'm also reading swiftkick.com manuals and experimenting, but a good list of do's and don'ts can't hurt

Hy everyone! In the Environment, the default input for faders is CC7 1 (Volume). But sometimes i'll have to process CC 7 too, so i'd like not to mess things up. Is it bad to use the "free" Meta messages as any other midi message (ie. -1- : from 0 to 45 , 46 is not free as it's reserverd for " Assign Alias ", and so on) , to control faders and or other elements, instead of bypassing/converting/transforming CC7? I'm already using the "legit" Meta messages to control transformers, faders, bang faders, etc. I'm planning to build something more complex, and Meta messages seem the perfect candidates for "internal only" cabling inside Macros, or even between Macros as long as i know what i'm doing. Thanks in advance for any suggestion

Thanks, it solved my problem.

That makes me sad! I was planning to include some kind of user interface in a macro... or at least to use an alias assigner to switch between macros (but it doesn't work that way)... this is what i'm working on: at least i can use layers thanks for the answer about alias assigners!

Thank you very much Kamil! I'll let you know if i use this wonderful IRs!