Region Automation: Control Change 23 — Logic Pro X keyboard command of the day

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

  Region Automation: Control Change 23

Program MIDI Control Change 23 for the selected region.

Drawing in MIDI CC messages using Region Automation can be far simpler than trying to insert events in the event list or adding them in the Step Editor.

Music Programming 301.

MIDI CC23 — called Control Change in Logic — is an undefined Continuous Controller. CC23 contains the MSB (most significant bits) of the control value. MIDI CC55 contains the LSB (least significant bits) or “fine control” values.

Control Change Messages (Data Bytes)

The following table lists all currently defined Control Change messages and Channel Mode messages, in control number order (adapted from “MIDI by the Numbers” by D. Valenti-Electronic Musician 2/88, and updated by the MIDI Manufacturers Association.) This table is intended as an overview of MIDI, and is by no means complete.

Show automation curves — Logic Pro X

Before you can add automation points to a track’s automation curves, you need to show the automation curves. Automation curves are displayed as colored curves and points on top of audio and MIDI regions across the track, running the length of the project. You can choose whether to view and edit automation across the track (track-based automation) or only within the track’s regions (region-based automation).

⇧ SHIFT – ⌃ CONTROL – ⌥ OPTION – ⌘ COMMAND

Open Step Editor… — Logic Pro X keyboard command of the day

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

  Open Step Editor…

Opens the Step Editor window. Time to make some MIDI.

Step Editor overview — Logic Pro X

The Step Editor is a graphical editor that can be used to create or edit MIDI note and controller data. You can use the Step Editor to view and edit different MIDI event types, shown as vertical beams—or steps—along a timeline within a region.

⇧ SHIFT – ⌃ CONTROL – ⌥ OPTION – ⌘ COMMAND

Open Articulation Editor — Logic Pro X keyboard command of the day

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

  Open Articulation Editor

Articulations are what is used to achieve full, rich sounds from sampled instruments. This is the part that is often not written in the score.

I have a number of instruments where articulation is key — Studio Strings and Studio Horns in Logic, sundry in SampleTank 4, and most instruments in Miroslav Philharmonik.

It’s rather complicated to program. It’s a matter of practice to use switches — memorize each. It’s a matter of taste.

Articulation editing overview — Logic Pro X

Sampled instruments that emulate real instruments often allow you to switch between the unique playing techniques that the real instrument is capable of. These playing techniques are called articulations in Logic Pro. Each articulation will be identified with a unique Articulation ID. For example, a sampled violin instrument might offer articulations to switch between tremolo, pizzicato, and sustained notes, while a sampled horn instrument might include articulations for sustained and staccato notes, trills, and falls.

⇧ SHIFT – ⌃ CONTROL – ⌥ OPTION – ⌘ COMMAND

Region Automation: Program Change — Logic Pro X keyboard command of the day

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

  Region Automation: Program Change

One of the vast array of things that can be automated.

I thought things might get confusing if there were program change events in a region and automation was used to make a program change. No, it’s not. The “automation” is accomplished with Program Change events. If you create an automation point the event is inserted in the region.

The Region Automation commands as found in the Key Commands are not the only things that can be automated. Any MIDI event can be programmed for any channel. It’s a different way of adding events to the MIDI region.

Region-based vs. track-based automation — Logic Pro X

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 only applies 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) the automation data remains tied to the initial point on the track in which it was created. 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.

Show automation curves — Logic Pro X

Before you can add automation points to a track’s automation curves, you need to show the automation curves. Automation curves are displayed as colored curves and points on top of audio and MIDI regions across the track, running the length of the project. You can choose whether to view and edit automation across the track (track-based automation) or only within the track’s regions (region-based automation).

⇧ SHIFT – ⌃ CONTROL – ⌥ OPTION – ⌘ COMMAND

Command    Key Touch Bar
- Views Showing Time Ruler
Region Automation: Volume
Region Automation: Panorama
Region Automation: Balance
Region Automation: Modulation
Region Automation: Breath
Region Automation: Foot Control
Region Automation: Portamento Time
Region Automation: Expression
Region Automation: Sustain Pedal
Region Automation: Control Change 20
Region Automation: Control Change 21
Region Automation: Control Change 22
Region Automation: Control Change 23
Region Automation: Control Change 24
Region Automation: Control Change 25
Region Automation: Control Change 26
Region Automation: Control Change 27
Region Automation: Control Change 28
Region Automation: Control Change 29
Region Automation: Control Change 30
Region Automation: Control Change 31
Region Automation: Control Change 32
Region Automation: Surround Angle
Region Automation: Surround Diversity
Region Automation: Surround LFE
Region Automation: Channel Pressure
Region Automation: Pitch Bend
Region Automation: Program Change
Region Automation: Note Velocity

Export All MIDI Tracks as MIDI File… — Logic Pro X keyboard command of the day

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

  Export All MIDI Tracks as MIDI File…

Why do I care? I make it a habit to create a MIDI track with a single Meta event — Project Select — that can be exported as a MIDI file. If I want to share my project with someone who doesn’t have Logic Pro X all I need to do is export all of the audio files AND export the MIDI track as a MIDI file. The MIDI file contains handy information, e.g., key signature, time signature, tempo setting, and markers!

I can provide comments or instructions in the markers which can be imported into a different tool and be properly located on the timeline.

Only the current marker set is exported to the MIDI file. If there are multiple sets of markers (I do this to provide notes to myself while listening and working, first pass, second pass, etc.) If I want all of the markers I have to make multiple export passes. I should experiment with using separate marker sets per project alternative.

The documentation only says that in some cases you get a Format 1 MIDI file and in other cases you get a Format 0 MIDI file.

If you export a single MIDI region you get a Format 0 MIDI file.

If you export multiple MIDI regions you get a Format 1 MIDI file.

If you ‘Export All MIDI Tracks as MIDI File…’ you get a Format 1 MIDI file.

Format 0 — contains a single MTrk (track) chunk of data.

Format 1 — contains multiple MTrk chunks of data which are intended to be played simultaneously.

Format 2 — contains multiple MTrk chunks of data which are not expected to be played simultaneously. I have never seen a Format 2 file in the wild.

 

Export MIDI regions as standard MIDI files — Logic Pro X

You can export one or more MIDI regions as standard MIDI files, to play in another music app. If your project contains only MIDI regions, you can merge the regions and export the entire project as a MIDI file. Before exporting, you need to perform several steps to prepare the MIDI regions.

⇧ SHIFT – ⌃ CONTROL – ⌥ OPTION – ⌘ COMMAND

MFile 0 1 480
MTrk
0 Meta 0x20 00
0 Meta SeqName "PX330 1*created"
0 Meta InstrName "PX330 1"
0 TimeSig 4/4 24 8
0 KeySig 0 major
0 SMPTE 1 0 0 0 0
0 Tempo 500000
891203 Meta Marker "Peter warmup tune.1"
1016457 Meta Marker "Gary and Andy warmup"
1151607 Meta Marker "Pistol Packin' Mama"
1319239 Meta Marker "Sweet Sue"
1681977 Meta Marker "Don't Fall In Love With Me Darling"
1898240 Meta Marker "Handsome Molly.1"
2148737 Meta Marker "Adobe Hacienda.1"
2353800 Meta Marker "Long Journey Home.1"
2701220 Meta Marker "I Don't Believe I'll Fall In Love Today.1"
2993353 Meta Marker "Big Iron.1"
3247477 Meta Marker "Detour.1"
3497047 Meta Marker "I Think I'll Just Go Away.1"
3774735 Meta Marker "Ridin' My Thumb to Mexico.11"
4007203 Meta Marker "Redwood Hill.11"
4196110 Meta Marker "Hold Watcha Got.1"
4436954 Meta Marker "Ghost Riders in the Sky.1"
4436954 Meta TrkEnd
TrkEnd