SliderPack is the gui, ArpManager is the midi handler. I don't want to combine the two.

Edit: Can I build my sliderpack value array on init?

Edit: The reason for the separation is so that you can arbitrarily decide what step has what values. If I have a sliderpack directly connected to that then it becomes inflexible, unportable, unscalable.

I think I am handling this correctly in the main file menu but this tiny popup slipped through the cracks somehow. Not much cross platform, will be fixed.

I think that you can get the value using the index, just not in the onInit callback

Yeah, that's right. I'll change that.

Well the beauty of code based UIs are that you can do stuff like this with loops (and I would really refrain from autogenerating Javascript code that creates 512 buttons manually).

Take a look at this quick example:

Content.makeFrontInterface(400, 300); const var buttons = []; var x = 0; var y = 0; const var Panel = Content.addPanel("Panel", 10, 10);// [JSON Panel] Content.setPropertiesFromJSON("Panel", { "width": 510, "height": 255 }); // [/JSON Panel] for(i = 0; i < 64; i++) { x = parseInt(i % 8); y = parseInt(i / 8) * 32; buttons.insert(-1, Content.addButton("button"+i, x * 64, y )); buttons[i].set("width", 60); buttons[i].set("text", x+1); buttons[i].set("parentComponent", "Panel"); }

The panel acts as parent component, so the positions of the buttons are set relatively to the Panel. You can select the panel and move it around and the buttons should follow (make sure you select the panel by rightclicking and choose "Select Component to Edit -> Panel"

If you planning to build sequencers or any kind of matrix (which your power of two number suggests), this is really the recommended way.

This is fixed.

This is fixed.

This is fixed now.

Good to know! Let me know if you run into another issue...

Thank you :)

That might work!

Yes it's not a major issue for me, just briefly confused me

Alright, this is fixed.

Nice catches. The sampler gets bypassed when the samples are loaded and unbypassed after the loading thread is finished, but it totally ignores if the sampler was bypassed at all. I'll fix this.

I'll also check the purge state, it should definitely restore it.

Thats awesome. Makes perfect sense now that the knowledge is there. : ) as with most things.

Thanks again

Yeah, the other filters aren't biquads and don't have IIR coefficients that can be plotted, but I'll add some dummy coefficients to hide this :)

But the Frequency modulation is supposed to work. I'll investigate.

This is the most simple low pass filter implementation imaginable:

reg lastValueL = 0.0; reg lastValueR = 0.0; reg thisCutoff = 0.0; reg invCutoff = 0.0; const var Cutoff = Content.addKnob("Cutoff", 0, 0); // [JSON Cutoff] Content.setPropertiesFromJSON("Cutoff", { "min": 0.01, "max": 0.99, "middlePosition": 0.1 }); // [/JSON Cutoff] function prepareToPlay(sampleRate, blockSize) { } function processBlock(channels) { thisCutoff = Cutoff.getValue(); invCutoff = 1.0 - thisCutoff; for(sample in channels[0]) { sample = thisCutoff * sample + invCutoff * lastValueL; lastValueL = sample; } for(sample in channels[1]) { sample = thisCutoff * sample + invCutoff * lastValueR; lastValueR = sample; } } function onControl(number, value) { }

However, iterating over every sample and process it is where a weakly typed language like Javascript comes to a performance bottleneck - this example needs about 2% while the CPU usage of native code of the same functionality should be totally neglectible. So for now it's OK to play around with it (and prototype new algorithms), but I wouldn't consider using it in an actual instrument.

I am planning to offer a collection of basic DSP building blocks that can be assembled via scripting (just like REAKTOR or MAX). The basic API is already there, but creating all those little modules will take a while...