@d-healey I like the design and how it's build. It makes a lot of things better like the license activations or even has a host management which I use to manage my client-host logic. Also, the REST API is very secure and provides a login / token feature which others don't have. Same as trial! very comprehensive and just works, I have no complaints in a 500 ish user sample.

To round it up, they provide such a good support. They are always helping me if I need to modify something or if I just have a question.

Also I've sent some suggestions and some cool features are coming up, like for example license distribution/redeem system through plugin sellers without affecting the order system.
more info here https://agency.enwikuna.de/store/enwikuna-license-manager-pro/

Cheers

@bendurso Hi again! Doing a little update here. So we got a few great updates since last we spoke.
Now you can have a list of distributors to sell your products in other stores like plugin boutique or thomann etc. and make the whole process automated.

Also Offline activation now is possible, remote deactivation of hosts from the users account, license blocking and many other little things that can be used like offering free plugins through the distribution system.

Soon I heard they'll add a really detailed analytics to collect necessary data to improve the products.

Feel free to try it in a test server using Postman!

@bendurso Oh nice I'll look it up! I always wondered what do companies use to build there synths (arturia, roland) - probably their own or an open source one that they build on top of.

I'm really wondering what to suggest to my dev for this first synth that I want to build (potentially NKS compatible)

@d-healey Did anyone ever tried? I'd love to have a few examples if you have some

Hi there,

Would it make sense to build a synth in hise and make it NKS compatible so it can load seamlessly in Kontrol keyboards?

Many thanks

@bendurso Hi again! Doing a little update here. So we got a few great updates since last we spoke.
Now you can have a list of distributors to sell your products in other stores like plugin boutique or thomann etc. and make the whole process automated.

Also Offline activation now is possible, remote deactivation of hosts from the users account, license blocking and many other little things that can be used like offering free plugins through the distribution system.

Soon I heard they'll add a really detailed analytics to collect necessary data to improve the products.

Feel free to try it in a test server using Postman!

@d-healey I like the design and how it's build. It makes a lot of things better like the license activations or even has a host management which I use to manage my client-host logic. Also, the REST API is very secure and provides a login / token feature which others don't have. Same as trial! very comprehensive and just works, I have no complaints in a 500 ish user sample.

To round it up, they provide such a good support. They are always helping me if I need to modify something or if I just have a question.

Also I've sent some suggestions and some cool features are coming up, like for example license distribution/redeem system through plugin sellers without affecting the order system.
more info here https://agency.enwikuna.de/store/enwikuna-license-manager-pro/

Cheers

Hi guys, a little update 9 months later, the enwikuna is clearly the best server based non centralised licensing solution. The new version just dropped with some really amazing upgrades.

If anyone wants help with the integration with Juce, feel free to reach out to them, there's a custom juce project that can be purchased that will help you get a head start on your software licensing journey.

@d-healey there's a migration tool from license manager if you want to check it out in your staging website!

@d-healey sounds good, so in the doc, it says if it's bigger than 50mo you're better off not putting them in the binary.
Seems logical!

Hi everyone!

I'm working on a project using a lot of graphical assets. To be able to draw them fast i'm using uncompressed pngs.

I also have a video I want to call for a cool transition. That makes a lot of assets, putting them in the binary would mean having the same assets for VST3, AAX and AU.

I'm thinking maybe it would be best to not include ressources in the binary but in a support folder? Thoughts?

thanks guys, I'm working on a distortion emulation, so avoiding aliasing is a must, I want to offer the option of 4x 8x and 16x. I'll just need to figure what's the best filter to use in this case.

Did someone experimented with the filters? The reaper And aliasing seem to be quite good, I wonder what they're using.

Hi guys, interesting subject. OS for higher than 16x can really be interesting for heavy saturation processors, i'm guessing 32 and 64x would completely remove any aliasing there is even in heavy situations.

Is there a way to overcome this Juce limitation?