crystal synth is making alot of noise lately.I just picked up the new issue of electronic magazine and its been featured in the download of the month section
cant wait to get my grubby paws on 2.1

BTW (and not exactly the same subject)
whats up with klangformer? wasnt it due for september?

opiadream wrote:

BTW (and not exactly the same subject) whats up with klangformer? wasnt it due for september?

We have some problems with the copy protection of the Klangformer. Some host applications (especially Cubase) don't load the plugins with our low level copy protection or make even other problems therefore.

The Klangformer final BETA is out now since weeks. But finally we cannot release it, because this stupid copy protection fault.

To protect DLL's with the conventional effective mechanisms is very difficult, because it seems to confuse the host applications, or these simply don't load protected dll's or discard these while startup and and and...

But to implement copy/disassemble protection is absolutely necessary.
Our commercial release of the Rebel2 was shipped to the WAREZ szene three days after release! Even our FREE NIN!jA was provided within an complete warez installation package under the motto: "We proudly present..."!!! Perhaps they did'nt believe, that NIN!jA was really free!?...
At least is was an massive copyright injury.

It indeed is very sadly novadays, that developers are forced to invest more than 10 percent (or more) of their development time to find some useful copy protection schemes to protect a work of more than one year intensive development and resurch...

Sometimes one could completely lose the desire there.

!j development

how about a special patch with an activation code that registered users download to remove the limitations.been there done that?

opiadream wrote:

how about a special patch with an activation code that registered users download to remove the limitations.been there done that?

This is just the current problem. Because this "patch" can be removed with ease by the crackers, if the *.dll cannot be enveloped with several encryption/anti dissassembling mechanisms and other nice things.

It seems to be the encrypion, which makes the miority of problems with the host applications or vice versa. So we have probably to hardcode some things now and search for other ways...

we know, there is no absolute protection for software. But we will try to make it not so easy as the last times for the "szene" and for those customers, which ship software to the szenes after purchase. Never the demos are cracked (this is not possible mostly), but the full versions.

!j development