rsjaffe edited this page Jun 23, 2018 · 62 revisions

On this Page

Prerequisites | Support | Installation | Instructions | Updating from a Previous Version | Faq/Known Issues


  1. Lightroom 6+ or Lightroom CC Classic
  2. Any compatible USB MIDI controller (e.g. Korg nanoKONTROL, behringer BCF2000). See for a list of known compatible and incompatible controllers.
  3. Windows 7+ or MacOS 10.12+


Use the MIDI2LR discussion forum for support. If MIDI2LR appears to be functioning incorrectly, include the contents of the MIDI2LR.txt file in your message. The file is generated by the plugin and saved in the directory containing the plugin. Also, if using or later, a log file (MIDI2LR.log) will be found in %AppData%\MIDI2LR (for Windows users) or ~/Library/Logs/MIDI2LR (MacOS users). This log file should also be posted.


  1. Download the installer and run it. The default directory chosen by the installer should work for most users.
  2. In Lightroom, add the MIDI2LR plugin by going to File⇢Plugin-Manager⇢Add and navigating to and selecting the MIDI2LR.lrplugin folder.
  3. The MIDI2LR application should automatically launch. If it is closed, it can be launched by going to File⇢Plug-in Extras⇢Start MIDI2LR
  4. Moving any controllers will populate the mapping table and allow you to set functions. You can also save/load mappings.
  5. If you want to stop sending messages to Lightroom while setting up the application, press the Halt sending to Lightroom button at the bottom of the application. The connection indicator will turn yellow while the connection is halted. Press the button again to restart communications.

If you need more details, Jeffrey Friedl has extensive generic plugin installation instructions.


The rest of this wiki has details about the various software features. There are many instructional Youtube videos uploaded by users. And the MIDI2LR group is a great place for support.

Updating From a Previous Version

  1. Close the MIDI2LR application if running
  2. Exit Lightroom (it hangs on to the old plugin if it's still running).
  3. Download and run the installer, installing the plugin into the same directory as your old version.
  4. Start Lightroom

FAQ/Known Issues

  1. Lightroom 7.3 opens up Effects Panel when Dehaze slider adjusted. This happens when Reveal adjusted panel is checked. This is a Lightroom bug.
  2. Lightroom 7.3 clears all settings that weren't specified in a develop preset. This happens when you apply a develop preset. This is a Lightroom bug. It is fixed in 7.4.
  3. Lightroom returns to basic adjustments when making other develop adjustments. This happens when you are editing a photo that is synced to Lightroom Mobile and you make the other adjustments before the tracking delay has expired. Tracking delay is adjustable in the Options Dialog under Other. In other situations, the only way to stop this is to turn off GPU acceleration in Lightroom. This is a Lightroom bug.
  4. Lightroom opens Lens Corrections when making Transform Adjustments. This is a Lightroom bug. It appears they forgot to reassign the controls to the correct panel in the API. To work around this, open up the app options dialog, go to Other, check Show status and activity and uncheck Reveal adjusted controls. This way, Lightroom won't open up a panel when you adjust a control, but it will show the adjusted values on-screen in a translucent bezel.
  5. The effects adjustments panel opens when making dehaze changes in Lightroom Classic version 7.3. This is a Lightroom bug and has been reported to Adobe.
  6. The basic adjustments panel doesn't open when making contrast changes. This is a Lightroom bug and has been reported to Adobe.
  7. Horizontal perspective control switched with vertical for portrait photos. This appears to be a Lightroom bug. See issue #107 for details.
  8. Pressing the Alt (Option) key doesn't change the display while moving a slider in MIDI2LR. The Alt (Option) key is used with several different sliders to show an optional display that highlights what is being changed. This key is ignored when moving the slider in MIDI2LR. This is a Lightroom bug.
  9. Lightroom doesn't read keyboard shortcuts or app crashes when sending shortcut. When using Lightroom with a keyboard that does not match the Lightroom language setting, some keyboard shortcuts send by MIDI2LR may be ignored by Lightroom. For example the \ (backslash) shortcut for Before/After does not function with a German-language keyboard if Lightroom is set to use English. For Lightroom with English setting this can be fixed by creating a TranslatedStrings_Lr_en_US.txt resource file to change the keyboard shortcuts. For more information see:
  10. App can't connect to Lightroom. Before trying to debug this, check your Lightroom version. MIDI2LR only runs on Lightroom 6/CC or later. Then, check your firewall. MIDI2LR uses ports 58763 and 58764 on localhost ( to communicate between the application and the plugin.
  11. Motorized faders stop working after upgrading MIDI2LR. Closing the MIDI2LR app then restarting Lightroom should fix this. This is a Lightroom issue.
  12. Motorized faders move slightly when new picture selected. This appears to be due to the effect of rounding off the values, and so far I have been unable to stop that from happening.
  13. Remember to save your mappings in the app. Any settings you make on the Options dialog are automatically saved by Lightroom. However, the button/knob mapping is managed by the app, so you need to hit the Save button in the app to save them.
  14. Error Assertion failed: err == noErr. This will occur in OSX if the app does not have execution privilege for the user. A quick fix is to, in Terminal do chmod +x "MIDI2LR.lrplugin/". If you encounter this, please open up an issue to notify me so I can fix the distribution files.
  15. Lightroom crashes upon starting the app. This can occur if you put the plugin in a directory in which you don't have full privileges (appears to be mainly a Windows 10 issue). Place the plugin in another directory. I suggest using a sub-directory off your Documents folder, as then it will be easily accessible for updating.
  16. MIDI2LR app doesn't load profile when starting. This can occur if you put the plugin in a directory in which you don't have full privileges. Place the plugin in another directory. I suggest using a sub-directory off your Documents folder, as then it will be easily accessible for updating.
  17. default.xml in the plugin directory gets overwritten by the application. This is the expected behavior. Do not use the file name default.xml for your settings if you want to save your settings in the plugin directory. I recommend saving your settings elsewhere anyway, as you're less likely to accidentally overwrite or delete them when updating the plugin.
  18. Button needs to be pressed twice for the command to work. MIDI2LR expects buttons to be in "toggle off" mode, where the button sends a 127 when pressed and a 0 when released. If you need to press a button twice to get an action, you need to reprogram the MIDI controller to the proper mode.
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.