Help! Internal error has occurred: Limits.lua:53:

[rajdude]

Hello everyone,

A total newbie here so please be gentle ;-)

No matter what I do I keep getting this error message while trying to access midi2lr's options in LR's menu

An internal error has occurred: Limits.lua:53: attempt to index global 'ProgramPreferences' (a nil value).

I am on Windows 10, 64 bit. Lightroom is CC version 2015.8

I have tried ......

• older versions, like 2.8
• uninstalling and re-installing multiple times
• Deleting midi2lr folders (where it gets installed in)

.......  still same issue.

Please! Someone help me!

-Raj

[Ernst Bokkelkamp]

ProgramPreferences is a public (global) table created in the file "Preferences.lua".

"Info.lua" provides the information that "Options.lua" provides the options menu.

"Options.lua" has a require statement for "Preferences.lua".

According to this information the error message is unexpected.

My first thought is that there is something wrong with the plugin directory.

Where did you install the plugin ? The prefered location is "%appdata%\Adobe\Lightroom\Modules".

[rajdude]

Thanks for looking into this, Ernst.

It is installed in the default location which is the same as you posted. See ...

-Raj

[rajdude]

By the way, I just tried version 2.7.0.4, even that one crashes on trying to open options.

-Raj

[rajdude]

Where does midi2lr keep its settings?

I want to wipe out everything and do a fresh installation. After uninstalling midi2lr, I deleted its plugin directory, I also searched the registry and deleted everything related to midi2lr (not much there).

So how come it remembers its old settings when I install midi2lr again?

I suspect it is holding on to some bad profiles I had downloaded from the internet and loaded into midi2lr the first time I installed midi2lr.

-Raj

On Thursday, October 25, 2018 at 10:24:52 PM UTC-4, rajdude wrote:

[rajdude]

Here is the answer to my own question (in the previous post).......

MIDI2LR is keeping these two files...

1. MIDI2LR.xml
2. MIDI2LR.log

...under %appdata%\Roaming\ which translates to the following path

C:\Users\rajdu\AppData\Roaming\MIDI2LR

The xml has the setting I was wondering about:

<?xml version="1.0" encoding="UTF-8"?>

<PROPERTIES>
  <VALUE name="profile_directory" val="C:\Users\rajdu\Pictures\Lightroom\MIDI2LR"/>
  <VALUE name="LastVersionFound" val="34144513"/>
</PROPERTIES>

-Raj

[Ernst Bokkelkamp]

Did you have a look at the contents of MIDI2LR.log ?

My opinion is that the contents of the file MIDI2LR.xml is wrong because it points to the wrong directory.

I would delete these files before re-installing the plugin in the right directory.

[rajdude]

Ummm.............no, the plugin directory is correct. See my screenshot posted 8:36 AM today, it shows the path.

The midi2lr.log and midi2lr.xml were in this path : C:\Users\rajdu\AppData\Roaming\MIDI2LR (I did not put it there)
The profile folder is where I chose to put in the profiles : C:\Users\rajdu\Pictures\

Lightroom\MIDI2LR

Anyway, I will try to wipe out everything and start over.........I bet it wont still work! LOL Been troubleshooting this off and on for two days now :-(

I cannot believe it works for you guys. Sorry, I am really frustrated here.

-Raj

[rajdude]

Oh well.......just as I predicted........I uninstalled. wiped ALL files, installed 2.5........fresh.

Absolutely no profiles, no settings (choose profile folder is blank), just a default install.......no other thing touched........still pulling up options crashes midi2lr!

-Raj

[rajdude]

ok I made some progress........

How I got it working:

1. I uninstalled. wiped ALL files,

1. installed 2.9.5
2. Created profiles folder (blank)
3. in MIDI2LR's GUI >> settings >> pointed it to the profiles folder
4. Mapped a few buttons manually
5. Saved it to a brand new profile

Now I am able to open the options page. However it still remembers some profiles which do not exist!

That means that MIDI2LR keeps these settings "somewhere" which does not get wiped when we uninstall it......its not there in the registry also......where is it?

[Ernst Bokkelkamp]

These settings are stored in the Lightroom Preferences, which can be found in  "%appdata%\Adobe\Lightroom\Preferences\Lightroom ? Preferences.agprefs"

You could use an editor to remove the lines, starting with the line which contains ["sdk_com.rsjaffe.midi2lr"] until the next line that starts with ",

Please make sure you keep a copy of the original file because.

On Friday, October 26, 2018 at 10:13:22 PM UTC+2, rajdude wrote:

ok I made some progress........

[TaucherTF]

PERFECT!!!

Thanks Ernst, i was looking for days to solve the same problem.

After I*ve deleted everything containing "midi2lr" at the Lightroom 6 Preferences.agprefs within the folder C:\Users\xxx\AppData\Roaming\Adobe\Lightroom\Preferences and restartet LR, it works perfect.

Thanks a lot!

[rajdude]

See this is the thing which threw me off......the location of the preference filea is different than what I used to think!

I did read this info in another thread. Over there, the guy was saying that just delete the preferences files totally (not edit it). I really did not want to delete my LR preferences files altogether, for risk of losing my preferences, of course. But, as a test, I did delete those files......but nothing happened.

In the old days, there was a setting in LR which let the preferences files to be written next to the catalog (in the same directory where the catalog is). So that is where I was looking for the preference files.I do have preference files next to the catalog, but the timestamps are from 2016!

Today I see that the preference files are actually here (just like you two mention):

C:\Users\rajdu\AppData\Roaming\Adobe\Lightroom\Preferences

Thanks!

-Raj

[Tobias]

I am getting the same error message on LR Classic CC latest version and I don't find any line in the file called "Lightroom Classic CC 7 Startup Preferences.agprefs" with that information "sdk_com.rsjaffe.midi2lr"

Any idea what I could try next.

[Tobias]

I think I found the error. I turned off the checkbox for "Zusatzmodul bei jeder Verwendung..." and then the error disappeared.