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 :)

showing samples in the GUI (to select it and save it in preset):

include("SettingsButton.js"); include("UserPresetWidgets.js"); const var ComboBox = Content.addComboBox("ComboBox", 721, 3);// [JSON ComboBox] Content.setPropertiesFromJSON("ComboBox", { "text": "Presets", "width": 189, "bgColour": 4278190080, "itemColour": 4278190080, "itemColour2": 4211081216, "pluginParameterName": "Presets", "items": "" }); // [/JSON ComboBox] const var Sampler = Synth.getSampler("Sampler"); const var sampleMapList = Sampler.getSampleMapList(); ComboBox.set("items", sampleMapList.join("\n")); inline function onComboBoxControl(component, value) { Sampler.loadSampleMap(sampleMapList[value-1]); }; ComboBox.setControlCallback(onComboBoxControl); const var presetDecButton = UserPresetWidgets.createPresetButton("presetDecButton", 379, 8, false); const var presetIncButton = UserPresetWidgets.createPresetButton("presetIncButton", 575, 9, true); const var presetDisplayPanel = UserPresetWidgets.createPresetDisplay("presetDisplayPanel", 405, 6); UserPresetWidgets.setPresetBrowserLookAndFeel(presetDisplayPanel, "Digital-7 Mono", 15, "0xFFAAAAAA"); const var settingsButton = SettingsButton.createSettingsButton("settingsButton", 5, 5); const var PerformanceLabel = Content.addFloatingTile("PerformanceLabel", 31, 2); // [JSON PerformanceLabel] Content.setPropertiesFromJSON("PerformanceLabel", { "width": 186, "height": 32 }); // [/JSON PerformanceLabel] const var perfData = { "Type": "PerformanceLabel", "Font": "Digital-7 Mono", "FontSize": "12.0", "ColourData": { "textColour": "0xAAFFFFFF" } }; PerformanceLabel.setContentData(perfData); const var Tooltips = Content.addFloatingTile("Tooltips", 1128, 2); // [JSON Tooltips] Content.setPropertiesFromJSON("Tooltips", { "width": 453, "height": 26, "itemColour": 4294901760, "itemColour2": 4294901760 }); // [/JSON Tooltips] Tooltips.setContentData({"Type": "TooltipPanel", "FontSize": 13.0, "ColourData": {"bgColour": "0x000000"}});

i used it for a multisample/library rompler. Of course all set "save in preset" = yes

OK, thanks...

I think I will pass my turn, unless I ask for it in the future ...

It transforms the console output from the mess you posted above into something more comprehensible.

I don‘t think it‘s mandatory so you should be able to compile without it, but on the other hand installing this is pasting one line into the terminal and then you‘re set. Check out the link to the GitHub repo I posted above.

hello !
maybe i will write a stupid thing but...
i remembered when working with RackAfx that Will Pirkle created his rompler with integrated (hardcoded) samplepath to do this thing (bidirectionnal) and explained in his book that with streamed samples it's not possible. so it seems that Kontakt don't "stream" samples, but load them before in temp memory to do this.

sure it's a great function. but i prefer without but with streamed samples.

Not sure of this... Must have confirmation by someone else...

You will need to learn to script if you want to do anything more than the most basic tasks with HISE - or any other similar development environment.

HISE has built in cycle round robin per sampler via groups (like Kontakt). You could use one sampler per velocity layer to get RR per velocity but that would be a huge waste of resources. Realistically you will need a script for this.

You could add a background image without scripting but you will need a little scripting to get this to display as a main interface for your instrument.

If you're scared of scripting then you are not going to be happy about VST exporting, have a look in the documentation and tutorials for more info :)

Hello,

That's news. Problem solved! I went to give the mini mac 4gb and I took in a store next to the mini mac with 8gb of ram. I buy an external SSD and I install High Sierra.

I had a hard time understanding why people bought mac ... and I still have a hard time understanding why he sells such shit. Anywai, this is not my problem anymore.

Thank you for helping me, it's a lot smoother now.

Big thanks!