Thanks for getting in touch.
When using ClipNr, it sounds like you may be sending string arguments to Live instead of the expected integers. Here is a Max patch that illustrates the difference:
If this doesn’t solve it, perhaps you could give us a bit more info:
- which host are you sending OSC from?
- would you able to add a print-screen of the messages in the Latest Messages Received panel of GrabberReceiver so that we can see exactly what messages you are sending?
I must say that TrackGrabber reacting at all when receiving a message destined for TriggeredClipNr with a string argument doesn’t sound correct. I added it to our todo list. Perhaps we can even do a red blink instead of a green or something like that.
When using ClipName: unfortunately I cannot reproduce the behavior you describe, launching clips round robin style. For me it works as expected. For this too it would help to know exactly what messages you are sending.
Regarding the ‘thru’ functionality, I think I see where you are coming from. With OSC, the way this is typically done is to send the same message to two different ports, one of which is listened to by Live, and another by Chamsys.
This requires your source application to support sending the same message twice though. If this is not supported, you could consider using an OSC routing application such as OSCulator to receive the single message from your source and send out two of them to different ports.
Let us know how you fare!