General
Lemur editor HUGE memory bug
Started by m127 on .
Sign in or create an account to join the conversation.
So I have been porting my original Lemur templates to test functionality in the iPad version, etc.
I found what seems a memory bug.
facts:
1. The editor memory meter shows very low consumption on my Lemur templates, which in the original Lemur hw and editor would take nearly the entire memory, but here it only shows between 13 and 15% ---that would be GREAT news if it wasn't because...>
2. The Lemur editor AND the iPad WILL delete objects ON THEIR OWN with no warning whatsoever... I mean what the total fuck!!!!
3. This seems to happen when the memory is fully consumed, BUT with the fucking meter not showing more than 15%, when will I know I am reaching the memory limits?
So, questions:
1. Compared to the original Lemur, which has 4mb, what is the memory limit in the iPad version?
2. Why in hell the Lemur editor or the iPad won't warn shyte before deleting objects and entire and partial interfaces (pages) on their OWN!!!!??
Reproduce steps:
1. Create a template and put your mom there too if you can; that is put everything you have and try to consume as much memory as you can. BUT try to divide the contents into several interfaces (internal pages) within the template (name them "1", "2", etc. so you keep track of them).
2. As you keep adding stuff, everything seems fine, and the meter shows you "paradise", ie, the consumed memory is apparently very low.
3. When you reach 16%-20%, save your project somewhere.
4. Close the Lemur and open the project to see whether the whole thing is there.
5. When I do that here, the last interfaces (in alphabetical order) simply disappear on their own, and the very last one might show only some of the objects (that is, the project is AUTOMATICALLY TRUNCATED FUCK!!)
memory meter 18 PERCENT.JPG
new used memory when the project is opened again.JPG
I lost 48 hours or non-stop work due to this fucking bug. OMFG
Other than that, the porting is exceptional, good job by Axel and Liine.
Hope you guys can sort this one out. I mean, guessing when to stop adding objects to your template is too much to ask, honestly.
Also, if could reinstate the keyboard/mouse functions, that would be great. Not sure why you removed them, that was very bad news here.
I am pissed at my lost work, but I am happy because of the obvious effort you put in the porting.
Must have been a titanic project.
I have supported the Lemur project for a long time.
I own 3 original Lemurs and now the iPad version.
lmk guys please.
.
I found what seems a memory bug.
facts:
1. The editor memory meter shows very low consumption on my Lemur templates, which in the original Lemur hw and editor would take nearly the entire memory, but here it only shows between 13 and 15% ---that would be GREAT news if it wasn't because...>
2. The Lemur editor AND the iPad WILL delete objects ON THEIR OWN with no warning whatsoever... I mean what the total fuck!!!!
3. This seems to happen when the memory is fully consumed, BUT with the fucking meter not showing more than 15%, when will I know I am reaching the memory limits?
So, questions:
1. Compared to the original Lemur, which has 4mb, what is the memory limit in the iPad version?
2. Why in hell the Lemur editor or the iPad won't warn shyte before deleting objects and entire and partial interfaces (pages) on their OWN!!!!??
Reproduce steps:
1. Create a template and put your mom there too if you can; that is put everything you have and try to consume as much memory as you can. BUT try to divide the contents into several interfaces (internal pages) within the template (name them "1", "2", etc. so you keep track of them).
2. As you keep adding stuff, everything seems fine, and the meter shows you "paradise", ie, the consumed memory is apparently very low.
3. When you reach 16%-20%, save your project somewhere.
4. Close the Lemur and open the project to see whether the whole thing is there.
5. When I do that here, the last interfaces (in alphabetical order) simply disappear on their own, and the very last one might show only some of the objects (that is, the project is AUTOMATICALLY TRUNCATED FUCK!!)
memory meter 18 PERCENT.JPG
new used memory when the project is opened again.JPG
I lost 48 hours or non-stop work due to this fucking bug. OMFG
Other than that, the porting is exceptional, good job by Axel and Liine.
Hope you guys can sort this one out. I mean, guessing when to stop adding objects to your template is too much to ask, honestly.
Also, if could reinstate the keyboard/mouse functions, that would be great. Not sure why you removed them, that was very bad news here.
I am pissed at my lost work, but I am happy because of the obvious effort you put in the porting.
Must have been a titanic project.
I have supported the Lemur project for a long time.
I own 3 original Lemurs and now the iPad version.
lmk guys please.
.
I had the same problem ..... wasted days ......
I can confirm the issue on my end.
Note however that this also happened with the original Jazzmutant Lemur editor, both PC and Mac versions.
Of course, now with the iPad that has bigger memory, users will definitely want to use more pages than with the original JM Lemur. I am looking forward to see a bugfix.
TN
Note however that this also happened with the original Jazzmutant Lemur editor, both PC and Mac versions.
Of course, now with the iPad that has bigger memory, users will definitely want to use more pages than with the original JM Lemur. I am looking forward to see a bugfix.
TN
Yes I can confirm the bug seems to happen in OS X and Windows versions of editor.
I wish I had read this post before yesterday when I was going nuts trying to figure out what
happened to my vars/functions that were working.
Seems the editor saves the file and truncates around 524K.
But while in memory, everything seems fine. Prob is when you load your work back into the editor from that broken .jzml
It doesn't even write the end XML tags.
My global variables and functions were the first to be chopped because they are always at the end of the file.
If you're not sure if you have hit the limit load the .jzml in a text editor (or tail in un*x). If there is no end tag of </JZML>
then it is broken.
save your work as new filenames and check them. I lost limited amount of time.. 2 hours only because i save and had exported interface sets as libraries. but THEN lost 4 hours trying to figure this insanity out and writing perl scripts to recreate some of the variables and containers lost for future time savings.
I'm having too much fun writing new code for Lemur iPad, so please please fix this save bug guys!
cheeers~
J
I wish I had read this post before yesterday when I was going nuts trying to figure out what
happened to my vars/functions that were working.
Seems the editor saves the file and truncates around 524K.
But while in memory, everything seems fine. Prob is when you load your work back into the editor from that broken .jzml
It doesn't even write the end XML tags.
My global variables and functions were the first to be chopped because they are always at the end of the file.
If you're not sure if you have hit the limit load the .jzml in a text editor (or tail in un*x). If there is no end tag of </JZML>
then it is broken.
save your work as new filenames and check them. I lost limited amount of time.. 2 hours only because i save and had exported interface sets as libraries. but THEN lost 4 hours trying to figure this insanity out and writing perl scripts to recreate some of the variables and containers lost for future time savings.
I'm having too much fun writing new code for Lemur iPad, so please please fix this save bug guys!
cheeers~
J
have they fixed this yet????
We have raised the file size limit in an update, which is pending approval by Apple. Hopefully it should be out pretty soon.
Subject: Re: Lemur editor memory bugI have never really looked here for Lemur discussions and do not wish to start now . . .
It would be great if people could keep it neat and post in the main Lemur discussion instead.
This would have been answered far earlier if you had
Cheers
MM
PS Seriously, the original issue is not really a 'HUGE memory bug' - it's a file-saving issue . . .
PPS This topic was originally in LiveControl Support forum - thats why my comments might seem weird . . .
PPPS It would be good if the HUGE could be removed from the title imho . . . Don't want to scare anyone off with bad information. . .
When you lose all your work without warning, it qualifies as "huge."
It's a huge issue to me too. I can't believe they let this bug through. Such a waste of time.
although I also fell victim to this memory limitation (many hours of work lost), I wouldn't call it a bug or huge bug. It is what it is, a memory limitation.
Subject: Re: Lemur editor not saving properlyI 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' . . .
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 limitWhen you lose all your work without warning, it qualifies as "huge."
If you only need to push it a little further it can be gotten around if you are prepared to hit a text editor . . .
A huge personal issue maybe, but not a shouted 'huge' 'memory bug' - which it isn't see above ...It's a huge issue to me too. I can't believe they let this bug through. Such a waste of time.
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.
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.
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.
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!!!
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.
Thanks for raising the limit, though - I'm looking forward to it.