Yes clearly you are well along with a set of FX. Well done (again).

Having a dynamically changeable path of effects is quite useful, if nothing else to allow users to select which filter they want to use, and to set the order. Clearly Reverb ->Compressor has a very different sound to Compressor ->Reverb

The ROMpler I'm currently working on has 4 insert FX slots (where the user can choose from over 15 different FX) and 4 Send FX slots(where the user can choose from half a dozen different FX). The DrumROMpler is even more complex, with 4 channel(Bus) effects, 4 insert(Instrument wide) Fx and 4 send FX, so it can all get a bit fraught with complexity….but users seem to like it a lot...

Very nice…

heres a list (some of which you might already have covered…):

• Reverb
• Convolution (yes I know these are both expensive on CPU...)
• Delay
• Chorus
• Phaser
• Flanger
• State variable versions of:
  Hi-Pass, Lo-Pass, Band-Pass (4 pole would be nice but at least 2-pole I think)
• Ladder Versions of:
  Hi_pass, Lo-Pass, Band-Pass
• Formant Filter
• Distortion
• Bit reduction
• Compressor
• Limiter
• Transient Manager
• Tape Sat
• Amp
• Cabinet
• Auto Pan

All this is a MASSIVE amount of work, so perhaps some way to build these as plug-able FX and others can build a market around selling us these "plug-ins". It shouldn't be too hard to define an interface, lets assume that NONE of these effects have their own UI, and their parameters would ONLY be accessible via scripting . So each plug-in would consume and return audio, and would present (in their documentation) an API to call their parameters: in some format like

set_param(fx_id,param_id,value)

Where fx_id could be either a unique ID for the FX/developer(but that limits you to one only of a given FX from a developer in an instrument) or a load sequence number. And param_id just a numeric for the relevant effect parameter..

The most important point, from an architectural point of view is that these should be load/unloadbale via the scripting interface, the way Kontakt effects are as of V5....

so we have (something like:):

load_fx(fx_file_name, position)

and:

unload_fx(fx_file_name, position)

One quick comment. To be honest I think an X/Y control wouldn't be the first thing on the list people would like. I think a range slider would be much more useful. Here you could treat it like a table, a background custom graphic only, and the range-bar and handle colours settable programatically.

Thinking even more….

Radio Buttons/Groups and Tabs would be a really really useful addition too.

.. and being able to set z-order too..which might already be there..because I haven't looked yet.

I really really would not worry about "transfer their Kontakt Libraries" - all of us who build pro libraries would gladly trade a little rework on an existing product for more usable space in the interface. Of course there has to be some limit to how big a VST interface should be, and setting the width to some silly big number seems, well, silly. But in the end if you just set the vertical limit to (say) 650 and allow that to be the dimension that can be programatically changed then setting the width to the kontkat 633 should be fine…

OK, final one(for now)…

The UI seems to be limited to 500 pixels high, I know this at first look seems fine, but truth is --- I'm already squeezing stuff hard to fit in Kontakt's 530 pixels, so 600+ would be really really nice...

..Great!

OK, good I guess I'm just trying to confirm that when you say "multiple presets you designed" this is samples and fx routing.

..and MULTI functionality…meeeh, never used them myself, but I know lots of people do...

Incomplete documentation? Clearly complete documentation EVENTUALLY would be nice, but not during this phase, no one should expect that.

I know this has been partially covered already with the idea of loadable sound sets, but here's my scenario, as usual I may have missed this in the documentation.

I'm just finishing up a ROMpler product, its in Kontakt and its got a custom UI and a custom set up for routing, effects and modulation etc. There are over 120 instruments, so the user opens Kontakt and can load "instruments" these contain the UI, the effects and group set ups, the modulations etc.

I may have this entirely wrong but as far as I can see I'd need 120 different separate plugins to get the same level of instruments using HISE… of course I may be missing the point entirely...

Well I seem to be on a bit of a roll, so I'll keep going.

I cant see where I can replace the graphics for the widgets(slider button etc.) if its not there yet then we will need it. KSP uses a stacked image paradigm - with an external txt file for the following parameters:

Has Alpha Channel: yes/no
Number of Animations: int
Horizontal Animation: yes/no
Vertical Resizable: yes/no
Horiziontal Resizable: yes/no
Fixed Top: int
Fixed Bottom: int
Fixed Left: int
Fixed Right: int

However any approach that would allow new widget types would be welcome, there's no x/y control for example, so some drawing paradigm might work…but I understand there is no Graphics Lib implemented in the JUCE implementation...so that might be a massive task.

Anyway simple bit-blitting an animation works for most situations. Of course if this is already there please just point me at it...