Set Nudge Value to 1/2 Triplet (1/3) — Logic Pro keyboard command of the day

  Set Nudge Value to 1/2 Triplet (1/3)

Sets the Nudge Value to one half of a triplet. By my reckoning that would be the full value of one of the notes — quarter note triplet — one half is a full quarter note. I’m not sure that I understand when I might want to nudge things like this, unless I was moving something that wasn’t an actual part of the triplet. Hmmm.

Move regions in the Logic Pro Tracks area — Apple Support

You can nudge regions (move them in small increments) left or right using key commands. To nudge regions, you first set the nudge value, then move selected regions by this value. Alternatively, you can nudge regions by a set value.

Copy to Live Loops ⌘ — Logic Pro keyboard command of the day

  Copy to Live Loops    ⌘

Copy the selection (regions) to Live Loops cells.

I need to investigate using Live Loops. It is such a different way to use Logic than as a simple recorder or arranger.

Work with Live Loops cells in Logic Pro — Apple Support

Using the Copy to Live Loops key command in Logic Pro, you can copy various combinations of regions to new scenes, depending on what you have selected in the Tracks area. This is especially useful for populating a Live Loops grid in an existing project containing many different regions, sections, or markers. You can copy any of the following to Live Loops:

Automation: Toggle Track/Region — Logic Pro keyboard command of the day

  Automation: Toggle Track/Region

Switch the automation lane view(s) between Track automation and Region automation.

I believe I am ready (finally) to start automating some of my mixes. I think that using region automation will help me focus on the goals of the particular automation.

Track-based vs. region-based automation in Logic Pro — Apple Support

Logic Pro offers two types of automation: track-based automation and region-based automation. Track-based automation can be applied to the entire track, from the beginning to the end of your project. Region-based automation applies only to the specific region the automation parameters are connected to. With track-based automation, if you re-record, move, or copy regions (either to another point on the same track or to another track entirely) the automation data remains tied to the initial point on the track in which it was created. However, with region-based automation, if you re-record the region, the automation is lost; if you move or copy the region (either to another point on the same track, or to another track) the automation remains with the region. Region-based automation is particularly useful when you are automating instrument parameters.