Receive OSC input from hardware --> modulate macros

[JohannesTress]

Hello all,
I am not at all familiar with the programming of the API, but I have a wish that I cannot imagine without diggin into the Scrippting-stuff:
I would like to route OSC data from external sources (Arduino, Littlebit, Android app, etc.) in Bitwig to the 8 macro buttons within a chain device. Since the names(pace) for OSC-Data always have to be defined individually, a solution similar to the Flexi script from Moss would be very ingenious. A "catch" or "learn function" would simplify the handling of different devices even more. First of all, I am interested in how realistic such a scenario is with the help of the Bitwig API. There are already very elegant solutions for MaxforLive (https://www.ableton.com/de/packs/connection-kit/), but I think within the Grid this kind of interfacing would open up creative spaces for interacting with the real world, not only modulars.
Thank you for your feedback!
Johannes

[moss]

If you can define the OSC messages yourself on these devices you can use my OSC implementation which is part of DrivenByMoss.

[JohannesTress]

Thanks moss, I'll give that a try! The idea sounds pretty straight forward...
All best!
johannes

[JohannesTress]

Ugh... I just haven't found the right names for the macro controller. I tried deconstructing the Open Stage Control App for Bitwig, but there seem to be too many variables in use to find the right address. Moss, can you tell me - without too much hassle - what address I need to specify for the 8 controllers of the first Device in the first track within Bitwig? That would be great...
all best!

[moss]

You cannot address specific devices. If you need something special you would need to implement it yourself.

The devices you can address are: The cursor device (/device), the primary device of the channel (/primary) and the equalizer device (/eq). All these are on the selected channel.

Parameters are: /device/param/{1-8}/...

See the manual for more info.