Yes, this might be the best way. BTW, I am currently working on making this a bit more robust. Also sorry for putting you through that, I know it is frustrating when stuff that worked breaks.

I shall remove it then.

Ah, no, that lousy Travis CI build file is broken since weeks. Things should be fine there (let me know if it doesn't).

Alright. Sorry about the underscore mess I realized that Steinberg changed the folder name (back when I downloaded the SDK the folder name was different IIRC). I'll update the readme.

going to the news:

repared all that i wrote before. result:

studio one: OK

reaper: Ok

Ableton Live : ok BUT if you first launch (creating the folder in c/users/appdata/etc...) with Live. if you first launch in another daw and after opening Live : Bug !

Sonar & bitwig: NO ! do what you want boy, but we only accept the 1.1.1 version !

difference beetween 1.1.1 & 1.1.2 version , (instead of updated modules settings) = the script from "musicbox" with the settings, tooltips,presets and samples menus. In 1.1.1, in the VST versions the setting menu disapear. In 1.1.2 this menu is visible; but seems to create problems with some DAWs.

Some scripts in the SettingButton.js that 1.1.2/ VST version is not supported by this ones.

not tested other DAWS (reason, cubase, etc. ...)

Thanks a lot, that worked.

Still, after resolving the sample references, the samples should be loaded, too, I think.

Here is fine, whenever I am find the time, I just search all your topics and bug fix my way through them :)

Things are starting to pile up on the Linux end :)

Oh yes I remember about that now. I had forgotten to do it. Thanks!

Here is a solution, for those to whom this disadvantage comes.

In the idea, all the modules loaded except the script. So, I was looking for a way to find my script and copy it to my project.

We must go to the folder of his project ----) Preset ----) Right click on the preset you have chosen and made open with a BlocNote ...!

You now have access to all your code ...!

You only have to copy it in the project!

Here is!

Alright, I keep it in mind. If anybode else requires this, I'll probably add it back in.

thanks.
good news for the API. if i remember well the rackafx code was created about a "rough" code. i will try to find it (http://basicsynth.com or http://musicdsp.org or else). I will try to find it.
i compiled the rackafx projects as .Dll so with this API i maybe will try to implement it in Hise.
if i don't write stupid things ERS made the dimension-D chorus in Juce....

I've updated the Readme in the repository with better instructions:

https://github.com/christophhart/hise_tutorial/blob/master/README.md

I have plans for changing this wizard and add another way of connecting modules simply by adding the module ID and parameter ID to the JSON:

const var Knob = Content.addKnob("Knob", 62, 6); // [JSON Knob] Content.setPropertiesFromJSON("Knob", { "width": 129, "height": 47, "processor": "LFO Modulator 2", "parameter": "Frequency" }); // [/JSON Knob]

This is a far more stable and bug prone way to implement a simple parameter connection (the wizard has to do a lot of regex processing which can lead to a lot of edge cases).

In the end the positioning of the loop point is all about how it sounds, so I don't think the process can really be automated, but the visual cue would really help in quickly finding the most likely optimal positions to audition. Although maybe some advanced "snap to cycle" in addition to snap to zero crossing might be useful? Well, I guess I'll try using Reaper for picking the loop positions.

Ah yes, thanks. I was reworking the handling of different modes for knobs and this is a side effect.