desmond wrote:If you're in plugin edit mode here and are controlling the dynamics parameter, then you are generating automation as the plugin parameter changes. In this case, the "Dynamics" parameter is exposed to host automation - and that is what you are using.
desmond wrote:*However*, the "Dynamics" control *also* responds to normal MIDI - the mod wheel. So - as an alternative method - you can play your eg string parts and use the mod wheel to control dynamics instead. In this case, the CC#1 data is controlling the Dynamics slider, and is recorded in MIDI regions in the normal way. This is straight MIDI control of a plugin parameter, not automation. When you move the mod wheel in this case, and the Dynamics slider in Kontakt is changing, Kontakt/Albion *is not* generating automation events (because otherwise, you could end up with two sets of conflicting data trying to control the same parameter).
Why could you have two sets? You mean if you were to use the mod wheel and move the slider with the mouse simultaneously?
desmond wrote:(Now - you could, if you want to, use Logic's controller assignments to directly learn MIDI CC#1 to the Albion Dynamics parameter. In this case, as we've seen previously, the CC#1 is blocked from reaching the sequencer, and instead controls the Dynamics parameter directly, and thus generates automation events.)
I think this is the bit I am missing.
desmond wrote:If you use Logic's controller assignments to *learn* the incoming MIDI messages from your TouchOSC controller, and map to the Dynamics parameter from Kontakt, the sliders will now be directly manipulating the Dynamics parameter, and thus Kontakt will be generating automation events.
OK now I know what to look for, I've pinpointed page 1109 of the Logic 10.5 manual, which describes assigning a controller in Easy view, and hey presto, I can now write the automation with my iPad in the way I had originally assumed it would work (but now have a handle on why it doesn't). :bouncy:
(Although the manual says Easy view, it actually opened for me in the scary looking Expert view, but I don't care because it still worked).
Thanks so much for all this. Looking forward to the details of Region automation! :ugeek: