The advantage Gorilla has is that it's very similar to Kontakt, even in its scripting. (Mind you, I haven't actually seen it for myself, this is just what I've been told.) And it's really efficient, in terms of loading times, voice counts, and all that. (Much faster than UVI, but I'm not sure how it compares to Kontakt.)
err... its not as similar as you think, my experience is that its about as similar as HISE (actually a bit less intuitive but I'll put that down to my addled brain).
Plus, staying close to Kontakt allows a few shortcuts. For instance, we don't really even need to build a drag&drop GUI for the mappings, since we could get Garth (Chicken Systems) or someone to build us an equivalent to his Translator app. So we could build in Kontakt, then it's translated into data and ported to our player.
Good grief I wrote this in an afternoon for porting from Kontakt to HISE sample maps: You take a kontakt instrument - run a Creator Tools script over it and out comes HISE Sample maps ready to load. So this is done already for HISE.
The *important* point here wasnt that I could do this in Creator Tools ( it was nice but I had to learn LUA at the same time ) - no the really important part was that the HISE Sample Maps were open and human readable, they are XML (an open well understood format) the sort of thing NI will never do for their data formats, and that you will *need* to do for your sampler MIKE
The lesson I learned: if the tools are properly designed and open - you can do this sort of thing easily yourself.
The user interface is a similar situation, where there are already third party UI builder apps, including ones that direct-port to Kontakt, so that could be our front end for designing GUIs.
Yeah I wrote one(in python) that ported Skinman files to Kontakt interfaces(a pile of ugly KSP) for my own work, I used it for years - it saved me acres of time. So when I got to HISE one of the first thoughts I had was "well now, lets see what the format is for UI layout is here, and extend the UI Composer I have..." took me about ten minutes to see the UI format was waaay easier to understand in HISE.. "woohoo this will be simple". Luckily I spent an afternoon in the UI builder *inside* HISE, and realised "hey, this UI builder is already more powerful and better than the external system I have, come to that better than *any* UI builder in or out of any sampler platform!!"
The lesson I learned: in HISE you dont NEED another UI builder - its already there.
Effects can be licensed. Especially now, when there's so much competition, so deals would be easier to make. Even with time stretching (TM-Pro), I'm told everybody licenses Z-Plane, so in theory, we can cross that off the to-do list as well.
Have you looked at the licensing price of Z-Plane? Have you ever built an effect? The first one I built took me two weeks, and it was rubbish, then I started using ScriptNode - it took me 2 days and it was pretty acceptable. I installed and integrated Faust - and built another - it took me an afternoon and it was commercially viable. I've built 20 effects this year - yeah if you understand DSP thats *insane*, especially as most of my time was spent on virtual instruments....
P.S Time stretching is already available (as part of the core package) in HISE...
The lesson I learned: With the right tool set already integrated then there is no reason to pay a 3rd party to either build it for you or to license their code(which you will then have to integrate).
For scripting, KSP is based on PASCAL, which I think is public domain, plus NI doesn't own those shortcuts on Sublime text that we all use. So we could create a scripting language everybody's already comfortable with, without legal worries of infringement.
HISEScript is based on Javascript - so its as public (if not more so) than Pascal, and you dont need any 3rd-party extensions in some 3rd-party editor.
This is all very early, though, and I don't want to come across like I've got it all figured out. I don't, and I fully understand everything's easy ...
in theory.
Mike, we need to have a conversation - before you spend your $1M or any part of it. I know from first hand experience you are a good man and I dont want to see you throwing your money away....and from where I'm standing this looks pretty much exactly like what you are proposing. Happy to be proved wrong.