There are more details and pictures in this thread, here. Is there a way to globally disable host automation entirely since I'm not using it? Or is there another solution to this issue? To confirm this, when I load instruments that don't populate host automation automatically I don't have this problem. However, nearly every Spitfire instrument automatically populates the Host Automation parameters upon loading, so any time I use these instruments and record Midi CC data for any of those mapped parameters (which includes dynamics, expression, and volume, I can't use touch mode for track automation on those tracks.

This is seemingly happening because, the dynamics (in this case) is assigned to a Host Automation parameter, as when I manually delete that Host Automation assignment in Kontakt, this solves the problem. What this means is that I essentially can't use touch mode to perform track automation data on any track that has Midi CC data for these instruments (which ends up being a lot!) without it interrupting the automation I'm trying to write with this information it's redrawing on its own. However, if I switch that track on which I just recorded to 'Track' automation mode, put it into touch (or latch, or write) mode, and press play, as the playbar passes over the CC1 midi data, it begins writing 'Track' automation data for the dynamics of that kontakt instrument. For example, I can just play one chord, and move the mod wheel (CC1) to record dynamics info. This is all being recorded in Logic's 'Region' automation lane. I am using a standard midi controller, like my keyboard controller, to play note information and write basic MIDI CC data while I play. This seems to cause some issues for me in Logic.

Whenever I load a Spitfire instrument, which is often, it automatically populates the Host Automation section with assignments. I'm using Logic 10.4.3 and Kontakt 5.8.1.

Automation logic pro x