Actually Christoph, do you have time for a Skype call? I think it might help if I could show you some stuff live.

Well it came up in a real world project but I just changed the name of the variable so I think it's safe to acknowledge it and ignore it

Duh, I solved it (partly) - had to select the script from the top left corner dropdown of the interface designer workspace. Still not showing up in the main workspace though.

Yes I wanted to change that for quite some time.

I just noticed, the front interface isn't an external script but yet it doesn't show up and the playable range script it's picking up the one combo box but not the rest of it, I'm guessing it's also finding the mic mixer script since it expands to the correct height...

You're right, but it just doesn't work if you put it into a SynthesiserGroup. I'll check this.

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.