If you select the parent (the chains) you can also use Ctrl+V

Time to make a hackintosh me thinks

Hi and welcome to the forum!

Also +1 for using the new question feature :)

Alright, should be online now...

That's how I think it should be too, so we'll interpret the GPL in a sensible way for it to apply to sampling, which is something it doesn't cover explicitly.

Aha now I get it!

Ah I forgot to hide this behind the USE_TURBO_ACTIVATE macro. I just committed the fix. I checked and the demo_project builds successfully as Standalone on OS X.

Yeah its in a terrible intermediate state and my internet is broken. I am making a new "official" build version tomorrow

It's smooth like Eyes...

They can be one character, but in this case your dynamic token mf also contains a m. However I just fixed this so from now on you can use your short names :)

But VS is so slow and big :p okay, I'll stick with VS to keep my sanity.

Nice! You might want to add an option to specify the index so that you can build crossfade tables for each group more quickly. This is a screenshot of three linear XFades with different indexes:

0_1488133216539_Bildschirmfoto 2017-02-26 um 19.18.42.png

EDIT: Nevermind, just realized you are doing this already on different modulators.

BTW, did you know you can copy & paste tables? Just select one (so it gets outlined), Ctrl + C, select another and press Ctrl + V.

You could add a dummy table to your script which can then just be used as copy source for all kinds of modulators.

The Ahdsr is indeed a bit slower, but it should not really matter. If you don't need it, just use the SimpleEnvelope, but don't be to scroogy with your CPU cycles here :)

haha that's awesome, I'm glad they were helpful

Excellent stuff

Excellent, glad it wasn't just me being mad

Great!! I'm going to try that, thank you for your effort, it's really appreciated.

Actually I am thinking about renaming the script language to something like HiseScript, since there are many language differences to traditional Javascript (reg, namespace, include, inline function, local just to name the most important ones). On the other hand it's a valid superset of Javascript (so almost every Javascript construct should work in the HISE implementation so it's not "Yet Another Script Language".

About the classes thing, most encapsulation needs can be satisfied with the namespace concept that David sketched above, however if you are looking for any kind of inheritance or even polymorphism you're out of luck (to be honest, I don't know ECMA 6 well enough to know what's going on there).

Could you describe what kind of thing you want to achieve using classes? I am positive there's a solution in the current HISE implementation.

Hi Marco and welcome to the forum!

A Project is just a folder which contains a specific subfolder structure and contains all files so you can easily transfer it to another computer. This is persistent so if you close and reopen HISE it should stay in the same project.

A Preset is the actual instrument and you can save it using File - Save and so on. I admit its a little bit poorly named - maybe "Patch" is a better name for it...

Once you created a project it will automatically save the Presets in the Projects subdirectory Presets and you should be able to load it from the file menu.