Global Velocity Modulators - and Arps.....

[Christoph Hart]

1. Use the script modulator as global modulator INSTEAD of the velocity modulator. You need to basically reimplement the velocity logic, but that shouldn't be more than two lines of code
2. Always return a value. Your false branch doesn't return anything which will probably be converted to a zero, so silence. return 1.0 is your friend as last statement.

[Lindon]

@Christoph-Hart said in Global Velocity Modulators - and Arps.....:

1. Use the script modulator as global modulator INSTEAD of the velocity modulator. You need to basically reimplement the velocity logic, but that shouldn't be more than two lines of code
2. Always return a value. Your false branch doesn't return anything which will probably be converted to a zero, so silence. return 1.0 is your friend as last statement.

problem with 1 is I want to retain the ability to have the user "draw" the curve they want.....

But point 2 is definitely t-shirt time for me... thanks..

I think my simplest solution may be to move the Arps AFTER the Global Modulators....as the retrigger functionality in the Global LFOs is getting screwed over too....

[d.healey]

@Lindon said in Global Velocity Modulators - and Arps.....:

I want to retain the ability to have the user "draw" the curve they want.....

Add a table to your modulator

[Lindon]

@d-healey to my ScriptVoice Start Modulator?

[d.healey]

@Lindon Yeah, it's just like any other script, you can give it a gui and then read from the table to scale the velocity.

[Christoph Hart]

@d-healey this. That's why I said "two lines of code" and not "one line of code" :)

[Lindon]

@d-healey said in Global Velocity Modulators - and Arps.....:

@Lindon Yeah, it's just like any other script, you can give it a gui and then read from the table to scale the velocity.

Nope not getting it... Script Voice Start modulators... can use ScriptNode, but I cant see where I build a GUI..or how I get that to show up in the plugins GUI...

[d.healey]

@Lindon said in Global Velocity Modulators - and Arps.....:

can use ScriptNode

Oh right, this is one of those things. Because everyone uses script node for the node part and not the scripting the interface designer isn't shown...

I use a custom workspace so I can see both, you can also add the interface designer as a floating tile.

You should create the GUI through scripting for your modulator rather than adding controls in the interface designer with the mouse. That way when you reuse your modulator in another project the GUI will be there too.

@Lindon said in Global Velocity Modulators - and Arps.....:

show up in the plugins GUI...

Connect the table on your UI to your modulator via processor/parameter ID - just like any other module.

[Lindon]

@d-healey right LOL - another thing in HISE that I should "just know about" even tho there's no clue in the default UI how or where to find it..

[Christoph Hart]

@Lindon yes in an ideal world the script voice start modulator should show the interface designer instead of the scriptnode workspace but that shouldn‘t keep you from slapping one lousy table on the modules interface by scripting.

That makes it three lines of code…