MIDI Kinetics Forum

While developing Lemur templates there are some technical limitations to be considered. As per today (Lemur editor version 3.04) I am aware of the following limits:

File size limit is currently set to 16MB per template.
Maximum multiline script length is currently set at 4096 characters.
Maximum expression text length is currently set at 256 characters.
Current limit to the number of items enclosed in '{' '}' braces is 64.
Maximum number of entries in an array is currently set to 256 (maybe less when dealing with long entries?);
Maximum number of bytes for a MIDI SYSEX string is currently set to 256.
Maximum number of items in a Menu object is currently set to 32.
Maximum number of points in a Breakpoint object is currently set to 64.
Maximum length of lists in scripts is 256 elements.

The undo/redo function doesn nott apply to live text editing in the Script panel.

Exceeding these limits may lead to unpredictable behavior, frustration and head banging If you are aware of any other limitation please post them here. It would be nice to have a point of reference for such information.

Cheers,
B.

Thanks for posting this in one place B. it should save time for some.

I found out that the script editor was overloaded when it began to show only white and the text wouldn't scroll any longer.
I was assigning long arrays for knob function.
It worked out fine though after my confusion, just run a second script.

-J

bxsj wrote:While developing Lemur templates there are some technical limitations to be considered. As per today (Lemur editor version 3.04) I am aware of the following limits:

File size limit is currently set to 2MB per template.
Maximum multiline script length is currently set at 4096 characters.
Maximum expression text length is currently set at 256 characters.
Current limit to the number of items enclosed in '{' '}' braces is 64.
Maximum number of entries in an array is currently set to 256 (maybe less when dealing with long entries?);
Maximum number of bytes for a MIDI SYSEX string is currently set to 127.
Maximum number of items in a Menu object is currently set to 32.

The undo/redo function doesn nott apply to live text editing in the Script panel.

Exceeding these limits may lead to unpredictable behavior, frustatrion and head banging If you are aware of any other limitation please post them here. It would be nice to have a point of reference for such information.

Cheers,
B.

Well done for gathering these limitations.
I would suggest to you to send them to Liine support on order that they are included in the manual. New users should be aware of these info.
Personally I've been frustrated too many times experiencing them but finally got used to them. The most annoying limitation/bug for me is the undo/redo function that doesnt apply to text editing in the Script panel.

the not undo for script is so frustrating. it gets me almost every day. it's so ingrained to press undo that I forget it will take my work back to the last save. fortunately frequent saving is also an established practice.

kraftf wrote: Personally I've been frustrated too many times experiencing them but finally got used to them. The most annoying limitation/bug for me is the undo/redo function that doesnt apply to text editing in the Script panel.

Thanks for posting this list. I think it is pretty complete.
Nice overview, and I agree that this should be mentioned in an updated manual...

I also had most trouble with "no undo for scripts"!
By the time I get used to "copy" (Strg+C) a script before editing. That way I can paste it again, if the new scripting is going wrong.

@Liine:
Is there hope for bugfixes on future versions? At least at some the points?

cheers
mat

this thread should be made sticky
and not just be added to the manual, but also a popup when you first open the Lemur editor.

Very helpful information. Thanks!
I'm just getting started with Lemur, and this weekend I was going to implement some giant, 128-member arrays of radio buttons to call up the preset patches from a midi sound module, and I wanted to put the name of each patch on its button via the multilable feature.

So now it looks like I'll have to implement each one as two 64-button arrays... But is there any way to "connect" them such that when I press a button in one array it shuts off all the buttons in the other? It seems like, with radio buttons, one of them is always going to be active.

implement some giant, 128-member arrays of radio buttons to call up the preset patches from a midi sound module

You might consider using a different approach to select patches; e.g. a patch changer? I guess you are doing this to have patch names on the lemur?
B.
Edit: Here is an example from another post http://liine.net/forum/download/file.php?id=246