Sending OSC from Bitwig via automation lanes that can be named

[Lokua]

Hello.

I have a very specific goal and am wondering if this is achievable with Bitwig:

1. Nameable parameters whose names show up in the automation lanes.
2. Ability to read the parameter value from controller script and send those out as OSC, but the parameter names have to be dynamic.

So imagine a device with knobs that have labels I can name like /address_1 etc., then I automate them and the script just knows to send the value out on OSC /address_1.

It's my understanding that Bitwig's automation lanes internally offer float precision, however on the output side for things like MIDI CC the output is limited to 128 values / 7 bits. I'm really hoping that I'll be able to access the higher precision data somehow. In Ableton this is simply not possible (unless I combine two lanes to do NRPN (nope) or use pitch-bend which can only be automated in clips, not in the arrangement which is a deal breaker).

As for #1, it's kind of a first-world need but in my case I'll have many lanes and it's really unhelpful for me to see generic labels like "Knob 1 Value" as is the case with MIDI CC device (which is probably the wrong choice anyway). I only chose this as it has nameable labels and I really hoped I would see those in the automation lane but no, but at least maybe if I can access the device from a script I could read the labels and use those as the OSC addresses.

The other thing I tried was creating an FX Grid and within it adding 8 Value knobs and then using the FX Grid's remote panel to add macros, which have nameable parameters. These too don't show up in the automation lane which is a real oversight IMO (the entire point of the labels is to make things friendly and recognizable; why wouldn't we want the recognizable name in an automation lane?)

I've come to the conclusion that it is simply not possible to have these names show up in the automation lane, which is a real bummer, but I'd still like a very stable way to have 8 knobs I can name and then use those names as OSC addresses. Can control scripts add UI elements somewhere?

In the end I just want ~32 knobs that I can name on a per-project basis (wouldn't mind doing this through settings either) to send OSC out. I have a basic OSC test working where I'm sending OSC to my target app, so hey there's that, but that's as far as I've got.

Thanks for reading my issue. Best.

PS. Where the hell is the API guide? The user guide mentions "developer resources" but all the help section lists is a link to Javadocs (which has been better than nothing but a poor substitute for real documentation)

[Kirkwood West]

whats up Lokua. OSC is the right place for you. you want to use remote controls. getting more than 8 of them at a time is tricky but can be done.

[Lokua]

Thanks for the tip. I get that and will look into it.