Yes that‘s true. The namespace concept has no meaning outside if the scripting engine but there must be a unique ID for presets, inter script communication, etc.

Excellent

yep !
i decided to change my filters. Because i had subtractive (with another subosc - 12 and noise osc) + FM. But in fact FM has no filters. so i put all waveforms in one synth group + filters and separate FM (2 sine osc) without filters.

for now i have keyfollow + polarity (because it also didn't work in FX filter mode)

I shall test and report back

Its WORK! Big Thanks !

The font goes in the images folder. You need to use the loadFont command in your front interface script to include it with the instrument. Make sure you own the license to use the font or that it is royalty free or similar :)

Take a look at my github repo, I have some modules for colouring keys (the playable range script) and switching articulations. You can use these as is or use them as a jumping off point for your own scripts. - https://github.com/davidhealey/HISE-Scripting-Framework/tree/master/v3/modules

yeah if you could put some example code for the output meter using a vu meter filmstrip that would be great ive been pulling out my hair the last two days trying to get it to work lol. as far as the compressor i wish i knew the exact coding process to birng dsp code into hise there are tons of great things at musicdsp.org

I recently changed this so that you can call this in the onControl callback which is required when you want to create modulators dynamically, so no it shouldn't cause any problems.

I think you can't do it in the MIDI callbacks though (and it would be pretty stupid to do so), but I'll have to update the API docs.

No rush, I'm only using it as a sub-modulator and restoring the parent modulator restores the note number modulator correctly

I also had this idea in mind (that's precisely what the company URL field in the User Settings dialogue is for). I think the best way for this is adding an About page floating tile, which also shows the registered e-mail address of the user along with some other useful information.

Yeah that makes sense, duly noted!

*facepalm ;)

CCs that are assigned will not be passed to the engine in order to avoid side effects, but the onControl callback should be executed (so you need to call repaint() from there).

That's a good idea, and it will offer a working example too. I shall do it that way.

I see, I thought it wasn't there because it's not showing up in my API list

0_1503830264859_Capture.PNG

Thanks Christoph, mystery solved :)

Yes, this is possible, but highly complex and subject of many proprietary algorithms. The problem is to resynthesise the samples without loosing the sonic quality.