Ok, now I see. Thank you mate :)

It works great! Thank you so much for your support.
I've used my plugin in FL Studio 12 with all buffer sizes; from 256 to 2048, it works on all of them :)

You are so fast for problem solving :) thank you so much...

Brillliant! golly that was fast response, very cool. Boots! Excited to tweak around now. - Thanks!

in the dynamic example:
https://github.com/christophhart/hise_tutorial/tree/master/DynamicsFX

in thye musicbox example:
https://github.com/christophhart/hise_tutorial/tree/master/MusicBox Tutorial/Scripts

catch the vu meter in these examples.

I am finally able to connect Rosegarden MIDI playback port to HISE! I just have to use the standard Midi through-port 0, easy right? Strangely all the other virtual ports created are not seen by HISE, but this one works!

Thanks so much for the help! hope that this post will be useful for other Rosegarden users. Thank you for the nice project!

ok.
Inside HISE should be great.
i making a drumbox and want to let the user changing the output of each categorie (kick, snare, et. ...)

maybe later....

thanks ! ;)

Great, that's exactly what I wanted. Sometimes having an example is the best way to learn.

P.S. Did you receive my messages? I have not received any complaints? (I am sending you on the email box)

Ok working well , thanks very much Staiff for your feedback, you re the best;)

1- Go to setting.

2- Embed audio file in Plugin = Yes

3- Export.

(Almost) everything is possible as soon as you don't use the processorId / parameterId properties and implement the logic purely in script.

These two are just for 99% of the cases where you just need to control a module without having to write so much boiler plate code.

yep !
i put it in the syn thGroup midi section and it works !
but the legato glide script from David don't work if legato retrigger is On.

just this detail.
but yes the retrigger works ! :D

Fixed !
problem found/solved by myself.

hey Dave,

It seems that you put the code into the false callback. I ran into this issue too some time ago. There are two callbacks that have a quite similar name what can be mixed up quite easily. onController and onControl. While the OnController manages the CC inputs the onControl serves as the callback for the GUI-Widgets/Elements.

And BTW: be a bit lenient with the tutorial in its current state. There have been many changes in HISE in the last months and not everything seems to be up to date.

best,
d

I like it, very simple!

Whats wrong with double left click?

Edit: Scrolled up, got it ;)

Ctrl Click is using fine mode, so thats not free.

You need to apply some sample start mod (s.mod) time to the samples - just like with Kontakt. If you want to use the whole sample then just set this to the full length of the sample but then the whole sample will be loaded into RAM.

Well, kind of. In C++ you have two ways of adding libraries to your app, either via static linking (which takes a .lib / .a file during compilation and embeds this into your app or via dynamic linking, which compiles a .dll / dylib which is loaded on runtime). There's also a third way, which is simply taking the source code of your effect and add it to your compiled plugin before compilation (this is why there is the AdditionalSourceCode folder in every HISE project folder, which is the least painful option (the other two ways both have severe disadvantages which go beyond the scope of this answer, but there are plenty of resources on the inter web).

I'd suggest you start with compiling a .dll for your effect (this step is required anyway in order to use the effect in HISE during development). When you're ready, you might want to try compiling a static library or embed the source code directly, but prepare for nasty issues like standard library incompatibilities and compiler flag mismatches.

It's send!!!

Thanks a lot, guys. I'll see if I can think of a way to reorganize the instrument to better fit a tree-like structure. Looking forward to play more with this :)