Menu
What's new
By:
Filters

Phantom Automation Data in Logic Using Capture Recording

jbuhler

jbuhler

Senior Member
I'm having an issue when I use Capture Recording in Logic. I'm getting recording of parameters I don't want and I don't know how they are being generated.

Screenshot 2024-02-03 at 9.37.23 AM.png

On this track, the automation for the Kontakt 7 filter and brightness power (these are host automation parameters 0003 and 0004 in the Kontakt instrument) appear whenever I use capture recording. (Other tracks record other spurious automation.) They do not appear when I use the normal midi record (it records just what I expect to be recorded), and I've checked the midi monitor and they are not being generated by any of my midi input devices. I don't know how to track down where these are coming from or more importantly how not to record this.

Does anyone know the cause of this behavior?

Since I rarely record anything other than CCs, is there a way in Logic to filter out everything except particular CCs when doing recording, especially capture recording?
Click to read more...
 
jbuhler said:
This does seem to have been the issue, though what is generating the spurious host automation is still unclear. In any case I now have a way to avoid recording this extraneous automation. Thanks for the help!
Click to expand...
Glad it worked!

Had a thought on the source of the automation: I suspect Logic is automatically mapping some Smart Controls for you. If your Kontakt instrument has parameters with both MIDI CC and host automation bindings, as is usual, then: (1) your MIDI CC input moves a parameter; (2) Kontakt tells Logic the parameter has changed; (3) Logic updates the Smart Control bound to that parameter; (4) the Smart Control emits automation data as if you'd moved it as part of the performance. Logic might also automatically map faders to those Smart Controls if it's set-up to do that.

Unless you set up the Smart Controls on purpose, you can wipe the automatic mappings by opening the Smart Controls panel (press 'B' by default), clicking the circled "i" in the top-left, clicking the circled "..." drop-down menu beside Parameter Mapping, and selecting "Delete all patch mappings."
 
aldous said:
Glad it worked!

Had a thought on the source of the automation: I suspect Logic is automatically mapping some Smart Controls for you. If your Kontakt instrument has parameters with both MIDI CC and host automation bindings, as is usual, then: (1) your MIDI CC input moves a parameter; (2) Kontakt tells Logic the parameter has changed; (3) Logic updates the Smart Control bound to that parameter; (4) the Smart Control emits automation data as if you'd moved it as part of the performance. Logic might also automatically map faders to those Smart Controls if it's set-up to do that.

Unless you set up the Smart Controls on purpose, you can wipe the automatic mappings by opening the Smart Controls panel (press 'B' by default), clicking the circled "i" in the top-left, clicking the circled "..." drop-down menu beside Parameter Mapping, and selecting "Delete all patch mappings."
Click to expand...
Looking at these automatic assignments to the knobs, they don't seem to be what is being picked up by the automation recording. At least one of the items that was being picked up is not among the 8 knobs assigned. In Kontakt libraries, what's picked up is host automation items 003 and 004.

Oddly, now that I've turned the Record Automation with Midi Region off for every instrument, even if I re-engage that option for a particular instrument, it no longer records the spurious automation.

I can't say that I really understand the behavior, but I'm happy that it is no longer recording that automation data.

Thanks for that! I really appreciate it!
 
This started getting buggy for me around 10.7.9 I think. Somewhere around there they added this preference as default behavior which I think was a mistake. Please submit this to Logic feedback! Glad you got it sorted.
 
You must log in or register to reply here.
Top Bottom