Osc messages to Bazille

[Samelot]

Hi, I've been experimenting with sending osc messages to Bazille (using Max and Reaper), and so far have been able to connect or disconnect the White Noise Generator to what ever Src (PhaseModSrc, FreqModSrc, etc) I touched last.

/fxparam/last_touched/value 0.05454533
/fxparam/last_touched/value/str White

or

/fxparam/last_touched/value 0.
/fxparam/last_touched/value/str none

This all works fine..

My problem involves changing the last touched parameter to something else, without having to use the Bazille's interface. I can't recreate this touching effect by sending an osc message into Reaper from Max.

Observing the Max console I can see that each time I click on the src "PhaseModSrc" in Bazille, I get "/fxparam/last_touched/name PhaseModSrc" (one executed when I click and another when I release).

Using this same message format, if I were to send, from Max, the osc message "/fxparam/last_touched/name FreqModSrc" any connections I make are still focused on "PhaseModSrc." Only when I click on "FreqModSrc" in the Bazille UI am I able to change the parameter I am focused on to make connections with.

Is there anyway for me to make that same action by sending an osc message from Max?

Thanks

[Phil999]

nice. Unfortunately I don't have an answer because I don't know Reaper enough.

It would be good if softsynth developers would start to build their own OSC interface into their plugins. To my knowledge, there is only Reaktor and Circle. I heard there are a couple of free OSC libraries available, so it shouldn't be too difficult to implement apart from the graphic side.

Softsynths with their own OSC interface would be (are) easy to setup for control, and even bi-directional. They would give the user back what was lost since the mid 80's: direct access to parameters. And even better: a reflection of the current state on the controller.

[xh3rv]

I heard there are a couple of free OSC libraries available, so it shouldn't be too difficult to implement apart from the graphic side.

Just my (probably over-) opinionated thoughts and wild speculation:

OSC doesn't really dictate much structure other than the message format, and there's nothing that explicitly defines a framework for interoperability in a way that's accepted uniformly across implementations. Consequently no developer can really identify a uniform, definitive standard to work off of.

There's some hope that eventually efforts to implement OSC converge to some uniform definition, but that's far from the current reality. AFAIK even the philosophy of having a rather explicit protocol or a more modular one, sort of service-oriented architecture (which was sort of a justification for having OSC just defined as a message format, early in it's history IIRC) - really hasn't been definitively answered. In the meantime it's almost like the worst of both worlds, although there are a few brilliant things happening.

As this relates to the OP, it's wildly speculative on my part but I wonder if the most robust way to think about OSC -> some specific VST plug is actually to encapsulate MIDI somewhere (not the whole way, just into and out of Bazille), at least as a starting point. Seems a bit boring but plausible. Remotely interacting with MIDI is maybe more clearly defined than even VST specs for this stuff.

[Samelot]

I heard there are a couple of free OSC libraries available, so it shouldn't be too difficult to implement apart from the graphic side.

http://www.rossbencina.com/code/oscpack

Is this kind of what your talking about? So reaper has OSC, it just doesn't support all of the messages to do what I want, and this can be added on to by using the link above?