MIDI Kinetics Forum

I worked on this template yesterday evening. This morning I tried to open it and the Lemur editor just crashes everytime I try to open it. The template is attached. This is mildy said unnerving, hours of work lost. Does it male sense to send the template to support? Does anybody have a clue on how to prevent such behavior?
B.
Edit:
When opening the xml file in IE, the following error message is displayed:

The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.
--------------------------------------------------------------------------------

The character '<' cannot be used in an attribute value. Error processing resource 'file:///T:/Daten/Lemur/Library/V-Synth/V...

for(i=0;i<4;i++) sysexout = osc1_time_sysex;
---------^

Btw., operating system is Win 7 64 Bit

Looking into this. It appears the crash occurs within the arraytohex script, because of the arraytostring function. We've already seen that one in another crashing template that was sent to support.
Try editing the jzml from a text editoer (back up the file first), and delete line 191 : return(array_out);
This should allow you to open your template back while we chase the bug.

Oops, I meant delete "return arraytostring(a);" in line 171 and leave everything else.

Thanks for the fast reply!
I can confirm that removing line 171 in my template, using WordPad, solves the crash when trying to open the template. In other templates the arraytohex function works just fine. So it must be specific to the stuff I do in this template. Here is what I noticed:
- I introduced a new function arraymerge that concatenates two arrays into one. Could this be causing the offending behavior?
- The script arraytohex lost all carriage returns
- The height value of menu midi_channel gets set to 8670 when I resize container settings? Before resizing it shows 510, but indicating a much higher height in the graphical display. Sounds confusing, so am I.

Again thanks for the help. At least I can access the template again. Any recommendations on how to circumvent this problem for the time being?

Take care,
B.

Hi
The returning a function -arraytostring(a) - bit seems a bit weird to me . . .
Maybe assign it back to the array and return it instead as it is clearer as to what should happen . . .

Iam doing some similar stuff with some Roland gear and will send you some stuff . . .
Cheers
MM

You saved my day I changed the script as per your recommendations and now it can be opened w/o a problem!!!
Thanks for your around the clock/world support. Greetz from Austria
Take care,
B.

Solution:
Do not use the arraytostring function in a RETURN statement returning variables in a script.
Bad:
return arraytostring(a);
Good:
arraytostring(a);
return(a);

This is valid in Lemur editor version 3.04.

Cheers,
B.

Hi

Also I don't think that the array merge function is even necessary -
you should just be to use {vector_1, vector_2} and they join . . .
I posted a Bank/Patch Change module somewhere the other day and will add an improved one soon
Have alook http://liine.net/forum/viewtopic.php?f= ... 2&start=10
Greetz from Australia

MM

Macciza wrote:Hi
The returning a function -arraytostring(a) - bit seems a bit weird to me . . .
Maybe assign it back to the array and return it instead as it is clearer as to what should happen . . .

Iam doing some similar stuff with some Roland gear and will send you some stuff . . .
Cheers
MM

There shouldn't be any difference in doing and I'm investigating that crash...

Also I don't think that the array merge function is even necessary -
you should just be to use {vector_1, vector_2} and they join . . .

Thanks, very usefull piece of information (not mentioned in the manual?).

I posted a Bank/Patch Change module somewhere the other day and will add an improved one soon
Have alook viewtopic.php?f=24&t=1152&start=10

Thanks again. I am pretty new to Lemur and still learning.

I wish I had more time to spend with this amazing app.
Cheers,
B.