MIDI Kinetics Forum

Hi
I commented on the title - which I believe is in-accurate though maybe I am taking a technical meaning from it. . .
It is NOT a memory issue - nor is it a 'bug' as such - and obviously I don't see it as 'huge' given that it will be fixed pretty soon . . .
To me a 'huge memory bug' is either a leak that builds up over time and consumes all your RAM, or over-allocation of empty RAM at startup,
or over-writing other memory locations, or loading a gig of unused graphics - some sort of actual problem to do with actual 'memory' . . .

When you lose all your work without warning, it qualifies as "huge."

It may qualify as huge to you but that does not make it a 'huge memory bug' and you don't lose all your work, only that beyond the 512k limit
If you only need to push it a little further it can be gotten around if you are prepared to hit a text editor . . .

It's a huge issue to me too. I can't believe they let this bug through. Such a waste of time.

A huge personal issue maybe, but not a shouted 'huge' 'memory bug' - which it isn't see above ...
It is a 'feature' of the original Lemur - and yes they let this 'feature' through . .

I will be REALLY interested in seeing the projects that are produced by the main complainants on this issue . . .
I find it quite strange that many of these posts were put up in the completely WRONG forum area
I also find it strange that few of them have posted anything much in the way of code or examples or assistance . . .
I can't help but think that the projects will suffer from bloat and excess and could have been achieved within the current limitations . . .
And I hope that the people involved will accept unfounded criticism of their work as easily as they seem able to dish it out . . .

Apologies if I have offended anyone but quite frankly I find this all a bit of a 'storm in a tea cup' . . .

Cheers
MM

again I agree with Macciza. I need so much kilobytes (actually, megabytes) because I have not gained the needed knowledge to make my templates more elegant. For example, I want to control two different EQ plugins, and instead of using one set of objects that can be switched to either of those two plugins, I create two different sets for each - using a lot of kilobytes. I create my templates mainly with the Duplicate command, and therefore reach the filesize limit quite soon. I also wanted to combine all my specific templates into one single template with several tabs (interfaces) for each function, so that I don't have to load templates during live performance.
My experience with data loss and a quick google search taught me that my initial idea does not work; I have to use smaller templates and load often. I can live with that. Lemur offers so many possibilities that were simply not available to me, I wouldn't dare to complain. I am very, very happy with what I got, and if we get a new version with 10 MB or so per template, all the better!

Another thought: have you guys realised that many of the best Lemur templates are quite small? The brilliant AB Bundle contains templates not bigger than 160 kB! What I do mostly with my templates is controlling plugins, which could be done equally well with TouchOSC, more or less. So why not use other controller apps for the trivial stuff, and Lemur for the real sexy stuff with preset saving and physics?

Anyway, this whole discussion probably will become obsolete when the Lemur update is out.

hmm, i guess this is why i just lost around 2 days of programming osc and scripts, there was me thinking i had loads of memory left. =(

Hi Guys,

The new version with the fix should be out in a matter of days. I apologize for the inconvenience.

Best regards,
Marino.

thank you very much, marino. Indeed, in 2012, there's no need for such limitations I believe.

I very much appreciate the way you listen to your customers. This is not very common.

What is the new file size limit?
We have to know this info or there should be an exact indication in the memory usage.
I am building 3 or 4 large projects and I have to keep redesigning them in order to afford the space provided. Big problem for me is the way strings are handled and the limits in the variable sizes.
Is the variable array size limit still 256 items? Please say no!!!

I assume that both the Lemur app AND the Lemur editor will be updated? It seems like the Lemur editor is the biggest culprit, as that's where you create and save your templates (and, incidentally, lose content if you happen to go over the limit). And that certainly doesn't need Apple's pending approval to be disseminated.

Thanks for raising the limit, though - I'm looking forward to it.