Lemur Programming Technical Limitations

Discuss Lemur and share techniques.

Lemur Programming Technical Limitations

Postby bxsj » 02 Mar 2012 17:37

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 :o 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.
Last edited by bxsj on 13 Apr 2012 18:35, edited 6 times in total.
Win7 64, Ipad Lemur, Cubase6 and a bunch of Roland Synths and Samplers
bxsj
Regular
 
Posts: 117
Joined: 24 Dec 2011 06:47
Location: Vienna

Re: Lemur Programming Technical Limitations

Postby analog604 » 02 Mar 2012 23:09

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
Dashboard gear control templates: User 112 :: LModIt Lite :: Co-authored: Blofeld DT :: more planned!
analog604
Regular
 
Posts: 249
Joined: 29 Dec 2011 15:40
Location: north east, usa

Re: Lemur Programming Technical Limitations

Postby kraftf » 11 Mar 2012 12:52

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 :o 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.
kraftf
Regular
 
Posts: 125
Joined: 14 Dec 2011 06:36

Re: Lemur Programming Technical Limitations

Postby analog604 » 11 Mar 2012 13:20

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.
Dashboard gear control templates: User 112 :: LModIt Lite :: Co-authored: Blofeld DT :: more planned!
analog604
Regular
 
Posts: 249
Joined: 29 Dec 2011 15:40
Location: north east, usa

Re: Lemur Programming Technical Limitations

Postby mat » 11 Mar 2012 17:47

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
Lemur modules and sequencer: http://music-interface.com
Setup: Win7professional 32bit, Intel Core 2 Duo @ 2,66 GHz.,Tascam US-144MKII, Ableton Live 8.4,
Arturia Analog Lab., Max/Msp, Maxforlive, Lemur Legacy + Ipad, Akai MPK61, Doepfer Pocket Control
mat
Regular
 
Posts: 126
Joined: 08 Dec 2011 09:21
Location: Germany

Re: Lemur Programming Technical Limitations

Postby filmriss » 14 Mar 2012 11:52

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.
filmriss
Newbie
 
Posts: 18
Joined: 28 Dec 2011 13:52

Re: Lemur Programming Technical Limitations

Postby Xenophile » 15 Mar 2012 00:06

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.
Xenophile
Newbie
 
Posts: 13
Joined: 08 Feb 2012 20:58

Re: Lemur Programming Technical Limitations

Postby bxsj » 15 Mar 2012 07:56

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
Win7 64, Ipad Lemur, Cubase6 and a bunch of Roland Synths and Samplers
bxsj
Regular
 
Posts: 117
Joined: 24 Dec 2011 06:47
Location: Vienna


Return to General Discussion

Who is online

Users browsing this forum: Google [Bot], MBM and 1 guest

cron