Logic Automation Scanning Issue
-
As a longtime Logic user (back when you had to buy CDs to install) this is a new one for me…
After loading up the compiled plugin as AU obviously, as soon as I change the preset, Logic scans (for lack of better word) through all of the available automation parameters.
Anyone know why this could be happening? It seems to be Logic only. Tested AU and VST/VST3 in Ableton, Reaper, and FL Studio. Doesn’t appear to happen in those DAWS.
-
Well that certainly is odd... Is there any way to monitor if MIDI CC is being sent to that track? I don't know if automation parameters can be changed via MIDI CC, so that is just a shot in the dark.
Edit: Hmm but it happens after a preset change. If it was CC, that would likely happen as soon as the plugin opened and reported parameters to automate. I can download this plugin at some point and try it to see if the same thing happens on my end.
-
@ericchesek Good thinking, it does appear to be that midi cc message(s).
After extensive testing, I think it may be a bug or at the very least a less than ideal behavior.
I downloaded some of the various Hise instruments that are linked on the main page of the Hise site as well as even bought a couple commercial releases that were made with hise.
It appears that if in the MIX tab <> Auto Select Automation Parameters <> is on, the behavior in the video posted above happens.
If you have that mode unchecked, it does not happen.