keyboard shortcut not working

[Bernd]

I configured via the options menu some keyboard shortcuts ie ALT 1 or ALT 2 and a simple g

and mapped them to buttons in my Korg kontrol2

BUT this is not working! the command on the midi device itself is detected but the keyboard shurtcut is not executed.
What could be wrong? Any ideas?

regards
Bernd 

[Yozz]

I Think it should be:

Moving between Modules	Library Module	G/E/C/N or Ctrl Alt 1	G/E/C/N or Cmd Opt 1
	Develop Module	D or Ctrl Alt 2	D or Cmd Opt 2

from: http://www.lightroomqueen.com/keyboard-shortcuts/lrcc6/

so maybe You forgot to check Control in this shortcuts ?

[Bernd]

thx - but none of the keyboard shortcuts is working.

anyway how would I map the ALT 1 (=from numpad) key stroke?

[Mathieu Carbou]

Did you make sure, after mapping your shortcuts, to bring the LR window to the foreground ? I run over the same issue, but it was because I kept MIDI2LR window in the foreground and LR window was in the background. Shortcut mappings work when you are in LR window. This resolved my issue.

[Mike Morelos - Fotografo]

Hello.

I used the keyboard shortcuts for almost a year without any problem.

Today just upgraded to WIN 10, lightroom 6.8 and now the keyboard shortcuts don't work anymnore.

Same setup as before.

[Henrique Ribas]

hey guys, 

here is on 2019, and i'm having the same issue

all the things work, except the shortucts at midi2lr

Can anyone help me?

[Natalia Rodriguez]

I am on a MAC and none of the keyboard shortcuts work for me. :(

[Rory Jaffe]

Are you using the latest version (3.1.0.4)? That alerts you if certain mac security settings are causing problems with the keyboard shortcuts. I'm also working on simplifying the code for the next release, which may fix some of these problems. In the meantime, you can use Shortcut Keys Assignments. And I'm going to address the issue with number key assignments, which don't work currently.

[Rory Jaffe]

3.2.0.0 beta is available, and the main changes are to the key handling code, fixing issues with LRCopy/LRPaste, and some other issues (e.g., unable to use number keys as shortcuts). See the announcement at the top of the group messages.

[yoav picherski]

Hi thanks for this amazing tool!
I'm on latest LR with the last 3.2.3.0 setup and shortcuts doesn't work for me... :(

Any solution?

[Rory Jaffe]

Please post MIDI2LR.log for the last run, it is in ~/Library/Logs/MIDI2LR

[yoav picherski]

HI

thanks for the quick reply

Here is the log

[Rory Jaffe]

It should work. What controller are you using? I noticed that you are sending some NOTE ON signals. Is that from hitting a key? MIDI2LR ignores low values to avoid reacting to "noisy" keystrokes, which causes problems if you are using keys that transmit key pressure values. If you look on the app, just above the Clear ALL rows button, you should see something like 11: NOTE14 [127] when you strike Note 14. How high is the value in the brackets?

[yoav picherski]

Hi Rory

Im using the X touch mini from behringer, i didnt set any velocity on the controller. maybe it is from accidentally moving the fader which is not assigned to any command. 

[yoav picherski]

Still Nothing happen when using the keyboard shortcuts option.

Im trying to assign before after and paste from last picture and i cant make it happen...

[yoav picherski]

it says 127

[yoav picherski]

Hi rory,any suggestion? 😬 now it crashed two time when trying to use the assigned keyboard shortcuts.

Log attached.

[Rory Jaffe]

I'm really at a loss. Sending 127 is great--that should work fine. One thing I've noticed in your log files is that Automation permission granted for com.adobe.LightroomClassicCC7 is missing from many of your runs. That message should always appear in the log for MacOS users if you've attempted to send a keystroke. 

This makes me wonder if you have profile issues, and the profile that's active is not what you expected. When you're having trouble sending keystrokes, recheck that the mapping is correct by looking at the app window. If the mapping is incorrect, we've found your problem. Otherwise, I don't know.

[Mike]

Hi.

The same thing happens to me (XTouch). Have you managed to fix it?

Thank you.

[Michael ONeill]

Forgive the Newbie question, I'm just getting started. Is there a tutorial or a separate program used to map keyboard shortcuts? I'm trying to create a button for Photomerge to Panorama, but I can't find any option for entering keystrokes. I'm using Windows 10 and  the Behringer X-Touch Mini. 

Thanks,

Michael

[Rory Jaffe]

See the wiki: https://github.com/rsjaffe/MIDI2LR/wiki/Plugin-Options-Dialog#keyboard-shortcuts

[Michael ONeill]

Thanks Rory! That was just what I needed. I really appreciate your quick response, thanks for sharing this with all of us!

Michael

[Hoop]

I just recently got the Behringer Xtouch Mini controller and I have been mapping out the buttons, but I am still coming across the problem that others are having when assigning keyboard shortcuts. I am trying to apply a copy and paste, and a before/after shortcut. I make the shortcut in setting then I map it to a button. After I have done that I press the button and get no response as if the button is unassigned. Any suggestions on what I could do to get over this problem?

[Rory Jaffe]

If using Windows, did you make sure, after mapping your shortcuts, to bring the LR window to the foreground? If that's not the problem, we'll need to see your log file.

[SE]

Hi Rory

Longtime user here and I have the same problem – after quite a few Mac versions that crashed on shortcuts, the latest one just ignores them for me... Tried deleting and adding it in Accessibility, no change. If I delete MIDI2LR from there and launch, it will ask for permissions and add itself, but still ignore the shortcuts.

[Rory Jaffe]

Here's a second try at fixing it, Again, post whether success or failure: https://www.dropbox.com/s/32h0j9xi28xmyz1/MIDI2LR-3.4.9.1-osx-installer.dmg?dl=0 .

[Aleksandr Newsky]

Win7x64Rus

LR 8.4.1

AKAI Midimix

Midi2Lr 3.4.9.1

Copy and paste LR settings not working :(

Deleted the settings. Completely deleted the plugin. Reinstalled. Restarted the system. Tied to different buttons and crawlers. No results. No mistakes. It just doesn't work (Function Copy and paste LR settings not working to). The code in square brackets is [127].

пятница, 4 ноября 2016 г., 18:40:46 UTC+3 пользователь Bernd написал:

[Aleksandr Newsky]

Tell me, is it possible to get help here? After all, the function does not work! Why is the author not responding?

[Rory Jaffe]

See my message in the other conversation. Please do not post duplicate questions.

[Aleksandr Newsky]

I wanted to add that the value "before / after" "\" works. And any combination of Ctrl or Shift does not work

пятница, 21 февраля 2020 г., 8:50:49 UTC+3 пользователь Rory Jaffe написал:

[Денис Поликарпов]

I installed version 4.3.1.11 (MAC OS 10.15.7) and keyboard shortcuts doesn't work. Is there any solution?

пятница, 4 ноября 2016 г. в 18:40:46 UTC+3, Bernd:

[Денис Поликарпов]

When I set up keyboard shortcut for COPY (Cmd+Shift+c) I get this pop-up window

понедельник, 24 мая 2021 г. в 23:11:50 UTC+3, Денис Поликарпов:

[Rory Jaffe]

Include the contents of the MIDI2LRinfo.txt file and the log file (MIDI2LR.log) in your message. These files are found in %AppData%\MIDI2LR (for Windows users) or ~/Library/Logs/MIDI2LR (MacOS users).

[Денис Поликарпов]

Here it is

вторник, 25 мая 2021 г. в 19:53:47 UTC+3, Rory Jaffe:

[Rory Jaffe]

Thanks. That explains what's going on. MacOS reports that the keyboard type is Russian. Because of the way MIDI2LR has to encode keystrokes to send to Lightroom, in MacOS it has to use the key symbols that are on the keyboard. Try to use the Cyrillic character that MacOS expects is on the "C" key instead of "C". That should fix it. If not, I'll look into this further. Alternatively, change the keyboard type to English (or whatever language the non-Cyrillic characters are arranged in) before starting Lightroom. Then you could use the non-Cyrillic characters in MIDI2LR.

[Rory Jaffe]

I will work on a new version of MIDI2LR that tries the standard ANSI keycodes as well, so that "c" would work in the future. For now, using Cyrillic is what I suggest.