Any reasons why my midi device often not detected/Midi2LR unresponsive?

[Surfingserenity]

Midi2LR works flawlessly for me but I have an on going issue where my midi device is often not detected by Midi2LR or Midi2LR is just not responding to the input.
I haven't been able to nail down whether it's a Midi2LR issue or a midi controller issue - sometimes the solution is just to unplug the midi controller and plug it back in, other times I also need to close Midi2LR and then restart it from inside LR, sometimes that also doesn't work and I need to close and restart LR itself and sometimes even that doesn't work and I need to unplug the midi controller and plug it back in and close Midi2LR and then restart it from inside LR.
It's really annoying when this happens and ruins what is otherwise a near flawless experience working with Midi2LR. There is no indication that the midi controller has issues because it's always worked perfectly with Ableton Live and I've had the controller for years without experiencing any issues using it with audio software.
It just occurred to me perhaps something is stealing the Midi focus but I wouldn't know what that could be because I have had it happen even when just LR is open.

What could possibly be causing this and what can I do to troubleshoot it?
I'd really like to solve it once and for all.

UPDATE:
I'm currently using a Novation Launch Control but I had largely the same issue with the 2 previous Midi controllers, one of which was a Arturia BeatStep.
I have tried 3 different USB cables but none made any difference.

[remov-b4-flight]

Hi,
have you ever tried 'reload' button at center of bottom on MIDI2LR app window?

[Surfingserenity]

The "Rescan midi devices" button?
That only helps sometimes and generally only if I have plugged the midi device in/out after opening LR.

[Surfingserenity]

Has anyone else experienced this issue or have any tips they can add?

[antzpantz]

Tried a new/different cable?

…

On Mon, 7 Apr 2025 at 17:01, Surfingserenity ***@***.***> wrote: Has anyone else experienced this issue or have any tips they can add? — Reply to this email directly, view it on GitHub <#822 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFIYPFEUKXUQTKT3A2SGGG32YI5GLAVCNFSM6AAAAABZ2CGN5CVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENZUHAZTAMA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Surfingserenity]

I have tried 3 different cables but none made any difference.

[remov-b4-flight]

it's nothing to do for users
if not show green note/cc message after pushing 'rescan' button.

[Surfingserenity]

What do you mean by that?
I have had this issue with all the midi controllers I have used with Midi2LR, it's almost as if something is stealing the controllers focus. Also it's not a midi controller issue as I also use them with Ableton Live(obviously not at the same time) and have never had any issues with them there.

[remov-b4-flight]

[Note/CC path to Lightroom]
MIDI cont. -> (OS USB layer) -> (OS MIDI class driver) -> MIDI2LR.app/exe -> MIDI2LR lua plugin -> Lightroom

Is not there any app/drivers provided by Contoller vendor or other Music apps. ?

Did they not have interfare these paths? especially between MIDI class driver and MIDI2LR.app/exe

I recommend full clean install from OS. (and do first to install Lightroom and MIDI2LR)

[antzpantz]

Do you have other MIDI controllers plugged into your computer that might have the same ID as your MIDI2LR controller? Have you tried other USB cables? Have you removed non-essential USB devices or tried the controller with the bare-minimum number of USB devices connected? Have you tried uninstalling and reinstalling MIDI2LR? Try isolating the issue.

…

On Wed, 9 Apr 2025 at 17:11, Surfingserenity ***@***.***> wrote: What do you mean by that? I have had this issue with all the midi controllers I have used with Midi2LR, it's almost as if something is stealing the controllers focus. Also it's not a midi controller issue as I also use them with Ableton Live(obviously not at the same time) and have never had any issues with them there. — Reply to this email directly, view it on GitHub <#822 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFIYPFFMYVLWHSAP7BTMQYD2YTP3TAVCNFSM6AAAAABZ2CGN5CVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENZXGU3DKOA> . You are receiving this because you commented.Message ID: ***@***.***>

[Surfingserenity]

I have tried 3 different cables but none made any difference. I only have the one controller plugged in, it's a Novation Launch Control. I haven't tried re-installing Midi2LR, perhaps that may help.

[antzpantz]

Definitely try reinstalling MIDI2LR. And I don't just mean 'other MIDI controllers' ... Even other USB devices or hubs can interfere with the comms.

…

On Sun, 13 Apr 2025, 10:35 pm Surfingserenity, ***@***.***> wrote: I have tried 3 different cables but none made any difference. I only have the one controller plugged in, it's a Novation Launch Control. I haven't tried re-installing Midi2LR, perhaps that may help. — Reply to this email directly, view it on GitHub <#822 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFIYPFFDX2JXE2U7VPDE2632ZJYZJAVCNFSM6AAAAABZ2CGN5CVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOBRHE4DSMQ> . You are receiving this because you commented.Message ID: ***@***.***>

[antzpantz]

And not just 'reinstall'... Do a full uninstall and then install again. Export your settings and shortcuts before you do so.

…

On Sun, 13 Apr 2025, 10:35 pm Surfingserenity, ***@***.***> wrote: I have tried 3 different cables but none made any difference. I only have the one controller plugged in, it's a Novation Launch Control. I haven't tried re-installing Midi2LR, perhaps that may help. — Reply to this email directly, view it on GitHub <#822 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFIYPFFDX2JXE2U7VPDE2632ZJYZJAVCNFSM6AAAAABZ2CGN5CVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOBRHE4DSMQ> . You are receiving this because you commented.Message ID: ***@***.***>