It would be great if I could address pins in patches without osc, I’ll give an example.
I have some values that I want to damp, if I send the values to the pins via osc, it is sending these values very frame, and you can get stutters from late packets etc, especially on multiple clients, if there was a node that could directly address these pins (as well as osc, with LTP) then I could send fade times as another message and do the damping more smoothly.
Then again, I don’t know the magic your using to do this anyway, maybe osc is the only way?
if you are on a single machine its not that hard to write values into pins using IPlugin2.Graph Interface (IPin2.Spread - Set Property) - but thats what the server node (which receives Kontrolleurs messages)does anyways.
using multiple clients you could use osc via udp which should not be that laggy for huge amount of values - as in boygoup setup framebased filtering could be calculated on each client separately which obviously could then lead to frame differences.
if osc is really your bottleneck you could try to transfer another protocol or just a simple udp stream which may produce some less overhead - but i assume that the bottleneck could be that youre using kontrolleur on a wireless device?
you could take a closer look to vvvv servers source code which you´ll find here:
but at the end it does exactly want you want to do (except the filtering)- it receives an osc message parse it and write the value directly into ioBox Pins.
you could separate the OSC receiver, do the filtering outside and just use something around line 330 to write the values into pins - or you could also implement some filtering code inside an own server node - which is may be not an elegant way
maybe there is another way to filter your values without any line of code - you could try to define a second udp server / port which will act as kontrolleurs message receiver - filter the values and forward them to the server node locally. should work without any losses in performance.