Personally i see it as an add on to JUCE, so follow the licence scheme, flat fee £500 for indies £1000 for companies (Multi seat) if i remember correctly.
Charge again for V2, just make sure it has valid wanted features, same for v3 and so on.

I understand completely that Chris needs to get paid, and that is of course only fair, however, the margin between getting paid and this disappearing and being just a hobby project is very slim, maybe Chris has not been on the scene and seen all of these kinds of developments appear and then just fade away because the sales that were expected never happened and the developer lost interest.
Having a huge fanatical user base that contributes tutorials/scripts/code/UIs and so on, will make HISE a valuable commodity, however, if you charge the ground roots user out of this (Which is what is proposed) you can forget those contributions, because
1 it will be mainly companies and why would they share (They never do)
2 Even if it was some indie developer, they have paid a lot for one app, why should they share their knowledge.
And lets be clear here, there is zero community right now around HISE, pretty much just you and the developer, that really is not good, considering how much of an impact it could have had.

At the prices suggested it is in to mid level territory, you are asking companies who are actually full time to rely on your backend, Kontakt is proven time and time again, so that is the platform these companies are going to go for, there is little to no doubt about that, I work with quite a few, and can tell, you, they have zero interest in moving away from Kontakt right now, their skillset is in Kontakt, their sales are in Kontakt. they trust Kontakt and for something else to even register on their radar, it needs to have been around for a long time and be offering something special.

@d-healey
VST, not VSTi, we have a VSTi, not a VST.
VSTi = Instrument.
VST = Effect.
To develop effects you need an environment that will work as intended, the VSTi that we have now, has no audio inputs, so the only way to test any effect designs (VST) is to load a sampler and use audio from that, we need a compile as VST (Audio inputs and outputs) added to what we have now, VSTi.

VST 2 supports inputs on VSTi, in fact the only thing it offers that was not achieved in VST 2 is its ability to create channels for chains, everything else was already done in 2 with extensions by various developers.

Having said all that, VST 3 had major issues with presets according to a lot of developers and took a long time to mature in to an acceptable plugin format, it is only just now becoming a viable alternative, 20 year old tech in this case means matured to the point of ultimate reliability.

OK, going in circles, just wait till i do a screen recording to show it ;)

Ok i think i see why this has gotten messy, you are talking about a Mid/Side recording, so Mid is on one channel and Side is on the other, I am talking about having the ability in an effect plugin to effect only the mids or only the sides from a normal stereo signal.

I think @orange wants what i am suggesting, Mid/Side separation for a standard stereo signal.

@orange not right now, im away from home mobile, after the weekend i can try, but i dont know HISE that well right now, but i will give it the good old try ;)

Just double checked this in Reaper and it created Mid Side perfectly, so must be some issue with the way HISE is summing them or something ?

Take your stereo path, pan both left and right channels to centre so that it becomes mono, this is your mid path, take the mid path and invert its polarity (Phase, been a while since i did any code at all, think it is signal * -1) and sum it with the original left and right channels and this will cancel out the mids and leave only the side path ;)
Now you have a mid path and a side path.

@d-healey
I'm a complete newb with the compiling side of things, but it would be interesting if we could get a VST going for sure, Making some basic effects would be a great way to learn construction in HISE i think.

@Christoph-Hart
Well yeah, KVR has a lot of users, and i would suggest with attitudes like the above, not to post there, eaten alive springs to mind hahaha.
@Jay
All i did was ask if it was mandatory, its not, that's cool, also very cool that you will, personally I will not overtly mention HISE, I think it is disrespectful to HISE (My opinion, not trying to tell anybody else what to do) I intend to push HISE through promotion of HISE itself ;)

Is this expected behaviour?

@orange That simply isnt true, SE is 32 bit/64 bit/VST3 and AU.
Synthmaker is updated on a near weekly basis, but is a hobby project now of one of the developers, not a real commercial enterprise.

It is very sad that any comments by people struggling are met with the kind of comments shown here though, sarcasm and elitism do nothing at all to grow the userbase, and my comment stands as fact, a LOT of people have picked up HISE, messed with HISE, gone straight back to Kontakt, just because you do not like that fact, does not mean that it isn't true.

The one thing that HISE does really well, force you to give up and go back to using Kontakt, SM/SE etc, I have brought up these issues before, but teh website still never gets updated, and unfortunately that means that just getting HISE set up before even doing any design is "The journey to the sorcerer" it feels like some nice side project for people who are just bored with using full JUCE, sadly not the goal the developer was aiming for.

https://docs.hise.audio/introduction/{LINK0}

https://docs.hise.audio/introduction/{LINK1}

https://docs.hise.audio/introduction/{LINK2}

https://docs.hise.audio/introduction/{LINK3}

https://docs.hise.audio/introduction/{LINK4}

https://docs.hise.audio/introduction/{LINK5}

There you go, as i said, try the links, that is the links in the documentation installation page to the GIT, to the compilers, to Steinbergs website, to intels website.

Pretty much the first thing that any new user is going to try and do, install.

No of the links work, just go to the very start of the documentation, try to go to the git or the compilers, you aren't going to get many people on board with broken links everywhere, I know it is more important to work on HISE itself, but honestly, basic stuff like that needs to be right.

@d-healey said in PACE (iLok) have acquired JUCE:

proprietary

Well, commercial is generally the point.

@d-healey said in PACE (iLok) have acquired JUCE:

GNU GPL

Yes but if they stop selling the licences for the current codebase, you cant use it to make commercial plugins, right ?

I doubt very much that they don't intend to push heavily and/or even force iLok usage, it could even be as simple as "JUCE is now free to developers, but you have to use iLok" acquisitions are made to make money, and if the business of iLok is more valuable than the business of JUCE (Which you would have to assume it is given they where able to procure JUCE) then JUCE will be used to leverage more iLok business.
How much this affects HISE in the long term is debatable, I would have to assume that Christopher already has back up plans and such if anything nefarious was to happen with JUCE, there are alternatives for him to implement if he needed to.

https://juce.com/discover/stories/juce-announces-acquisition-by-pace

Have to see how this one plays out, but i would expect some changes to JUCE licencing.

This has been requested for a long time, a VSTFX version of HISE for making effects.