I am testing out some OSC parameter updates in sushi 1.1.
I have "enable_all_processor_outputs" : true in my config file, and this works when I send a remote parameter update. For example, if I send
/parameter/BuSeq-mt/pattern 0.7
to port 24024, I’ll see the same path and value come back to me on port 24023.
What I was hoping to achieve is by updating some internal parameters in the VST3 plugin with data that is generated internally, I’d get OSC updates sent on 24023. For example, the sequencer has a “pattern” parameter that is a sort of macro for setting steps on and off, and different operations that can modify those steps. I’d like to get a report back over OSC what the state of those steps are, so I setup some parameters for each step get updated as they change, hoping that these changes would trigger OSC messages.
Perhaps a simpler example is a the current step number - as the sequencer advances, I update a “stepno” parameter. When I load the plugin in a DAW, I see this parameter update in the rudimentary UI I have.
But when I load the plugin in Sushi on Mac, I don’t see the OSC updates as those parameters change.
I saw in an older post that this may be a VST2/3 issue, but there was indication that this was going to be addressed in a future sushi update. Curious where this ended up!