I'm a little confused as to why there is different automation in the Midi Editor (automation lane) and Track Automation (key [A]). The track will show Midi Editor automation lane, such as modulation, but can't seem to edit the automation with Track show automation (key [A]). To me there seems to be some inconsistency or I can't figure out the value for each approach.
Any insight is appreciated.
Part (midi) automation will override track automation. Say you have your mod automation set at 100. If you have no automation in the part, you mod will play at 100. If you happen to enter mod automation in the part, it will then play at that value.
This is a great approach IMO. Let's say you have a parameter that gets changed in just a few parts (maybe only one) in the track. You can set you track auto at whatever default you want. As long as you don't change that parameter in the part, it result will be whatever is on the track. You don't have to worry about bringing the parameter back to default at the end of the part.
I don't know why you are having a problem with editing the automation.
So are you saying if I edit a automation lane in the Midi Editor I should be able to also edit in the Track automation [A]?
In the midi editor, that is automation contained in the Part. Your targets are comparatively limited, too.
When you press A and look at the track automation that’s contained on the track, you have a few different targets available as well.
You can have both active, but they are not linked. Completely different things.
Yeah, selecting [A] for track automation is tidy, as the automation sits on the track, but it's not useful for editing then, where having automation reside in separate lanes is easier. As far as choosing which to use, it's largely best to think of automation lanes are for audio tracks, and MIDI or instrument tracks utilize event based automation within the confines of those parts
As pointed out, such MIDI/insyrument changes are limited to events, and not a whole track. When rendering the track to audio (print), any such automation changes to all events on that track will be captured.
There's some practicality for altering either as track automation, or an instrument event lane
For an instrument or MIDI event such as even a volume change where one doesn't want to commit to rendering to audio yet, it's nice to be able to vary volume changes (i.e drums, synth swells) on the instrument part(s) alone. Also great for fading in or out, where there still may be synth or some parameter changes left to do. Towards the end of the song, it's common and most advantageous to final print the MIDI or instrument tracks to audio. Then cover any whole track automation at that time.
Hope that helps clarify some differences.
Tips/tricks: You can copy lane or track changes over to one another. Just be clear where the song pointer resides when copying/pasting.
Latest song releases on Bandcamp -
Latest albums on iTunes
LP's "Amber & Blue", and "Reasonable Approach" available on all major distribution music services.
Simply search "James Conrad Tucker".
All songs copyright. Be safe.