Any chance the max size of templates gets increased?

[electrofux]

My two interfaces already take up 90% and i would like to expand. Any chance we see an increase in the max template size?

[Traxus]

Excuse the probing, I don't mean to be insulting if this kind of advice is below you, but have you re-factored at all?

A lot of the time when building templates, I tend to build stand alone modules and duplicate them across the template. Inside those modules are scripts etc... That in an ideal world would actually be removed from the modules and placed at a higher level where all of them could access the code, but only have it written once. A lot of times templates can really be slimmed down by finding and abstracting redundancies.

[artsUNMUTED]

I have got the same problem - some custom graphic stuff takes a lot of memory - esp. text elements arranged into icons. It can't be helped with script optimization.

[Macciza]

Not sure about size increase plans currently but it may happen . . .
Re optimising: As always 'It depends' . . .
If you have a lot of scripting in every custom graphic, it can be factored out.
And there are other ways to optimise . . .
If they are non-changing graphics they only need to be defined once, not 100 times . . .
Same thing with any multiple representations of the same control . . .

[Softcore]

I'm with Macciza and Traxus....after the initial excitement of achieving what I wanted functionally with my latest template attempt, Im looking at it now wondering how stupid can a person be to not use aliases for static texts that appear 24 times in one template - just tried and I had a 3% decrease


Also, most of the time, using a more "encapsulated" logic in scripts, looking at it in a bigger picture results in avoiding duplicate calls and functions. Already got a lot of ideas to improve my templates memory-wise.

[electrofux]

I am sure something can be done with my template but i think it is a problem because i am doing a "per track"-sequencing template and it features 20 tracks with 16 steps and 20 faders each aswell as submenues/containers and stuff. Maybe i can post it and someone can take a quick look and see if there is something catastrophic going on (i wouldnt be surprised). It is kinda hard though to dive deep into this and refactor stuff. My first tries ended in deleting the whole thing because it didnt work anymore . The complicated stuff is done and i have 8% left for some simple synth templates that go along with the sequencer but the air is getting thin.

[artsUNMUTED]

All that is true - we learn all the time but there are some things that can't be optimized in the current state - in my x1 template there are 200 unique icons (a couple of thousands of text objects). I can't optimize it... and they take about 40% of the template.

[Softcore]

I understand that part of the appeal of your designs is the visual aspect but frankly? I would prefer to not have that 40% burdain and look "basic"....

I wouldnt "sacrifice" more than 5% for looks only - of course that is just a personal matter - opinion!

[artsUNMUTED]

everybody has got their priorities:-).

[dsorlien]

Yes, please increase the Lemur object memory. It's 32Mb now, and really could use 64MB.

I've put about a year of work into my big Lemur template. It is a controller for the Fractal AxeFX guitar processors. The AxeFX is a rack multi-effect device with over 30 different effect types (e.g. amp, cab, delay, reverb, chorus, pitch shift). Each effect block has anywhere from 10 to 120 editable parameters. In total, there are about 1000 unique editable parameters in the AxeFX that my template can control.

I have re-factored many times, but now am running out of ideas to save memory.

Please double the memory limit. That would be huge for those of us pushing the limits of the Lemur IOS platform.