It seems like you have automation recorded in the region as (RBA), while trying to record in track as (TBA), or vice-versa.Ĭhecking in the region for CC or Fader events, via the Event List editor against the special automation's (dedicated) Event List editor. Yet this data corruption/overwrite still happens when I then switch to Touch, with all input devices off.Īny help appreciated.
#KONTAKT LOGIC PRO X DOWNLOAD MOD#
The Spitfire walkthroughs show perfect results, doing the same procedure - eg with the Albion One Combinations patch, the mod wheel crossfades between, say, winds and tremolo strings. Even when all midi devid=ces are physically turned off.Īnd if I try to write NEW data over old, the values are fighting each other on a tick-by-tck basis, making for a choppy, fragmented end product.ĭoes anyone recognize what's actually happening here, cos I'm very confused (I'm not a Midi boffin, sadly, but I'm not doing anything differently to what I've done for years. Even ONLY switching to Touch mode, the data is being constatntly overwritten. I see the Dynamics slider in the Kontakt instrument moving smoothly, and sounding correct.Īs soon as I try to re-record the dynamics data (switching into Touch or Latch mode) - as I've done before, maybe 10,000 times - there seems to be a struggle going on with the automation data that I just can't figure out. Starting my orchestral template build.ĭoing what I've always done: recording legato melodies whilst controlling dynamics using the mod wheel (or strip, on the S88)įirst pass works just fine. Recently purchased Albion One and Tundra.