@christoph-hart OK. I already knew I was in over my head but it's good to know that I'm WAY in over my head.

I started out just wanting to build a simple sampler I could throw my custom samples in that wouldn't require too much scripting and could be DAW agnostic.

But now I'm only going to be satisfied by trying to rebuild an emulation of EXS24 with some added features. Guess I better get a lot better at scripting. :(

@d-healey Thanks! I've been diving into the Interface Editor for the last couple days and am pretty happy with what I'm able to accomplish. And the linking widgets to parameter id's is a breeze.

But there are still some things I'll have to script and I'm unsure about how to go about it. For instance, say I setup a knob called "randomPitch" in the interface. I assign the processor id to "detuneRandom" (a Random Modulator in a pitch modulation module in the sampler container). I then assign the parameter id to "Intensity". Works. Great! But I don't want the knob to be able to go all the way 12. ;) This knob is for a chorus-y detuned effect, so I really only want it to have a range of +/- 50 cents. Well, I can sort of do this in the component specific properties by setting the "Max" field to .041 (1/24), but then the smallest step size available is .01....so not enough resolution for this type of control. So, I tried a little scripting. I put this in the onControl callback:

if(number==randomPitch)
    {
const var detuneRandom = Synth.getModulator("detuneRandom");     
detuneRandom.setAttribute(detuneRandom.Intensity, (value/24);

    }

where "randomPitch" is my widget id, and "detuneRandom" is my pitch random modulator module. A couple of questions about this:

1. Is the onControl callback the best place to put this script? I know from reading some of Christoph's posts, there are efficiency concerns with where to put scripts.

2. I also read on some post that the first value of the .setAttribute method should actually be an integer instead of a string? And that integer is an index of each modules parameter? Is there a way to to determine what index number pertains to what parameter?

3. Is this very simple code I thought would be easy, very wrong?

@christoph-hart OK. I already knew I was in over my head but it's good to know that I'm WAY in over my head.

I started out just wanting to build a simple sampler I could throw my custom samples in that wouldn't require too much scripting and could be DAW agnostic.

But now I'm only going to be satisfied by trying to rebuild an emulation of EXS24 with some added features. Guess I better get a lot better at scripting. :(

@Christoph-Hart Christoph, sort of on a similar topic, would you use the Global modulator system if you wanted to give the user the ability and flexibility of assigning the same modulators to different parameters in different modules as they see fit? Say, for instance, I wanted the user to be able to be setup their own modulation routing so they could decide to modulate the phaser rate by "LFO 1"? And then they could use that same "LFO 1" and assign it to modulate the cutoff on a filter module? But, I don't want to pre-bake the routings, I want them to be able to set it up for themselves.

Ah. Victim of the old tutorial.

I’m going to watch that video but what’s the best practice when you’re switching between scripting and editing via the property editor?

So say in the inInit callback I add a button:

Content.addButton(“myButton”);

I then hit compile and the button shows up in the interface editor, so then I grab the button with my mouse and move it to where I want it and then use the interface editor to set its color.

Then when I hit compile, the button returns to its default coordinates. :(

I know I can set these properties in the script as well, but sometimes it’s more intuitive to just grab and move.

I guess I don’t have a full grasp of the difference between JSON and the standard scripting window.

Slightly off topic, but in line with old features phased out...what’s replaced the assign parameter wizard? Say I want to assign “myButton” to the power button of a filter module in my main container? Again I know this is probably easy to do with scripting, but the old way of right clicking on the interface object and setting it to whatever seemed pretty easy for JavaScript noob like me.

Thanks everyone for the help! Love this platform.

Is there a preference to have any changes made in the property editor (when you're working with an interface object) be reflected in the script? In the tutorials the script seems to be automatically updated when you edit a parameter in the property editor panel. I'm not getting this behavior.

@christoph-hart ok thanks for the clarification. I thought I was going nuts.

So the solution for right now is to have a duplicate set of samples edited to the release tails. Easy enough, just have to put that step into my workflow.

Thanks!

Trying to build my first sample instrument using mostly built in modules and very little scripting. I've got my initial sample map set up in "Sampler1" with all my settings like 'SampleEnd', 'LoopEnd', 'SampleStartMod' dialed in. But, I want to use the "release trigger" script that's built in, so I've created a second sampler module ("Sampler2") and copied the sample map from "Sampler 1". I've also added the release trigger midi script to this second sampler module. The problem is that when I modify the sample setting like 'sample start' or 'enable loop' in this second module it seems to mirror it in the first sampler module. I've made sure I've only had the samples in the second module selected, and have even created and loaded a duplicate sample map with a different name, but it doesn't seem to change this behavior.

I'm sure this is obvious but how do I make it so the samples in sampler2 have different settings than sampler1?