I can’t believe I’ve only just discovered this, but I appear to stumbled on a major limitation… hoping someone can figure out a workaround.
NOTE - post edited to reflect further honing down of the problem.
Record some midi onto an Instrument Track.
Add some automation data - NOTE this is not the same as midi part automation, such as a normal CC1 modwheel, I mean an automation lane of any kind which is synchronous with the clip. You can change the modwheel to record this way by going into CC Automation Setup in the midi menu, and setting Record Destination on Conflict to be “automation” - of course make sure your track is also write enabled. It won’t convert existing midi data to automation, so write fresh data.
Make sure Automation Follows Events is checked in the Edit menu, and view your data in the automation lane.
Move the clip around the timeline - you should see the data moving as you’d expect.
Now create a new midi channel (NOT another instrument channel), and move or copy the midi clip to the new channel.
You’ll see that the automation data stays exactly where it was - it DOESN’T follow the event, as expected.
Moreover, it doesn’t seem possible to copy the data using the edit menu copy / paste. Again, it only moves to elsewhere on the same track.
EDIT - so on further testing, it seems to effect Midi CC automation data only betwen instrument and midi tracks. Regular automation data - such as volume - behaves normally, as does copying between midi tracks, and copying between Instrument tracks. The issue only arises when copying between an instrument and a midi track.
PS - for those who want to write “why don’'t you just use midi part data”, its to do with controlling over EuCon via Quick Controls. That’s the only way to have an Artist Mix (or whatever) control midi CC data.