Logic Pro User Guide
- Welcome
-
- What’s new in Logic Pro for Mac 10.7.8
- What’s new in Logic Pro for Mac 10.7.5
- What’s new in Logic Pro 10.7.3
- What’s new in Logic Pro 10.7
- What’s new in Logic Pro 10.6
- What’s new in Logic Pro 10.5
- What’s new in Logic Pro 10.4
- What’s new in Logic Pro 10.3
- What’s new in Logic Pro 10.2
- What’s new in Logic Pro 10.0
-
- What is Logic Pro for Mac?
- Logic Pro project basics
- Use menu commands and key commands
- Use the complete set of Logic Pro features
- Undo and redo edits
- Manage Logic Pro content
- How to get help
-
- Projects overview
- Create projects
- Open projects
- Save projects
- Delete projects
-
- Play a project
- Set the playhead position
- Control playback with the transport buttons
- Use transport shortcut menus
- Use transport key commands
- Customize the control bar
- Change the LCD display mode in Logic Pro for Mac
- Monitor and reset MIDI events
- Use the cycle area
- Use the Chase Events function
- Use Apple Remote to control Logic Pro
- Use Logic Remote to control Logic Pro projects
- Preview projects in the Finder
- Close projects
- View project information
-
- Overview
-
- Before recording software instruments
- Play software instruments
- Record software instruments
- Record additional software instrument takes
- Overdub software instrument recordings
- Spot erase software instrument recordings
- Use Note Repeat
- Replace software instrument recordings
- Record to multiple software instrument tracks
- Record multiple MIDI devices to multiple tracks
- Record software instruments and audio simultaneously
- Use step input recording techniques
- Record MIDI messages from another music app
- Use the metronome
-
- Arranging overview
-
- Regions overview
- Select regions
- Select parts of regions
- Cut, copy, and paste regions
- Move regions
- Add or remove gaps
- Delay region playback
- Loop regions
- Repeat regions
- Resize regions
- Mute and solo regions
- Time stretch regions
- Reverse audio regions
- Split regions
- Demix MIDI regions
- Join regions
- Create regions in the Tracks area
- Change the gain of audio regions in the Tracks area in Logic Pro for Mac
- Normalize audio regions in the Tracks area
- Create aliases of MIDI regions
- Convert repeated MIDI regions to loops
- Change the color of regions
- Convert audio regions to samples for a sampler instrument
- Rename regions
- Delete regions
- Create groove templates
-
- Overview
-
- Add notes
- Select notes
- Snap items to the grid
- Move notes
- Copy notes
- Change the pitch of notes
- Resize notes
- Edit note velocity
- Quantize the timing of notes
- Quantize the pitch of notes
- Change note articulations
- Lock the position of events
- Mute notes
- Change note color
- View note labels
- Delete notes
- Time stretch notes
- View multiple MIDI regions
- Split chords
- Automation/MIDI area in the Piano Roll Editor
- Open other editors
-
- Logic Pro for Mac advanced editors overview
-
- Audio File Editor overview
- Play audio files in the Audio File Editor
- Navigate audio files in the Audio File Editor
-
- Audio File Editor edit commands
- Edit audio files with transient markers
- Use the Audio File Editor Pencil tool
- Trim or silence audio files
- Remove DC offset
- Set audio file levels
- Normalize audio files
- Fade audio files
- Reverse audio and invert phase
- Audio File Editor Loop commands
- Undo Audio File Editor edits
- Backup audio files
- Use an external sample editor
-
- Mixing overview
- Set channel strip input formats
- Set channel strip pan or balance positions
- Mute and solo channel strips
-
- Plug-ins overview
- Add, remove, move, and copy plug-ins
- Insert a plug-in on a track using drag and drop
- Activate plug-ins on inactive channels
- Use the Channel EQ
- Work in the plug-in window
- Work with plug-in settings
- Work with plug-in latencies
- Work with Audio Units plug-ins in Logic Pro for Mac
- Support for ARA 2 compatible plug-ins
- Use MPE with software instruments
- Use the Plug-in Manager
- Work with channel strip settings
- Surround panning
- Use the I/O Labels window
- Undo and redo Mixer and plug-in adjustments
-
- Smart Controls overview
- Show Smart Controls for master effects
- Choose a Smart Control layout
- Automatic MIDI controller assignment
- Map screen controls automatically
- Map screen controls
- Edit mapping parameters
- Use parameter mapping graphs
- Open the plug-in window for a screen control
- Rename a screen control
- Use articulation IDs to change articulations
- Assign hardware controls to screen controls
- Compare Smart Control edits with saved settings
- Use the Arpeggiator
- Automate screen control movements
-
- Live Loops overview
- Start and stop cells
- Work with Live Loops cells
- Change loop settings for cells
- How the Live Loops grid and Tracks area interact
- Edit cells
- Edit scenes
- Work in the Cell Editor
- Bounce cells
- Record a Live Loops performance
- Change Live Loops grid settings
- Control Live Loops with other devices
-
- Global changes overview
-
- Tempo overview
-
- Smart Tempo overview
- Use free tempo recording
- Choose the Project Tempo mode
- Choose the Flex & Follow setting
- Use Smart Tempo with multitrack audio
- Work in the Smart Tempo Editor
- Improve the tempo analysis using hints
- Correct tempo analysis results using beat markers
- Protect Smart Tempo edits by locking a range
- Match audio recordings to the project tempo
- Match the tempo to an audio region
- Use audio file tempo information
- Record tempo changes
- Use the Tempo Interpreter
- Use the tempo fader
- Control project volume
-
- Overview
- Add notes
-
- Part box overview
- View score symbols
- Select score symbols
- Add notes and rests
- Add notes and symbols to multiple regions
- Add key and time signature changes
- Change the clef sign
- Add dynamic marks, slurs, and crescendi
- Change note heads
- Add symbols to notes
- Add trills, ornaments, and tremolo symbols
- Add sustain pedal markings
- Add chord symbols
- Add chord grids and tablature symbols
- Add bar lines, repeats, and coda signs
- Add page and line break symbols
-
- Select notes
- Move and copy notes
- Change note pitch, duration, and velocity
- Change note articulations
- Quantize the timing of notes
- Restrict note input to the current key
- Control how ties are displayed
- Add and edit tuplets
- Override display quantization using tuplets
- Add grace notes and independent notes
- Delete notes
- Use automation in the Score Editor
-
- Staff styles overview
- Assign staff styles to tracks
- Staff Style window
- Create and duplicate staff styles
- Edit staff styles
- Edit staff, voice, and assign parameters
- Add and delete staffs or voices in the Staff Style window in Logic Pro for Mac
- Copy staffs or voices in the Staff Style window in Logic Pro for Mac
- Copy staff styles between projects
- Delete staff styles
- Assign notes to voices and staffs
- Display polyphonic parts on separate staffs
- Change the staff assignment of score symbols
- Beam notes across staffs
- Use mapped staff styles for drum notation
- Predefined staff styles
- Share a score
-
-
- Key commands overview
- Browse, import, and save key commands
- Assign key commands
- Copy and print key commands
-
- Global Commands
- Global Control Surfaces Commands
- Various Windows
- Windows Showing Audio Files
- Main Window Tracks and Various Editors
- Various Editors
- Views Showing Time Ruler
- Views Showing Automation
- Main Window Tracks
- Live Loops Grid
- Mixer
- MIDI Environment
- Piano Roll
- Score Editor
- Event Editor
- Step Editor
- Step Sequencer
- Project Audio
- Audio File Editor
- Smart Tempo Editor
- Library
- Sampler
- Drum Machine Designer
- Step Input Keyboard
- Smart Controls
- Tool Menu
- Control Surface Install Window
- Touch Bar shortcuts
-
-
- Working with your control surface
- Connect control surfaces
- Add a control surface to Logic Pro for Mac
- Automatic assignment for USB MIDI controllers
- Grouping control surfaces
- Control Surfaces settings overview
- Modal dialog display
- Tips for using your control surface
- Supported control surfaces
- Software and firmware for Logic Pro for Mac
-
-
- Environment overview
- Common object parameters
- Customize the Environment
-
-
- Fader objects overview
- Use fader objects
- Play back fader movements
- Work with object groups
- Fader styles
- Fader functions: MIDI events
- Fader functions: range, value as
- Fader functions: filter
- Vector fader
- Special faders overview
- Cable switchers
- Meta event faders
- SysEx faders
- Work with SysEx messages
- Special functions
- Ornament objects
- MMC record buttons
- Keyboard objects
- Monitor objects
- Channel splitter object
- Physical input objects
- Physical input objects
- MIDI click objects
-
-
- Use MIDI plug-ins
-
- Arpeggiator overview
- Arpeggiator control parameters
- Note order parameters overview
- Note order variations
- Note order inversions
- Arpeggiator pattern parameters overview
- Use Live mode
- Use Grid mode
- Arpeggiator options parameters
- Arpeggiator keyboard parameters
- Use keyboard parameters
- Assign controllers
- Modifier controls
- Note Repeater controls
- Randomizer controls
-
- Use Scripter
- Use the Script Editor
- Scripter API overview
- MIDI processing functions overview
- HandleMIDI function
- ProcessMIDI function
- GetParameter function
- SetParameter function
- ParameterChanged function
- Reset function
- JavaScript objects overview
- Use the JavaScript Event object
- Use the JavaScript TimingInfo object
- Use the Trace object
- Use the MIDI event beatPos property
- Use the JavaScript MIDI object
- Create Scripter controls
- Transposer controls
- Record MIDI to Track
-
-
- Alchemy overview
- Alchemy interface overview
- Alchemy Name bar
- Alchemy file locations
-
- Alchemy source overview
- Source master controls
- Import browser
- Source subpage controls
- Source filter controls
- Source filter use tips
- Source elements overview
- Additive element controls
- Additive element effects
- Spectral element controls
- Spectral element effects
- Pitch correction controls
- Formant filter controls
- Granular element controls
- Sampler element controls
- VA element controls
- Source modulations
- Morph controls
- Alchemy master voice section
- Alchemy Extended parameters
-
- ES2 overview
- ES2 interface overview
- ES2 integrated effects processor controls
- Use ES2 in Surround mode
- Extended parameters
-
-
- Sculpture overview
- Sculpture interface
- Global parameters
- Amplitude envelope parameters
- Use the Waveshaper
- Filter parameters
- Output parameters
- Use surround range and diversity
- Define MIDI controllers
- Extended parameters
-
-
- Ultrabeat overview
- Ultrabeat interface
- Synthesizer section overview
- Filter section controls
- Distortion circuit controls
- Glossary
- Copyright
Use the Lane inspector in Logic Pro for Mac
You use the Lane inspector to change the parameters of the selected lane. The most important parameters are Status and First Data Byte. The Status parameter sets the event type for the selected lane. The First Data Byte parameter (shown as “Number” in the image) sets the value for the chosen event type. The appearance of the First Data Byte parameter changes when different event types are chosen.
Name a lane
The name of the selected lane is visible beside the disclosure arrow in the inspector. This is mirrored in the Name column in the Step Editor.
In Logic Pro, select the name to open a text field, enter a name, then press Return.
Note: If you define a named MIDI controller, or a note from a mapped instrument in the Status and First Data Byte parameter lines, the relevant name is automatically shown. Changing a note name in the inspector also alters the corresponding note name in the mapped instrument.
Delay or advance all steps on the selected lane
The inspector’s Delay parameter is very useful for drum programming (flams, for example), as only individual event types or note numbers are affected. It’s also useful for tightening up or sliding notes in a region, without resorting to quantization.
In Logic Pro, set the Delay parameter to the value you want to use.
Position changes are immediately reflected by the steps in the lane. New events (inserted when a grid was active) are offset from the grid positions by the Delay parameter value.
Tip: In general, you should transmit controller data slightly before or after note events, to improve the timing of notes. In other words, place controllers before (use a negative delay value) the grid positions of the notes lying exactly on the grid positions.
Change the length of new steps
In Logic Pro, drag the Length parameter values vertically to change the length of events (this primarily applies to note events) to be added, measured in divisions (the left number), and ticks (the right number).
You should avoid the use of small tick values because many MIDI devices do not respond quickly enough when note on/note off messages are sent in quick succession, resulting in no note being heard.
Set the MIDI channel number for a lane
In Logic Pro, select the MIDI channel checkbox.
If selected, the display is restricted to events on the set channel.
If unselected, the Channel parameter is ignored, and matching events on all channels are displayed.
Choose a MIDI channel number from the pop-up menu to the right of the Channel parameter.
Simultaneously change the parameters of multiple lanes
Just as you can adjust the parameters for several MIDI regions at once, you can set the parameters of several lanes simultaneously.
In Logic Pro, do one of the following:
Press and hold Shift, then click several lanes in the Name column.
Choose Lanes > Select All Lanes, then deselect lanes you don’t want to change by Shift-clicking them.
Any alterations you make in the inspector affect all selected lanes.
Change the event type
The event status determines the type of event controlled by each lane.
In Logic Pro, drag the event type shown beside the Status parameter vertically to choose one of the following:
Fader: Defines a fader event lane. Fader event data can be used to control any possible parameter (except channel volume and pan that use controllers). Fader data can also be used to create meta events.
Meta: Defines a meta event lane. Meta events are internal Logic Pro commands that can perform tasks such as screenset switching.
Note: Defines a lane for a particular note pitch (useful for drum programming).
Control: Defines a MIDI controller lane.
A-Touch (Aftertouch): Defines a lane for aftertouch (also known as channel pressure), a feature of many synthesizers that adds vibrato, for example, when you press down on MIDI keyboard keys that are already held.
P-Touch (Polyphonic Aftertouch): As above, but each note can be independently modulated.
Program Change: Defines a lane that is used to create and send MIDI program change events, allowing you to switch between sounds (electric piano and clavinet, for example) midway through a region.
Pitch Bend: Defines a lane for pitch bend information.
Important: The chosen Status parameter value (event type) directly affects the behavior (and appearance) of the First Data Byte parameter. For example, if Note is chosen as the Status parameter type, you can use First Data Byte to determine the pitch (MIDI note number) of the selected lane. If the MIDI region is played by a mapped instrument, a pop-up menu of input note names (drum sound names) appears here.
Show the first data byte and set a value
The First Data Byte checkbox and pop-up menu are shown at the bottom of the inspector.
The name of the First Data Byte parameter reflects the chosen Status parameter, as follows:
Fader, Meta, Control, Program: A number is shown as the first data byte.
Note, P-Press: Pitch is shown as the first data byte.
C-Press and PitchBd: The first data byte is dimmed, as it has no function.
Select the First Data Byte checkbox to show the defined first data byte. Select the box a second time (unselected) to hide the first data byte. In the case of note events, the velocity values of all notes (regardless of pitch) are displayed in the relevant lane.
Choose a value from the First Data Byte pop-up menu. The choices shown in the pop-up menu depend on the parameter shown in the Status line:
If Control is chosen in the Status line, the First Data Byte pop-up menu determines the controller type (controller number).
If Meta or Fader is chosen in the Status line, the First Data Byte pop-up menu determines the meta or fader event type (meta or fader message number).
If channel aftertouch (C-Press), or program change events (Program) is chosen in the Status line, the First Data Byte parameter setting is ignored and the first data byte is displayed as a beam height.
When pitch bend data (PitchBd) is chosen in the Status line, the First Data Byte parameter setting is also ignored because both data bytes are used to display the beam height.
Download the guides:
Logic Pro User Guide: Apple Books | PDF
Logic Pro Instruments: Apple Books | PDF
Logic Pro Effects: Apple Books | PDF