Page 2 of 2

Re: Using dll primitive as files encryptor

Posted: Thu Jul 24, 2014 4:17 am
by kortezzzz
When you use a Mapped File, you can do it with any kind of file - the DLL accesses it as raw binary bytes. The 'sharing' feature of MappedFiles can also be turned off by making them 'Anonymous' so that another process isn't able to hook into them.


8-) Sounds great and worth the effort of encoding\decoding.

and even the compiled code is buried inside the much larger exported VST DLL file, so you'd have to find it first.


Is that mean that the "finding matrix" is a separate dll?? so there will be the vst plugin dll, "finding matrix" dll and library dll?

And, of course, none of this helps with the security of your licenses - if someone hacks your registration code validation, your whole plugin becomes warez, and it won't matter what audio format you use then!


That's right, but close format audio library is still an advantage, as it can not be used outside of your plugin and can not be converted. so even if your plugin becomes a warez, yourr sound library is still secured and can be used in many other ways.

Re: Using dll primitive as files encryptor

Posted: Thu Jul 24, 2014 10:01 am
by trogluddite
kortezzzz wrote:Is that mean that the "finding matrix" is a separate dll?? so there will be the vst plugin dll, "finding matrix" dll and library dll?

It would be very flexible that way. For example, the encoder/decoder would be best 'hidden' inside the VST dll - but you could 'invent' two new encoded file types, so that you have the audio and the 'playback parameters' as separate files, allowing variations of patches that share the same audio files. That would make it really easy to then sell new patch libraries as 'upgrade packs' for existing customers - and it would speed up loading times when changing patches too.

Re: Using dll primitive as files encryptor

Posted: Thu Jul 24, 2014 12:11 pm
by kortezzzz
so that you have the audio and the 'playback parameters' as separate files, allowing variations of patches that share the same audio files. That would make it really easy to then sell new patch libraries as 'upgrade packs' for existing customers - and it would speed up loading times when changing patches too.


Sounds promising. Thanks for sharing. 8-) Are these patches based on SFZ format or would be anything else? A closed format (like kontakt) is really groundbreaking stuff.