learning at the elbow of the internet

Logic Pro X keyboard command of the day. #LogicProX @StudioIntern1

  Set All Tracks to Automation Touch    ⌃⇧⌘T

My normal starting state is to have Read automation turned on. Whatever automation there is gets applied. When mixing the state should be changed to Touch — whatever is there is read until you change a parameter (move a fader) which is in effect until you stop movement at which point automation is again Read.

I would probably use this command at the start of a first pass for a mix letting me alter all of the tracks as I need to. As mixing progresses, or focus on certain sections becomes important it might be better to set all the tracks to Read and only enable Touch on the important tracks.

Choose automation modes — Logic Pro X

Automation modes determine how automation tracks are treated. Automation is either being read or being written. You can independently set the automation mode for each track. You can also trim automation values and record relative automation data.

The X-Touch (I use X-Touch and MCU and Logic Control interchangeably) has an entire section of buttons and modes dedicated to automation. It makes sense since the automation is often applied from a physical controller — so much easier than turning knobs with a mouse…

Mackie Control automation buttons — Control Surfaces Help

Hold down the OPTION button, then press one of the Automation buttons to assign the selected automation mode to all channels. When an automation mode has been assigned to all channels, the corresponding automation mode button LED illuminates whenever you hold down the OPTION button.

⇧ SHIFT – ⌃ CONTROL – ⌥ OPTION – ⌘ COMMAND

Logic Pro X keyboard command of the day. #LogicProX @StudioIntern1

  Open Marker Text

This opens the text window at the bottom of the Marker list. It would be even more fun if it would open the window AND let you start entering text. That is not to be.

For workflow — during an initial listen to a mix it can be very helpful to set markers at points of interest. Distraction of the visual interface is not a good thing.

Create a marker — ⌥’
Now rename the marker — ⇧’
and start typing the note. A carriage return closes off the text. Don’t worry about the display!

For purposes of cross-DAW work you can create a MIDI file that contains *LOTS* of useful information.

Create an external MIDI track (or have one in your template) and insert any *real* MIDI event.

If you now export all MIDI tracks to a MIDI file the MIDI file will contain tempo, key signature, and all of the markers.

Markers overview — Logic Pro X

Markers can help you organize your project, and also act as storage areas for locator positions.

⇧ SHIFT – ⌃ CONTROL – ⌥ OPTION – ⌘ COMMAND

Meta Messages In Logic

In addition to standard MIDI messages, Logic uses two special message types to carry out certain operations and to communicate among its various components. In the Logic Notes column in SOS December 2002 we had a look at Fader messages, which are used for track-based automation. Here we’ll examine Meta messages, which have several functions within Logic. One thing to keep in mind as you read this is that these special message types only travel within Logic — they never venture down the MIDI pipeline to confuse your gear or other MIDI applications.

The Wayback Machine takes us to 2003 to get a description of Meta messages and what the are good for in Logic — even today, sixteen years later…