Direct access to track/device/parameter page/parameter through Bitwig API

[Bjørn Felle]

I want to use OSC to control Bitwig from a touch screen, but I need to be able to control devices on more than one track at a time. Currently Drivenbymoss operates on the currently selected track, device and parameter page. I forked Drivenbymoss and added the abilty to change to a track and parameter page specified in the OSC message, and this seemed to work well. However when I went to use it today the performance was not very good and Bitwig didn't seem to like the rapid switching between tracks.

So, I'm hoping to access the parameters directly. Drivenbymoss uses the cursor device as a reference to the currently selected device, but can tracks, devices and parameter pages be access directly without switching to them? This would allow OSC to function more like MIDI mapping, meaning parameters across devices could be changed simultaneously.

Thanks in advance

[Bjørn Felle]

It seems IModel.getTrackBank returns an ITrackBank, and its ITrack items should be available through ITrackBank.getItem(n). So I can get a reference to a specific track. However, I can't find any mechanism to get from this a set of the devices on the track.

[Bjørn Felle]

Turns out Bitwig doesn't send feedback when values change on devices that aren't selected. I established this by having OSC receiving on the touch screen controller, and using a MIDI controller to change the value. The parameter changed in Bitwig, but feedback on the current value was only sent to the touch screen controller when the track was selected. It's a real shame you can't "OSC learn" like you can MIDI learn in Bitwig

[Tj Shredder]

This is something to send to support. I think OSC should work directly without a script, maybe just to switch it on/off… An OSC name space could include direct access as well as access based on selection…

[moss]

Turns out Bitwig doesn't send feedback when values change on devices that aren't selected. I established this by having OSC receiving on the touch screen controller, and using a MIDI controller to change the value. The parameter changed in Bitwig, but feedback on the current value was only sent to the touch screen controller when the track was selected. It's a real shame you can't "OSC learn" like you can MIDI learn in Bitwig

Which parameters of a Device do you monitor? Are you sure you are not only monitoring the cursor device?