for now another new problem.
i have a synth group with 3 waveforms osc (osc1 & 2 for fm, 1subosc) & 1 noise osc.
if i enable FM (with scirpt on OnControl) i can enable osc1 & osc2 as carrier and modulator controled via on/off button in interface.
if i put off the button the Synth Group is soloed to Osc1 only.

is there a way to enable FM, osc1 and osc2 with button ON, and enable all synths when button is off ?

EDIT:
ok found that the synthesizer group has changed; and i hate the new one. Definitively. deactivate FM let just 1 waveform generator ON. The old one when deactivated let ALL the generators in it playing.

Yes, but this is like this since months. I removed the top bar because 100% of everybody wanted to customize it and use their layout etc.

You can use the FloatingTile component in conjunction with the PresetBrowser, TooltipBar etc. Take a look at the Floating Tile API for more information.

yes !
i also work with RackAfx (some times ago with WDL OL) and in this case using a lot of "if" and "else if" or "case" with the functions to do.
but it's pure C++
here it's JSON.
i must learn again how to work with C++ codes in hise before doing this.

i actually make the synth in hise and the BDD Juno/Dimension-D in Rackafx.

@Christoph: sorry but i resampled it (so erased the old ones and replaced it). the new works. So the problem was the wav file for sure.

@Alexaudio : Maybe just use 4 layer and use the velocity modulator to control this 4 layer like it could have 9 layer. not sure it will be as good as real 9 layers. remember that old Roland MKS-20/RD 1000 piano had beetween 4 and 8 layers and a velocity layer to map the all 0 - 128 velocity steps. that was causing (in parts) his particular sound and velocity response for a 80's digital piano.
But maybe with your real piano it will sound as a "digital" piano. So not sure.... just an idea...

I might have stumbled across a bug but as yet I haven't been able to repeat it reliably. It occurs when I load some samples into a sampler, run trim start, then decide I'm not happy with the threshold I chose so I reset the start time of all the samples to 0 and run trim start again with a different threshold. What happens is some of the samples end up with their start time being set to the same as their end time.

I checked the latest version. Now the front panel has become active!
Thank you very much

I think your confusing AU with AAX.

AU is Apple's native plugin format for Logic, Garageband etc (although VST is also supported on OSX). AAX is the plugin standard for ProTools and is available on both OS (Windows and macOS).

And yes, you definitely need a Apple system to compile AU plugins (and AAX plugins for ProTools on macOS). A mac mini will be just fine as long as it has an Intel CPU (you can't compile Universal Binaries on PowerPC CPUs). I am myself using one as main system (I am running Bootcamp for Windows so I have both OS on the same machine).

In order to compile AAX plugins, you need to register at Avid, compile their SDK, get a iLok, register at PACE for a code-signing account, get a digital codesigning certificate for Windows from Comodo (or another company), build the AAX versions and sign them using their codesign utility which I can tell you is a very tedious and annoying procedure.

RE Commercial license, I am cooperating with a few companies that are building commercial plugins, where I offer my support during development and after release. If you want to discuss the specifics, drop me an PM.

I'll take a look, but it's possible that my loop-point importer is not as robust as it should be (it worked for my samples in the past, but there is no hard standardisation for loop point definition so there are many edge cases).

It is done! And by the way, I really believe in your program. Good continuation!

awesome. could i just replace the code in the vumeter.js with this code?

Make sure you don't install Xcode 9, it is buggy as hell according to everybody...

Well, you can simply select all samples and enter a new sample start value (or right click on the field to open a big slider). Loop points should not be affected by this.

If you want to change them dynamically, increase the sample start modulation range of all samples and add a constant modulator (take a look at the tutorial how to use the sample start modulation).

I found something better than Synth.noteOffByEventId() !
Just have to assign the button to Sine Wave Generator, and then connect to 'gain'.
0=no volume, 1= volume :)
Thx :D

Here is a link to the .jucer file: https://we.tl/wj7OFfq9BC

Thanks Christoph - didn't expect you to produce this tutorial so quickly :)
I'm a bit tied up for the next couple of days stacking firewood for the coming winter, but as soon as I get a chance I'll go through the tutorial and do some experimenting.....
Thanks again!

Can you check again with the most recent build and source code? I fixed a few things regarding sample detection last week.

now i got it so it doesnt freeze everything but i get "sample directory is not existing" i have tried so many different things but what is the correct practice to have all user presets and accompanying sample maps recalled

thats understandable