Mhh, the SNEX documentation seems quite confusing to me... is there a kind of tutorial somewhere to get statrted with it. Maybe a simple example from the main code to implementing it into a scriptnode? I don't know where to start...
@lalalandsynth If the step size is zero, then it's the default and the property will be removed from the value tree, but this means that it won't show up in the property editor (which is just a glorified XML editor).
As soon as you change the step size to something non-zero, it should show up. You can use the range presets for this.
@Christoph-Hart Ohh, awesome, that works fine. You can also specify the slot that way.
Content.makeFrontInterface(600, 600);
const var rm = Engine.getGlobalRoutingManager();
const var cable = rm.getCable("Slot_01");
const var value = cable.getValue();
Console.print(value);
@Lindon Yes, unless they use certain things which prevent compilation:
global cables
modulator slots
changes to the DSP network using the scripting API
I think there are a few more edge cases, but these are the most important ones. If none of them apply, then you should export the scriptnode network as dll and use the hardcoded modules instead, this bypasses the entire scriptnode data management with its additional data layer and API access.
Ok thanks - good guidance, in passing... what are "modulator slots" here?
@d-healey I was watching it than I started 'getting creative' to see what I can do... and that's where I got in trouble... I used to write javascript and AS2 and AS3 for flash... there is some familiar things going on and it's been awhile...
Trust me you don't want a single knob. This creates many issues with preset restoring / automation if the order of the sync knob and the button is not in the correct order etc.
What I'm usually doing is to have two knobs at the same position and just swap the visible property to show only one of them.
