Lennard Apathy Summary For Potential Customers

[cis-didge]

Please tell me ..what is it all about this memory leek???...i have used sylenth in Live on a pc, sometimes from 4 to 6 instances on just as many tracks. I have never observed any problems in doing so..so where and when could i eventually run into problems because of that memory leek

only if you close and reopen the gui
i never need to close the gui, do you ?

does that mean that if i save a song i am working on half the way close Live and reopens later, it would give me problems...i have never observed it could do so

[D N A]

This is and all ways has been about the memory leak, dramatically effecting users for well over a year

No it doesnt.

Do you really believe that all these great producers use broken software with bug that "dramatically" affects them ? Dont think so. It affects kvr kids mostly... Sorry, for being harsh but it's really getting boring hearing about memory leak. How much memory do you have, 256 mb ram ????

[Mac Hine]

It affects kvr kids mostly... Sorry, for being harsh but it's really getting boring hearing about memory leak. How much memory do you have, 256 mb ram ????

I dont care about how may great producers or pro's dont have a problem, I do and pro's are not here! I also payed money as the pro's did

I say this allready in IBTL thread but I repeat it again as it propably was not the "best of the threads". Anyway:

"I worked with a song on weekend. After couple of hours FLStudio crashed and work was lost as ofcourse I forget to save... Then I wonder what happend and after couple hours it crashed again. Then I noticed that this memory leak issue is filling the memory. I had 500M free but it filled it in 1-2 hours and when there was no free memory, sound and FLStudio hanged and I hade to stop it with endtask.

I had 6-7 Sylenths and I propably do quite bit of jumping between them which easily seems to fill up the memory. I go and buy some more memory as workaround but I would hope that we would get a fix to this soon. "

Well, my point is not to complain this over again but I think the problems caused by this memory leak was missed on ibtl thread. Usually I have about 1G extra (after project is loaded). I dont think that answer to clear bug should be: go buy some more memory. I dont need more memory to anything else but for this bug.

I have to say that Lennard has been very helpfull and fast about other issues and the patch support has also been great. So complaints about he's not communicating are little bit over-reacted.

About actual problem: Lennard says that it should not crash a host so maby the crashing is caused some other plug that I use. Sylenth1 is however part of the problem as it is responcible for filling the memory which crashes some other plug?

I know that some of you are sick of hearing about memory bug but dont bash the users who are affected by it. It is not a catastrophe (except when I lost 2-4 hours of work) but it is not going to way by saying that you should not be affected by it as pro's dont

[carrieres]

is this memory leak relative to windows XP SP2 only ?
because there is a known bug and a patch to fix it

[D-Fusion]

is this memory leak relative to windows XP SP2 only ?
because there is a known bug and a patch to fix it

No it is not related to the Sp2 bug it happens in Sp3 and windows 7 also.

The only workaround so far is to minimize the sylenth1 gui instead of closing and reopening it again.

Synapse Orion is not affected by this bug because it only hides the gui when you close it instead of closing it like other hosts do.

What i would like to see soon is a working 64bit version for windows 7

[carrieres]

i work with orion
so, the workaround is not so difficult to apply

[D-Fusion]

i work with orion
so, the workaround is not so difficult to apply

Same here

[Happy Frog]

DNA,

Very professional response.

And if professionals use broken hardware, why wouldn't they use broken software, are you a professional in the know or something.

[TotcProductions]

sorry, I know this is taking this off topic, but I can't understand the crapping on morphine that goes on.

Atmospheres

Keyboards

SFX

RealisticSynth

That's all resynthesis...aided slightly by envelopes and the noise player. There's really not much out there that compares. I suppose folks just don't know how to use it .

Peace

[pikadilly]

I don't understand. The problem of memory leak has been reported for years. The developer done and promised nothing except asking whistleblower to buy more memory. Does he actually own the source code and clear all proprietary issues?

[GMusic]

While the memory leak issue doesn't affect me much at all, if a developer says he's going to do something, I'd sure hope he did it and as soon as possible. If not, then at least keep customers updated on a monthly basis at least. Honesty is good.

In a way, it's silly to see some customers defending Lennard. Every Customer have every right to complain if the product is faulty and a said update "soon" hasn't come in months (years?). Other customers who aren't affected so much by the faults really don't have a right to silence a rightfully angry paying customer of which are affected greatly by a fault in the product.

Just because something isn't a big deal to you doesn't mean you can silence others who do believe the issue is irritating/deal breaker.

Just respectfully stating my opinion. If I missed something lately, fill it in. I don't check here much at all, because there's really no point as far as I can tell.

[liquidsound]

This may be my first post here... (Maybe I'm the one with the memory leak!)
Anyway I remember we had the same issue at energyXT when Jorgen completely vanished and we all were bitching until finding myself sleeping on the PC keyboard at the forum.

What happened it's now history: he was working out a business deal and for whatever reason he could not disclose it and he HAD to dedicate his time for it.

I often have a feeling that the same thing is happening with Lennar.
After all Sylenth1 is a supreme synth and if I had Lennard's knowledge and skills I certainly would work on new synth ( as u-he actually does) or a deal with some investors to create something more than just a Plugin no matter how great it is.
In business you need keep moving.
"Standing still" is not "Still standing" forever.

In conclusion I regards complains as one's right of opinion and sometime if you are not sure of the future of a Synth just move on like I did with XT which came back to action and it's a great Daw but, because of doubts I had of its future, I discovered MuLab and with the recent v3 upgrade I will never look back.
So Paul, bite the head of the snake. Buy it, enjoy it as much as you can or move on. That's what I call Free Will.