i have a plugin that changes the state of one of its parameters based on the state of another parameter. Specifically, when i press Record twice, it will record and then stop recording and start playing. So i want a widget connected to PLAY to turn on when that happens.
It’s probably going to require some scripting; how can i trigger a widget change on a plugin parameter change?
You might be able to do without the scripting by using radio grouping. You’ll have to experiment to find out.
it’s not so much a radio grouping, because i could press record and sample a 10-sec loop, press again and it will start playing the loop. When stopped, i can also press PLAY/STOP to play.
So what i’m looking for is a way to tie the state of a widget to change on an event from a plugin itself, not MIDI or my own action. FWIW, the plugin provides “outputs” of the state of each switch; in the plugin they are represented by LEDs but i believe they are like parameters that aren’t able to be controlled by the user, just the plugin itself.
I wrote the plugin myself, to emulate the classic Boomerang+ Looper:
Did you try host automation of your plugin?
Can you map a widget to the parameter you want to observe?
i believe so
I take it back. It doesn’t act as an “output” as i’m expecting it to (which isn’t terribly surprising).
The Plugin’s UI:
The LEDs on the bottom row are technically Outputs. They light up showing state of the device. Here’s the manual: GitHub - mcascone/boomerang-plugin: VST/AU plugin based on the Boomerang+ Phrase Sampler.
In GP the mapping looks like:
it’s hard to see but it’s 5 - Once, 6 - Direction… then 8: OUT: Thru Mute, 9: OUT: Record, etc
I know it’s not a lot to go on but it’s what i got at the moment. I’m looking forward to eventually learning GPScript but for now trying to do it manually.
Well, it would be nice if the plugin provided host automation for everything, including “output only” items. Unfortunately, developers sometimes don’t consider the possibility that someone might want to control/access the plugin without actually going through its editor.
So why not just add that LED as an output parameter from the plugin?
I’m pretty sure it is an output parameter, that’s why it’s there and labeled “OUT: …”. But it’s been a while, maybe something’s not connected right.
Any time it changes inside the plugin you need to “announce” it to the host.
I had to enable “enable automation output” on the output leds. Now it is linkable to a widget! And I’m able to use GPScript to make it control the state of another widget. This is fantastic. It’s what I’ve always wanted in a jamming platform!
Widget link almost worked but script was cleaner.
I made some decisions in the plugin code that are making this harder than it should be in this new context. But now I have so many more options!
