Hi everyone,

I want to connect bitwig -> pd using OSC. I have communication working from pd -> bitwig, but I am puzzled at oscparse. Here's what is coming from bitwig:

/track/5/selected 1
/track/9/selected 0

I want to parse this to get the number 5 (in this example, changing when selecting another track in bitwig) outputted if selected is 1. Not sure how to do that. What I have now is:

[netreceive...]
|
[oscparse]
|
[list trim]
|
[route track]
|
[print frombw]

frombw: 5 selected 1
frombw: 9 selected 0

Any idea?

@EEight This might work: netroute.pd

The second one is if you explicitly want to filter for "selected".

Edit: Small correction.

@EEight If @ingox solution doesn't work (and even if it does) it is probably this..... https://forum.pdpatchrepo.info/topic/9856/oscformat-and-oscparse-integer-not-routing-as-expected
The header...... /this/float/that when broken up by oscparse sends all parts onwards as symbols..... including the float. The data is forwarded correctly.
So the float cannot be routed as it isn't a float.
Solution in that thread.
David.

@whale-av Indeed, I have a problem with unpack... Looking into the other thread. Kind of painful doing OSC with the vanilla object.

@EEight You can also use [fudiformat] and [fudiparse] to clean up the list and make numbers that are symbols to floats: fudiroute.pd

The left one does not work, but the right one works.

Maybe it is also possible to directly use [fudiparse] instead of [oscparse], but i am not sure...

@EEight It's fine if you keep the address as all symbols and the floats (or symbols and integers) as data.
i.e. track/selected 5 1 but of course other programmers are unaware of our problem.
I posted it as a bug to the list at the beginning of 2017 but there was no appetite for a fix.
So I made a few abstractions to emulate the MrPeach Library.......test OSC.zip although [routeOSC] needs to be followed by a standard [route] object.
It all works except for a message like /iannix/add curve 1
I didn't need to get back such a message...... only send it..... so I never wrote in a fix for receiving that format.
David.