# Option N doesn't kick NLP anymore

**URL:** <https://forums.negativelabpro.com/t/option-n-doesnt-kick-nlp-anymore/7015>\
**Category:** Troubleshooting and Bugs\
**Created:** [November 7, 2023, 6:35pm UTC](https://forums.negativelabpro.com/t/option-n-doesnt-kick-nlp-anymore/7015 "2023-11-07T18:35:17Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![Condo](https://avatars.discourse-cdn.com/v4/letter/c/7ab992/32.png) [@Condo](https://forums.negativelabpro.com/u/Condo)\
**Post date:** [November 7, 2023, 6:35pm UTC](https://forums.negativelabpro.com/t/option-n-doesnt-kick-nlp-anymore/7015/1 "2023-11-07T18:35:17Z")

</div>

Because Lr 13.0.1 was bugged I came back to Lr 12.5 but encountered many issues I rest my preferences (I’m on a Mac).  
Since then Option N doesn’t display the NLPboard. To get it, I have to go to File/ puglin/ click on NLP and the NLP copmmand box appears and works as usual but for someone with hundreds of images to convert this is a cumbersome process.  
Any clue anyone?

---

<div class="post-metadata">

**Author:** ![cvandebroek](https://avatars.discourse-cdn.com/v4/letter/c/50afbb/32.png) [@cvandebroek](https://forums.negativelabpro.com/u/cvandebroek)\
**Post date:** [November 7, 2023, 11:08pm UTC](https://forums.negativelabpro.com/t/option-n-doesnt-kick-nlp-anymore/7015/2 "2023-11-07T23:08:30Z")

</div>

You may try resetting Lightroom’s preferences as things might have gone wrong when downgrading.  
Hold Option + Shift pressed when opening Lightroom. In the menu, select “Reset Preferences”.

If this doesn’t help, you can set the Option+N command up yourself. Go to  
System Preferences \> Keyboard \> Keyboard shortcuts

Select App Shortcuts and define a new one for Adobe Lightroom Classic.  
" Negative Lab Pro" =\> Option+N

It’s important to have three leading spaces to make this work, otherwise nothing will happen.

Hope any of these help!

---

<div class="post-metadata">

**Author:** ![Condo](https://avatars.discourse-cdn.com/v4/letter/c/7ab992/32.png) [@Condo](https://forums.negativelabpro.com/u/Condo)\
**Post date:** [November 8, 2023, 11:43am UTC](https://forums.negativelabpro.com/t/option-n-doesnt-kick-nlp-anymore/7015/3 "2023-11-08T11:43:14Z")

</div>

Thank you for your response.  
I had already reset Lr’s preferences prior to the issue.

In the chain you suggested ,System Preferences\>Keyboard\>Keyboard Shortcuts I don’t see any option to create a Shortcut  
(we’re talking about the Mac’s System preferences, right)?  
I’m still stranded.  
Now, to use NLP I have to go to LR/Files/plugin manager/click on NLP… not very cool

---

<div class="post-metadata">

**Author:** ![cvandebroek](https://avatars.discourse-cdn.com/v4/letter/c/50afbb/32.png) [@cvandebroek](https://forums.negativelabpro.com/u/cvandebroek)\
**Post date:** [November 8, 2023, 1:54pm UTC](https://forums.negativelabpro.com/t/option-n-doesnt-kick-nlp-anymore/7015/4 "2023-11-08T13:54:49Z")

</div>

Yes – Mac system preferences.

You need to choose the option for App Shortcuts. Not sure which version of macOS you’re on, so the screen might look different for you but this customisable option is available every since Mac OS X.

 ![](https://canada1.discourse-cdn.com/flex029/uploads/negativelabpro/original/2X/d/d49797f10404e590e7ab80e2b8aeb6af19d6e20a.jpeg)  
Once you’re in App Shortcuts, click the + button to set up a custom shortcut. Lightroom won’t show up in the list of applications as Adobe installs it in a folder, so you need to choose “Other” and then find Lightroom in your application folder. Once the app is selected, you can define the shortcut for NLP. Don’t forget the leading 3 spaces otherwise is won’t work.

---

<div class="post-metadata">

**Author:** ![Condo](https://avatars.discourse-cdn.com/v4/letter/c/7ab992/32.png) [@Condo](https://forums.negativelabpro.com/u/Condo)\
**Post date:** [November 8, 2023, 2:38pm UTC](https://forums.negativelabpro.com/t/option-n-doesnt-kick-nlp-anymore/7015/5 "2023-11-08T14:38:39Z")

</div>

Thank you very much for your effort, cvandebroek, I really appreciate!

I believe I’ve done all according to your instructions -only doubt is about the spaces, although I’ve set up three of them

 ![Screenshot 2023-11-08 à 15.20.51](https://canada1.discourse-cdn.com/flex029/uploads/negativelabpro/original/2X/5/5c084595bafcac6ebe9473d5678220dec8cc34e4.jpeg)  
But alas, I see no change and NLP remains usable only by the lenthy process

---

<div class="post-metadata">

**Author:** ![cvandebroek](https://avatars.discourse-cdn.com/v4/letter/c/50afbb/32.png) [@cvandebroek](https://forums.negativelabpro.com/u/cvandebroek)\
**Post date:** [November 8, 2023, 2:56pm UTC](https://forums.negativelabpro.com/t/option-n-doesnt-kick-nlp-anymore/7015/6 "2023-11-08T14:56:04Z")

</div>

You need to make sure to have the custom shortcut named exactly as it’s mentioned in the menus, although it looks correct on your screenshot.

See:

 ![](https://canada1.discourse-cdn.com/flex029/uploads/negativelabpro/original/2X/8/81af0bf18ecd1f3877c909a799d217035848feef.jpeg)  
If everything is set up correctly, your custom shortcut should be visible next to the menu entry.  
The reason you need the 3 leading spaces is because the menu entry is indented.

It should work without a restart of Lightroom but just in case restart the App 😊

---

<div class="post-metadata">

**Author:** ![Condo](https://avatars.discourse-cdn.com/v4/letter/c/7ab992/32.png) [@Condo](https://forums.negativelabpro.com/u/Condo)\
**Post date:** [November 8, 2023, 3:43pm UTC](https://forums.negativelabpro.com/t/option-n-doesnt-kick-nlp-anymore/7015/7 "2023-11-08T15:43:45Z")

</div>

Here in my Mac it looks the same as in your menu. And I have reset the Preferences again. Last thing would be to dump NLP, restart and download it again I guess?  
I’m really grateful.

---

<div class="post-metadata">

**Author:** ![addieleman](https://yyz1.discourse-cdn.com/flex029/user_avatar/forums.negativelabpro.com/addieleman/32/6278_2.png) [@addieleman](https://forums.negativelabpro.com/u/addieleman)\
**Post date:** [November 8, 2023, 8:53pm UTC](https://forums.negativelabpro.com/t/option-n-doesnt-kick-nlp-anymore/7015/8 "2023-11-08T20:53:18Z")

</div>

To the OP: you say you use Option N. On my Mac I use **Ctrl** -N which is the default shortcut for opening the NLP window.

---

<div class="post-metadata">

**Author:** ![Condo](https://avatars.discourse-cdn.com/v4/letter/c/7ab992/32.png) [@Condo](https://forums.negativelabpro.com/u/Condo)\
**Post date:** [November 8, 2023, 11:22pm UTC](https://forums.negativelabpro.com/t/option-n-doesnt-kick-nlp-anymore/7015/9 "2023-11-08T23:22:36Z")

</div>

That’s the one I had too but now that the shortcut don’t work it make the converting process even more painstaking.

---

<div class="post-metadata">

**Author:** ![cvandebroek](https://avatars.discourse-cdn.com/v4/letter/c/50afbb/32.png) [@cvandebroek](https://forums.negativelabpro.com/u/cvandebroek)\
**Post date:** [November 8, 2023, 11:54pm UTC](https://forums.negativelabpro.com/t/option-n-doesnt-kick-nlp-anymore/7015/10 "2023-11-08T23:54:38Z")

</div>

You see the shortcut next to the menu entry and it still does not work?  
In that case I would uninstall NLP and install fresh again, yes.

Custom shortcuts should definitely work, as this is the first instance macOS checks before anything else. This is more than weird, indeed.

---

<div class="post-metadata">

**Author:** ![burkphoto](https://avatars.discourse-cdn.com/v4/letter/b/f05b48/32.png) [@burkphoto](https://forums.negativelabpro.com/u/burkphoto)\
**Post date:** [November 10, 2023, 12:25am UTC](https://forums.negativelabpro.com/t/option-n-doesnt-kick-nlp-anymore/7015/11 "2023-11-10T00:25:08Z")

</div>

OPTION N was never the command. But CONTROL N works just fine…

---

<div class="post-metadata">

**Author:** ![Condo](https://avatars.discourse-cdn.com/v4/letter/c/7ab992/32.png) [@Condo](https://forums.negativelabpro.com/u/Condo)\
**Post date:** [November 10, 2023, 3:40pm UTC](https://forums.negativelabpro.com/t/option-n-doesnt-kick-nlp-anymore/7015/12 "2023-11-10T15:40:17Z")

</div>

I finally resolved my issue by dumping NLP and reinstalling a new one.  
Thank you Chris for your support and patience, and thank you all who did offer a solution.
