The problem I see here is that you have to define the tempo with one value only (so it can be connected to one parameter).

But to be honest, it is nothing more than a lookup table of factors to determine the time and you can implement a system like this for yourself pretty easily.

Yeah, there are only two, but since you can morph a panel into a button with just a few lines of code I'd like to keep the button rather simple.

I think this would be a case where it's better to just use a multidimensional array - the MidiList is a pretty small container which gets it's performance / usability advantages by limiting on numbers (its even not storing floating point, but simple 16bit integers). Making its slots dynamically resizable would defeat any performance advantage - you just end up with another multipurpose container type like the array :)

It would also be helpful if we could retrieve the current purged/loaded status of a mic position

Yes, although I'll make it Ctrl+Alt+C/V (Ctrl+Shift+C is already in use for creating a script variable declaration when a module is selected.

Ah that's a good idea!

Aha I think I get it, I'll have to play around with it. I don't have an example in mind, it just occurred to me that SVG might be a good format for a scalable ui

This looks awesome, I shall try it out soon. Thanks :) you work very quickly!

Ok, I'll give it a go :)

Ah cool, I was trying to get the text property I didn't think to try the value.

Thanks, I've just built it (first time I've tried) and it seems to be working .

Here is an example of the kind of thing I'm hoping to do with such functions:

In this example I had to specify each modulator in the script but it will be great when this script can just inserted in the container and it will add the modulators itself.

Yes, this is reasonable. The method will be Synth.isTimerRunning() (the JUCE Timer class has a similar method so it's pretty easy to add this). I'll also add Synth.getTimerInterval() if I am at it.

This is excellent :)

Well, there is only you and me until now :)

I might still take advantage of your system and script a midi mixer vst to use in Max, since their JS doesn't run in the high-priority thread.....

Yes, 256 or even 128 should also be no problem (things get a little bit tight at 64 samples).

Ah that's good to know. Having all the callbacks in one main file will be good and then other functions can go into external files.

Yea I don't think that would be a problem, if RAM usage becomes an issue I'll tackle it with the other method.

Alright, I'll see what I can do.

There is already a automatic update check for HISE itself (I think since Build 620), which does exactly this.