how to reset controller assignments in logic pro x

Change Language

Assign key commands, assign a function to a key, learn a controller assignment, delete a key command or controller assignment.

beat bars blog

beat bars is a place for musicians, producers and DJs.

How to map an effect and assign a controller in Logic Pro X

Logic Pro X offers powerful, almost unlimited possibilities in music production. It is certainly one of the most versatile and advanced DAWs available on the market. This has its pros and cons. What is impossible in other DAWs is almost always possible in Logic Pro. However, what is relatively simple in other products, is often too complicated and difficult in Logic. This sounds quite controversial in relation to a product by Apple, but it is based on the experience of many musicians and producers.

One of the non-intuitive and confusing things is configuring external MIDI controllers – assigning and mapping MIDI events to effects.

This can be done in several ways. On the one hand, it’s good because it provides a lot of flexibility. However, it requires the user to spend time learning too much unnecessary information.

Key Commands

• Open the “Key Commands - Edit” window from the main menu, or use the keyboard shortcut ⌥K.
• Select the command you are interested in, e.g. Record, and then click the button in the bottom right corner <Learn New Assignment>.
• Now press the button on your physical MIDI controller, e.g. the footswitch you want to use to start recording.

That’s it! Unfortunately, it is impossible to map everything this way. Despite the fact that there are so many commands, they are only general assignments. Take, for example, Volume – master or track – if you want to control it using the MIDI pedal, this parameter cannot be assigned in this window.

To do this, you need to use another method…

Control Surfaces - Controller Assignments

• Move the slider or knob that you want to assign to the controller, first with the mouse or touchpad. This way, you activate the parameter which will be soon mapped.
• Then, in the “Control Surfaces” menu, select the option “Learn Assignment for  parameter ”, or use the key combination ⌘L. The displayed parameter will be the one you triggered earlier with your mouse.
• Now move the slider of the physical controller or the MIDI pedal to assign a parameter to it.

This is how you can map e.g. Master Volume, Track Volume, as well as parameters inside individual plug-ins, both those that are built-in, e.g. Echo Feedback, and in third-party Audio Units. The possibilities are therefore quite large, but sooner or later you will come across a situation where you cannot assign the parameter you want this way. Let’s take, for example, the built-in EQ and try to map High Cut Frequency. No matter how you move the mouse, the menu will still display High Cut Q-Factor instead of High Cut Frequency, and it cannot be changed in any way.

Smart Controls - single mapping

The previous ways had one thing in common – the <Learn> button. It will also appear in this method, but in another place. You will find it in the Smart Controls window (unfortunately these controls are not very smart at all). Open this view by clicking the “knob” icon on the toolbar, or select “Show Smart Controls” from the View menu, or simply press the B key.

Let’s start with the visual layout of the parameters. Click the ⓘ icon to show the Inspector panel. You will probably see “Automatic Smart Controls” at the top – this is the starting point. You can choose a different Layout (by hovering over this header, you will see that it is a drop-down list – this is not obvious at the beginning). It is worth experimenting by trying different elements from the list.

Once you have chosen Layout, click on one of the knobs (preferably those marked as “Unmapped”).

• you can click the <Learn> button, but as in the previous method, you won’t get what you want.
• It is better to choose a parameter from the drop-down list, e.g. Channel EQ ▸ High Cut Frequency
• In the External Assignment section, click <Learn> and move the physical controller slider or pedal.

This method of mapping and assigning parameters is the most complicated, but gives the greatest possibilities. It allows to map “invisible” properties, and even assign several different parameters to one controller.

Smart Controls - multiple mapping

Assigning many different parameters, usually from different plug-ins, allows to create very useful parameter combinations that can be controlled with one move (in Ableton it is called Macro). To define such a set, proceed in the same way as in the previous point.

After mapping and assigning the first parameter, add the second and subsequent parameters as follows:

• In Controls, select another knob which is Unmapped.
• In Inspector, in the Parameter Mapping section, click the ⚙ icon and then Add Mapping. Another drop-down list will appear. Proceed identically as in previous method. You no longer have to assign a controller because it was done when adding the first parameter.

Thanks to this, by moving the wheel, knob, slider or pedal on your physical MIDI controller, you can control two or more parameters at once. Many trademark sounds, such as the Wobble effect known from Dubstep, result from modulating a few parameters. The equally well-known Wah-Wah effect is nothing more than a combination of several different EQ attributes: Frequency, Q-Factor and Gain. By experimenting with many variables at the same time, you may even be able to create a completely new effect.

Till next time.

20 Jun 2020

• #Foot Controller

Explore categories →

You can assign controllers to Logic Pro parameters, and edit controller assignments to fit your workflow.

This section explains how to assign controllers to Logic parameters, edit controller assignments, and use zones and modes to switch between groups of assignments.

This chapter covers the following:

Assigning Controllers to Logic Pro Parameters

Controller Assignments: Working in Easy View

Controller Assigments: Working in Expert View

Assigning Buttons to Key Commands

Controller Assignments Storage

Akai Professional

Akai mpk mini plus | how to reassign your transport controls in logic pro x print.

Modified on: Fri, 4 Nov, 2022 at 5:09 PM

On your MPK Mini Plus, hold down the PROG SELECT  button, and press Pad 3 to automatically assign your controller to the Logic Pro X preset.

After the controller is reassigned and connected to your computer, click on logic pro x  to the right of the apple logo, then go to control surfaces > controller assignments . ,  you will then open the controller assignments window. to start, create a new zone for your mpk mini plus. you may press the +  at the bottom of the window to create a new zone. , from here, go to the window that includes controller/parameter . and press the +  below to create a new control. then press learn mode so your controller can send the proper control to your computer. you may now press the first transport control you would like to assign. for this example, we are assigning the play button . ,  your transport control is now ready to be assigned a control you may find commands aside the command window . however, you will find more commands when you press  show... , you are now all set to properly assign the transport controls on your mpk mini plus in logic pro x.

Did you find it helpful? Yes No

Related Articles

Still need help.

Chat with one of our technical support experts! Click on the chat bubble in the bottom-right corner of this page during our business hours to get started.

Monday through Friday:

• 5:00am EST - 2:00pm EST
• 2:30pm EST - 6:00pm EST

inMusic World Headquarters

200 Scenic View Drive Suite 201 Cumberland, RI 02864 United States

inMusic Brands Europe LTD

Unit 3, Nexus Park, Lysons Avenue Ash Vale Hampshire GU12 5QE United Kingdom

inMusic GmbH

Hans Günther Sohl Str. 4a 47807 Krefeld Germany

inMusic Taipei

7th Floor, NO. 165, Naking East Road Section 4 Taipei 105 Taiwan

inMusic Japan Corporation

Minami Azabu 1-5-10 Koike Building 1-2F Minato-ku, Tokyo 106-0047 Japan

• Existing user? Sign In

[SOLVED] Controller assignment input keeps changing

By thedeermunk January 5, 2022 in Logic Pro

• Reply to this topic
• Start new topic

Recommended Posts

Thedeermunk.

Hi everyone,

I used a hack to utilize my Akai MIDIMIX buttons to select tracks one through eight. It works by setting up "Mackie Control" then changing the channel select input to the device, in this case my MIDIMIX. for some reason the assignment doesn't stay though and returns to "Any" after either restarting Loigc or changing a project. I have to reset the input back to my MIDIMIX every time

Things I've tried:

1. Copying the assignments out and pasting them into a new, renamed zone.

2. Changing Channel Strip from "Fader Bank" to "Index"

3. Checking "exclusive"

Link to comment

Share on other sites.

Likely your MIDI port list config is changing (devices being added or removed) which is causing entries to go away, or the Akai sets up new virtual MIDI ports with different ID's, rather the reusing the existing ID for that port.

Is it just assignments from that MIDI port that reset? Ie if you create assignments set to different incoming MIDI ports, do those assignments stick, or not?

Thanks for the reply!

Technically I'm not creating the MIDI assignments. I imported the zones from the "Control Surface Setup" section under "setup..." in the drop down menu and chose "Mackie Control" since it has the assignments I need.

According to my lengthy research on the internet, there is no way in logic to create a controller assignment that selects a track. This seems counterintuitive given that the designers of the Mackie Control, surface control group have done this. This is the closest Ive gotten.

However, all of the other controller assignments I've created for my MIDIMIX ie. volumes, FX knobs etc.. still work and do not need the input reset. I now this probably doesn't answer your questions but I'm a lay person with this kind of stuff. Hoping this might clear up what is going on.

So you are installing a "fake" MCU in the control surfaces setup window. What MIDI I/O ports have you set for this device?

Presumably you are leaving that MCU device installed from that point on?

According to my lengthy research on the internet, there is no way in logic to create a controller assignment that selects a track.

Sure there is, but as selecting a track within a fader bank is a function of the control surface functionality, you have to have one installed before Logic will respond to that behaviour. Which is what you've done, by adding a fake MCU. This is the proper way to go about this, when you want to use control surface functionality in Logic without a "real" control surface device.

This seems counterintuitive given that the designers of the Mackie Control, surface control group have done this. This is the closest Ive gotten.

I'm not sure what you mean here - what's counterintuitive?

My guess would be you've installed the MCU with "Any" as an input port, and you are trying to edit it's assignments to some other MIDI port (which Logic does not handle - there is no such thing as an MCU that transmits over multiple different MIDI ports, that's not how it's designed), so any edits to those assignments which belong to that fake MCU device get their inputs reset to the device you've specified in the control surfaces window.

Have you tried setting the in/out port of that MCU device to that of your Akai controller, and seeing whether they stick now?

(Be aware that this may have other unintended consequences, as again you're mashing two different devices and MIDI messages which may well clash or not depending on a variety of factors).

Note that abusing the MCU in this way is somewhat outside the design parameters of how these things are supposed to be used - it does work, but you need to be prepared to handle the complexities of behaviour should you choose to hack the controller support in this way.

• 4 weeks later...

Logic seems to be doing it again regardless of what the ports on my Mackie HUI is set to. It all started after I transferred Logics controllers assignments to another computer so I could edit from my laptop. When I transferred it back it broke. Not such a smart move looking back :/

[edit] never mind. I installed the wrong Mackie while trying to fix it. The HMU is the correct one.

• 10 months later...

So, if I'm reading this correctly, thedeermunk, you installed a dummy MCU control surface (HMU in your case) and assigned your existing Akai MIDIMIX as the i/o for the dummy MCU control surface, and this has remained stable, allowing you to access Logic screen elements that would otherwise be unavailable to the MIDIMIX without the MCU control template? 

This is exactly what I'm looking to do, and others have advised, assuming everything is stable doing that. 

This is great to hear if it works as expected?

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account. Note: Your post will require moderator approval before it will be visible.

×   Pasted as rich text.    Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.    Display as a link instead

×   Your previous content has been restored.    Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

• Insert image from URL
• Submit Reply
• Unanswered Topics
• All Activity
• Leaderboard
• Logic Pro Class
• Student Testimonials
• Book in English
• Livre en Français
• Privacy Policy
• Terms of Service
• Create New...

Working with MIDI Controllers in Logic Pro X

Harnessing MIDI Controllers is an essential tool to exploit the expressive potential of both software and hardware instruments. In the following workshop, Mark Cousins takes back control… During our last two workshops – exploring Studio Strings and Studio Horns – we saw just how important MIDI CC (continuous controller) messages are in fully extracting the […]

Harnessing MIDI Controllers is an essential tool to exploit the expressive potential of both software and hardware instruments. In the following workshop, Mark Cousins takes back control…

During our last two workshops – exploring Studio Strings and Studio Horns – we saw just how important MIDI CC (continuous controller) messages are in fully extracting the expressive range of many software instruments. The most commonly used MIDI CC message is the modulation wheel, which in case of Studio Strings and Studio Horns moved between a soft pianissimo performance to a strong fortissimo.

The exact effect of the modulation wheel will depend on how the instrument has been configured, but the process of recording, editing and manipulating MIDI CC data is important to your work inside Logic Pro X.

It’s worth noting that Logic has changed the way it works with MIDI CC data, away from the MIDI Draw system and instead using an extension of the automation system called region-based automation. So whatever software instruments you work with, it’s worth understanding more about MIDI CC messages in Logic Pro X.

MIDI CC messages date back to the earliest days of MIDI sequencing, based on a set of 127 assignable controllers that can shape and control aspects of sound. The modulation wheel (MIDI CC 1) is the most commonly used MIDI CC message, and may vary the amount of vibrato, for example. Other controllers exist, although their effect will always depend on the software instrument that receives them.

In its simplest form, you can record MIDI CC information into Logic using a controller keyboard or a MIDI fader bank. Here, the use of parallel track is useful as a means of distinguishing between note data and MIDI CC messages, allowing you to keep the two forms of information separate from one another. MIDI regions will display a preview of the MIDI CC messages, but this won’t be editable at this point.

Useful editor

One way of editing MIDI CC messages is to use Logic Pro X’s various MIDI editors. Piano Roll for example, includes a lower panel that can be used to display and edit MIDI CC messages. Another really useful editor is the Event List that will display all forms of MIDI information in a text-based format. The text-based approach makes it really easy to filter different event types or simply use it to reassign MIDI CC messages.

The main purpose of the workshop is to explore how MIDI Draw has been replaced by region-based automation. Before version 10.4, MIDI Draw was used as means of editing MIDI CC data at ‘arrangement level’, which makes most sense given that its application (namely, adding expression) is usually an arrange-level decision. The use of MIDI Draw was essential for serious virtual orchestral work, where this level of dynamic interest is so vital to the music’s realism.

Rather than using MIDI Draw, Logic Pro X 10.4 now uses Region-based automation to display and edit MIDI CC information. Conventional automation data is, of course, not attached to region. You can edit and reposition a vocal, for example, without its automation moves being moved with it. By comparison, so-called region-based automation is permanently attached to the region and, most importantly, region-based automation can be used to display MIDI CC messages, whereas track-based automation can’t.

Region-based automation looks and functions like track-based automation, with a series of nodes to display the varying MIDI CC levels. Like automation, you can draw new nodes in, change curves between two node points, or even scale the nodes up and down across the whole track (all of which is covered in the walkthrough). However, remember to make the distinction between conventional automation data (used to control specific virtual controls in Logic’s mixer) and the ‘generic’ MIDI CC data used in region-based automation.

Although it ‘looks’ like automation data, it’s just plain and simple MIDI CC information. While MIDI CC data may seem like the antiquated solution, its open-ended nature makes it a real winner in the studio. For example, most ‘knob-heavy’ hardware instruments (or controller keyboards) will transmit MIDI CC data, and in many cases, software instruments can map incoming CC messages in seconds. Likewise, any synth produced after 1983 will undoubtedly respond to CC messages, which provides a level of backwards compatibility that most could only dream of!

Working with MIDI Controllers: step-by-step

1. Our Logic Project uses a simple Retro Synth patch. Retro Synth’s Settings page lets you quickly map a number of key parameters to incoming MIDI CC messages – in this case, Mod Wheel to Filter Cutoff.

2. If you have a suitable MIDI Controller, you can simply record MIDI CC messages directly into Logic. Consider using a parallel track lane (Track > Other > New Track with Same Instrument) to keep the MIDI CC data separate.

3. Keeping MIDI CC as a separate region makes it easier to move MIDI CC data between different tracks and parts in your arrangement. In this case, copying the same CC moves onto the synth Bass on Track 2.

4. Even if you’ve recorded the MIDI CC data separately, there’s always the option of merging it with the original note data using the glue tool. This is certainly a good option when it comes to arranging the track.

5. Working the other way, the Event List editor is useful if you want to separate Note data from MIDI CC messages in the same region. To do this, start by filtering out note data using the button at the top of the Event List.

6. The event list now shows only the MIDI CC information for the sequence, so you can simply ‘Select All’ and delete. To preserve the MIDI CC data, simply filter Controller data and delete the notes instead.

Gaining hands-on access to any parameter in Logic’s mixer doesn’t necessitate buying a dedicated hardware controller, thanks to Automation Quick Access. You can enable Automation Quick Access using the menu option Mix > Enable Automation Quick Access.

7. Another really useful function of the Even List editor is its ability to change the type of MIDI controller. You could, for example, record using a Mod Wheel but change the type to Expression (11) or Cutoff (74).

8. To get a better view of the recorded data, or edit elements of it, try opening the Piano Roll editor. The lower pane defaults to note velocity but can be switched to view MIDI CC messages in that region.

9. MIDI CC data is displayed as a series of Nodes on the bottom half of the window. You can use the Arrow tool to add or reposition Nodes, for example, or the Pencil tool to draw new moves ‘free hand’.

10. The drop-down menu at the bottom of the Piano Roll editor can also select other MIDI CC types, which can be useful if you want to draw in other controller messages that aren’t Modulation.

11. MIDI CC messages can also be edited on arrange level, using an extension of the Automation system called Region-based automation. To view and edit the MIDI CC data, select the menu option Mix > Show Automation.

12. Move the Track’s Automation mode from Track to Region and from the drop-down parameter menu, select your chosen MIDI CC type – Ch. 1: Modulation. The MIDI CC data is displayed the same as in the Piano Roll.

13. Unlike conventional automation data, Region-based automation moves are ‘hard-wired’ to the region and copied or moved with the region. This is useful as MIDI CC data often forms an integral part of the region’s musicality.

If you haven’t setup a suitable controller, Logic will prompt you accordingly, which simply involves moving the controller (like a modulation wheel) of your choice. Once assigned, any selected automation parameter will have ‘hands on’ access.

14. Once up and running, MIDI CC data in the arrange area can be viewed and edited like any other automation data. For precision work, the ability to draw the nodes in (without having to enter the Piano Roll) is a godsend!

15. For automation nodes entered by hand, it’s well worth employing the automation curve tool, moving between exponential, logarithmic and S-Curve shapes. The result is a more musical transition.

16. Another useful feature is the ability to scale the automation data using the box on the right-hand side of the track header. Raising or lowering the setting will apply the corresponding correction to all the MIDI CC messages.

17. Clicking on the small arrow on left-hand side of the track lane will create a parallel track which can be assigned to different MIDI CC parameter. This lets you edit two or more MIDI CC types at the same time.

18. The Mix menu contains automation options, which double-up on MIDI CC messages, most notably the Delete Automation menu item, which is useful as a reset option or a means of paring back to the note data.

Get the latest news, reviews and tutorials to your inbox.

Trending Now

1 my forever studio: benn jordan’s concrete cabin is a low-key science lab, 2 kanye west allegedly samples underground producer tsvi without permission: “we’re at the bottom; he’s at the top with billions in his bank”, 3 benn jordan says “more than half” of music gear owners “aren’t really making music on it”, 4 light as a feather: nujabes’ lasting impact on hip-hop and electronic music.

• Search forums

Follow along with the video below to see how to install our site as a web app on your home screen.

Note: This feature may not be available in some browsers.

• Apple Logic Pro Discussions

Logic Pro (X)   Controller assignments - MIDI output

• Thread starter pajczukin
• Start date Sep 5, 2020
• Sep 5, 2020

Peter Ostry

Administrator.

• Sep 6, 2020

If you are familiar with Logic’s MIDI Environment, you can do it. Connect a monitor object to the channelstrip with the plugin, move knobs and faders in the plugin and look what the monitor shows. If you see "Fader" events, you are fine. Take a transformer with a map or a couple of transformers, convert the Fader events to CC or whatever you want and send them out through a "Midi Instrument" which is actually a MIDI port.  

Peter Ostry said: If you are familiar with Logic’s MIDI Environment, you can do it. Connect a monitor object to the channelstrip with the plugin, move knobs and faders in the plugin and look what the monitor shows. If you see "Fader" events, you are fine. Take a transformer with a map or a couple of transformers, convert the Fader events to CC or whatever you want and send them out through a "Midi Instrument" which is actually a MIDI port. Click to expand...

• Sep 7, 2020

Just a note: There are settings for reset messages in Logic’s global MIDI preferences, but the option for "send used instrument settings" does not work, at least not in my 10.5.1 Logic under Mojave. This option should send learned (assigned) parameters at several occasions, see the Logic user manual. Maybe it works for you. If I need such a feature I have to find workarounds as described below. — From Controller Assignments you can have feedback of the learned values from Logic. "Automatic" usually works. Logic sends you the current values of learned parameters when you select the instrument track. Via key commands we have several possibilities to select tracks by MIDI. For me it works for example when I send Logic one MIDI event to select all tracks and another one to select all instrument tracks. Depending on the current selection, one of the two events forces Logic to send the learned parameters of an instrument track. The Arrange window must have the focus, otherwise Logic complains about the wrong view. A view-independent command is the "Hide" toggle, it works in the Arrange- and Mixer window. The track in question must be selected. Maybe you find better commands for your application. Maybe you only need that once and simply deselect/select one track with mouse clicks before you start playing. Or the command for next/previous track is good for you. — Another option would be to have track automation that sets plugin parameters. Send a "Play" command via MIDI, read the parameter values in Arduino and switch automation off or send a "Stop" command. This also works only with Controller Assignments and only learned parameters are sent from Logic. Not as flexible as the method above but better if you want always the same start values. — If you do not want Controller Assignments, you can do similar things in the MIDI Environment but this is not easier. Rather more complicated.  

pajczukin said: don't know how to get that "feedback". For me it's grayed out as you can see on the enclosed screenshot. Click to expand...

pajczukin said: So even Logic sends feedback I still don't know where he sends it, to which output? Click to expand...

• Sep 8, 2020

OK, one more time great thanks. I need to test it and I will inform about the results.  

We value your privacy

We use essential cookies to make this site work, and optional cookies to enhance your experience. Please note that in order to help fund the site we may serve ads by via Google AdSense, and cookies may be used for personalisation of these ads to make them more relevant. These are optional and you can choose to enable/disable any such cookies in your preferences:

Click here for further information and to configure your preferences

• Essential cookies
• Optional cookies
• Third-party cookies
• Detailed cookie usage
• Privacy policy

Control Surfaces Support Guide for Logic Pro

• Control surfaces overview
• Mackie Control overview
• Displays overview
• Display control buttons
• Channel strips overview
• Channel strip buttons and LEDs
• Assignment buttons overview
• Assignment views
• Track button overview
• Channel view
• Track shortcut menu
• Channel strip setup view
• Pan/Surround button overview
• Pan/Surround Mixer view
• Pan/Surround Channel view
• Pan/Surround mode options
• EQ button overview
• EQ Mixer view
• EQ Channel view
• Options in EQ edit mode
• Send button overview
• Send Mixer view
• Send Channel view
• Options in Send edit mode
• Plug-in button overview
• Plug-in Mixer view
• Plug-in Channel view
• Plug-in edit view
• Instrument button overview
• Instrument Mixer view
• Instrument edit view
• Bank buttons
• Channel buttons
• Flip button
• Global View buttons
• Function keys
• Modifier buttons
• Automation buttons
• Group button
• Utilities buttons
• Transport buttons overview
• Marker button overview
• Large Marker mode
• Nudge button overview
• Large Nudge mode
• Temporary Nudge mode
• Cycle button
• Drop button
• Replace, Click, and Solo buttons
• Cursor and zoom keys
• Jog/Scrub wheel
• Programmable user modes
• Foot switches
• Assignments overview
• Display buttons table
• Channel strips assignments table
• Assignment buttons table
• Assign Function keys table
• Global View buttons table
• Modifier buttons table
• Automation buttons table
• Utilities buttons table
• Transport buttons table
• Cursor keys table
• Jog/Scrub wheel assignments table
• External inputs table
• iControl overview
• iControl Assignment buttons
• iControl Arrow buttons
• iControl channel strip controls
• iControl Mixer and Channel view
• iControl jog wheel
• iControl transport controls
• iControl locators with Cycle mode
• iControl Master fader
• iControl assignments overview
• iControl Assignment button functions
• iControl channel strip functions
• iControl jog wheel functions
• iControl transport functions
• Euphonix device setup
• Mirror mixer tracks on Euphonix display
• MC Pro Soft Key assignments setup
• Euphonix Read and Write automation modes
• Euphonix fader strips
• Control of plug-ins with Euphonix devices
• Euphonix knobsets overview
• Inserts knobset
• Input knobset
• Aux or Sends knobset
• Pan/Surround knobset
• Group knobset
• Mix or Output knobset
• Euphonix Logic Pro features
• Set up your Motormix
• Motormix Select buttons
• Motormix faders and pots
• Motormix A to H multi buttons
• Motormix I to P burn buttons
• Motormix Solo and Mute buttons
• Motormix view controls
• Motormix left function buttons
• Motormix right function buttons
• TranzPort setup
• LCD display
• Channel strip
• Master controls
• CS-32 MiniDesk setup
• CS-32 MiniDesk assignments overview
• CS-32 MiniDesk display
• CS-32 MiniDesk pots
• CS-32 MiniDesk channel strips
• CS-32 MiniDesk bank button
• CS-32 MiniDesk F keys
• CS-32 MiniDesk cursor controls
• CS-32 MiniDesk transport controls
• CS-32 MiniDesk jog wheel controls
• FaderMaster 4/100 setup
• FaderMaster 4/100 assignments
• MCS3 assignments overview
• MCS3 F1 to F6 buttons
• MCS3 W1 to W7 buttons
• MCS3 cursor controls
• MCS3 jog wheel and shuttle ring
• MCS3 transport controls
• microKONTROL and KONTROL49 setup
• microKONTROL and KONTROL49 Pads overview
• Transport mode
• Solo/Mute mode
• Rec/Select mode
• Enable the User 4–8 modes
• Effect edit mode
• microKONTROL and KONTROL49 main controls
• microKONTROL and KONTROL49 channel strips
• microKONTROL and KONTROL49 external input
• Baby HUI setup
• Baby HUI assignments overview
• Baby HUI channel strips
• Baby HUI encoder assignment controls
• Baby HUI automation controls
• Baby HUI display controls
• Baby HUI utility controls
• Baby HUI navigation controls
• Baby HUI transport controls
• HUI assignments overview
• HUI assign controls
• HUI fader bank buttons
• HUI window controls
• HUI keyboard shortcuts
• HUI channel strips
• HUI DSP controls
• HUI function keys
• HUI global controls
• HUI automation controls
• HUI status/group controls
• HUI editing controls
• HUI time display
• HUI numeric keypad controls
• HUI transport controls
• HUI cursor buttons
• HUI jog wheel
• HUI foot switches
• C4 V-Pots and V-Select buttons
• C4 function buttons
• C4 Assignment buttons overview
• C4 Marker overlay
• C4 Track overlay
• C4 Channel Strip overlay
• C4 Function overlay
• C4 modifier buttons
• C4 Parameter, Track, and Slot buttons
• Novation Launchpad setup
• Launchpad multi-device support
• Novation Launchpad buttons overview
• Launchpad modes overview
• Use a Novation Launchpad in Session mode with Logic Pro
• Use Novation Launchpad in User mode with Logic Pro
• Use Novation Launchpad in Mixer mode with Logic Pro
• Change mix parameters on the Launchpad Pro, Launchpad X, and Launchpad Mini MK3
• SAC-2K Setup
• SAC-2K assignments overview
• SAC-2K LCDs and encoders
• SAC-2K channel strips
• SAC-2K Mixer view controls
• SAC-2K software navigation controls
• SAC-2K locator display
• SAC-2K marker controls
• SAC-2K transport controls
• SAC-2K Channel view controls
• SAC-2K troubleshooting
• Recording Light setup
• Recording Light parameters
• SI-24 Setup
• SI-24 Assignments overview
• SI-24 Channel strips
• SI-24 Status mode controls
• SI-24 Channel assign controls
• SI-24 Surround/pan controls
• SI-24 Numeric key controls
• SI-24 Transport controls
• US-2400 Setup
• US-2400 Assignments overview
• US-2400 Channel strips
• US-2400 Encoders
• US-2400 Master channel
• Instrument Edit view
• Plug-in Edit view
• US-2400 Master section controls
• 01V96 Setup
• 01V96 Assignments overview
• 01V96 Display Access controls
• 01V96 Fader Mode controls
• 01V96 LCD controls
• Insert display mode
• Channel display mode
• Meter display mode
• 01V96 Selected Channel control
• 01V96 Data entry controls
• 01V96 Channel strips
• 01V96 Assignable keys
• 02R96 Setup
• 02R96 assignments overview
• 02R96 Display Access control
• 02R96 Aux Select controls
• 02R96 Encoder and Fader Mode controls
• 02R96 Effect/Plug-in controls
• 02R96 LCD display
• 02R96 assignable keys
• 02R96 channel strips
• 02R96 Machine Control parameters
• 02R96 data entry controls
• DM1000 Setup
• DM1000 Assignments overview
• DM1000 Display Access controls
• DM1000 Aux Select controls
• DM1000 Encoder and Fader Mode controls
• DM1000 LCD controls
• DM1000 LCD display modes
• LCD common elements
• DM1000 Data entry controls
• DM1000 Channel strips
• DM1000 Stereo channel strip control
• DM1000 Assignable keys
• DM2000 Setup
• DM2000 Assignments overview
• DM2000 Matrix Select controls
• DM2000 Aux Select controls
• DM2000 Encoder and Fader Mode controls
• DM2000 Display Access controls
• DM2000 Effect/Plug-in controls
• DM2000 LCD display
• DM2000 Track Arming controls
• DM2000 Automix controls
• DM2000 Locator controls
• DM2000 Transport and cursor controls
• DM2000 Channel strips
• DM2000 Assignable keys

Overview of using control surfaces in Logic Pro

Control surfaces are hardware devices that typically feature controls such as faders, rotary knobs, buttons, and displays. They allow you to select parameters for editing, or select tracks, channel strips, or channel strip banks for playback and recording. Some control surfaces offer a jog wheel to move the playhead precisely, transport buttons to control project playback, and other physical controls.

More sophisticated control surfaces can feature motorized faders, rotary encoders, LED rings, and programmable displays. The additional feedback these provide makes them easier to use without looking at your computer screen or relying on mouse interaction.

Logic Pro provides dedicated support profiles (plug-ins) for a number of hardware control surfaces, enabling control of transport, mixing, recording, automation, and other tasks.

Many USB MIDI keyboard controllers can also act as control surfaces. In addition to a musical keyboard, these devices can include drum pads (used for note entry or as buttons to execute Logic Pro commands), faders, rotary controls, transport controls, and assignable buttons that can be mapped to Logic Pro commands. Logic Pro provides Lua scripting support, rather than a dedicated profile, for dozens of keyboard (and desktop) controllers from various manufacturers. USB MIDI keyboards can be automatically mapped to Smart Controls and other Logic Pro functions, or you can create and modify your own assignments.

The Logic Pro User Guide contains a section that shows you how to set up your control surface device to work with Logic Pro. See Add a control surface to Logic Pro in the Logic Pro User Guide .

Note: A number of devices such as Nektar Panorama, Native Instruments Komplete Kontrol, and other units, provide a manufacturer-supplied plug-in. Refer to the device manufacturer’s support materials for setup information.

All Logic Pro Mixer controls, such as level and pan, can be adjusted onscreen with your mouse and computer keyboard. However, this is not an ideal method for precise real-time control. You can enhance your creative flow and can achieve greater flexibility and precision by connecting a hardware control surface to your computer.

Control surfaces or MIDI keyboard controllers are ideal for creating dynamic live performances using a portable Mac and an audio interface. In the studio, you can record control surface automation for mixer and plug-in parameters (even when Logic Pro is not in record mode). Track automation appears in the Tracks area and in the Piano Roll Editor.

Moving a fader on the control surface prompts the corresponding fader in the Logic Pro Mixer to move, and rotary knobs (or other controls) can be used to control EQ or other parameters, with the corresponding parameters updating instantly in Logic Pro.

Because communication between Logic Pro and your control surface is bidirectional, adjustments to parameter values onscreen are immediately reflected by the corresponding control on the control surface. Visual feedback on the control surface is determined by the facilities of the device itself, such as LCD screens, LED indicators, or motorized faders.

When you use a supported control surface with Logic Pro, some controls are pre-mapped to common functions. You can map unassigned controls to other Logic Pro commands and functions.

For detailed information about how to assign controllers on your control surface device to Logic Pro functions, see Assign hardware controllers in the Logic Pro User Guide .

For devices supported by Lua scripts, you can also remap controls in this way, or you can use the Smart Controls mapping options. See Use Smart Controls in the Logic Pro User Guide .

The following sections explain how to use specific control surfaces with Logic Pro.

Download the guides:

Logic Pro User Guide: Apple Books | PDF

Logic Pro Instruments: Apple Books | PDF

Logic Pro Effects: Apple Books | PDF

Control Surfaces Support Guide: Apple Books | PDF