Bitwig 3.2 Beta: Scripting API Discussion

[hydrogxn]

ControlSurface API version 11
Hardware controllers using the new API now have sub-buffer accuracy and no jitter when controlling parameters

Manual MIDI mappings in a project now have lower latency, sub-sample accuracy, and no jitter when controlling parameters

Now possible to map controls to MIDI pitch bend messages

Ability to choose between physical or logical knob/slider for a mapping in mapping browser

Ability to decide if a MIDI note mapping applies always or only when it is used for note input

Some of these are straight forward but i'm a bit more interested behind these things because this affects controller scripting.

For myself in this controller scripting world. I guess the next obvious thing is to start migrating my scripts over to use the new hardware controllers, seems like there are obvious advantages...

I was also curious what this is about... and where to make that choice...

Ability to decide if a MIDI note mapping applies always or only when it is used for note input

New bitwig is looking tight... controller scripting is next level. having a good time with it overall.

[klingt.net]

The first thing I noticed was that my build broke because the extension API is now compiled with Java12:

Code: Select all

[ERROR]   bad class file: ~\.m2\repository\com\bitwig\extension-api\11\extension-api-11.jar(com/bitwig/extension/api/util/midi/ShortMidiMessage.class)
[ERROR]     class file has wrong version 56.0, should be 52.0

Maybe I overlooked it but I could not find anything about this change in the release notes.