Logic Pro 9 automation keeps sticking

[edurbrow]

I copied a region to a new track. There appears to have been volume automation set on it. What I can't figure out is why when I change the automation it jumps back to the old level even though the automation line in the track appears to stay where I moved it to.

 

[georgelegeriii]

Sounds like you also have automation data in your region as well. Logic, in the most unlogical way, can have automation in the track as well as within a region, and if this happens, you will see the kind of behavior you're mentioning.

 

[Atlas]

Sounds like you also have automation data in your region as well. Logic, in the most unlogical way, can have automation in the track as well as within a region, and if this happens, you will see the kind of behavior you're mentioning.

I think that oddity (automation on track vs region) is reminiscent from the old days of Notator SL, when the P_USER events were introduced to add some automation then. These P_USER events were included in the MIDI stream, among the other MIDI data events but could only be recognized by Notator; when you were normalizing the project (in order to make it into a MIDI file) Notator would translate these P_USERs into corresponding CC events whenever possible to retain as much as possible the original modulation. That "P_USER" approach was to circumvent the MIDI clogging effect of multiple CC use on the ports. Also adding more flexibility and adding programmeable imbedded Notator self auto control. Notator SL was then able to ouput MIDI data stream through 6 distinct ports (96 MIDI channels, which was astounding in those days)... 🙄