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.

I used objects to manage the panels and I'm just using the namespaces for each tabs script, with each script stored in a separate file. I'm going to experiment with placing the functions into variables to see if it makes it a little easier to manage, although so far it hasn't been too complex.

There is actually a skin/wallpaper image there that hasn't come out at all in the low res GIF unfortunately. The drop down menu image is actually part of that background image, as is the heading text for each section of controls.

I designed everything in Inkscape, the knobs and sliders were rendered in KnobMan. The dynamic text for things like knob values, the articulation names, and the CC names are all rendered directly in HISE using fonts.

If we could render sliders directly that would be awesome, I haven't spent any time with the drawing functions in HISE but now you've mentioned this I think I'll have to go down that rabbit hole too. :)

A few people think this is just a service being offered that is using HISE.

8 would be perfect but I think I'm going to re-export some of my samples as stereo files so it may not be an issue for me anyway. Can HISE handle samples with more than 2 channels?

I think I'll do that then :)

Well another reason for the HISE Player :)

So welcome back :)

Swapping samplemaps is about as fast as purging / unpurging. However I would not try to load them directly from a note on callback, because the loading is asynchronous.

But if you select the sounds from the UI, you should get away without any noticable latency if you just swap a few samples.

I don't think they are still affiliated with Google, not since Chrome was released. - https://en.wikipedia.org/wiki/Mozilla_Corporation#Google

Actually it keeps a list of recent projects in the app data folder and I don't think the uninstaller removes these (the installer routines are still pretty simple). I didn't see that error for myself for years :)

Thanks for this great job!

Regards

A ballbark figure is that it takes about twice as much CPU than sample playback with a few modulators.