Bitwig Studio 3.2.5

What's new in this version:

Improvements:
- Extension API is now at version 12, allowing finer control of specific devices and plug-ins

Automation Streamlining:
- When automation follow is enabled, automation and MIDI both follow when Arranger clips are moved or deleted
- Certain parameters (such as pitch bend, pedal CCs, pressure) will always clear to 0, regardless of what the value from the left side of the time range was
- MIDI automation is recorded in a proper hold mode (avoiding inadvertent ramps)
- When recording and not overdubbing, each MIDI parameter that already has an automation lane write a flat line
- When recording, MIDI automation is only played back when overdubbing
- Automation thinning is not applied to certain MIDI parameters (pedal CCs) after recording
- Automation thinning is not applied after pencilling certain parameters (non-continuous parameters, not related to MIDI)
- MIDI parameters that already exist are no longer added twice on record
- Fixed some GUI repaints in the Arranger

Fixes:
- Application could hang when there were very large Grid patches, in some cases
- Changing a toggle parameter in a device now updates the status (in the window footer) immediately
- Pressing the [DELETE] key, etc., in the plug-in host window will no longer delete project content. (Global shortcuts like controlling the transport, will still work though.)
- Assigning shortcut to DSP Performance Graph window does not close it anymore after opening
- Changing caps lock status in a plug-in window would not necessarily turn on note input
- Keyboard note input did not allow some keys that weren't are used for note input to reach the plug-in (such as the arrow keys, etc.)
- barStartPos value sent to VST 2 plug-ins would always be 0
- Jack transport could be reported incorrectly to Jack when there were time signature changes
- Windows: plug-ins always assumed that caps lock was used to turn on keyboard note input even, if the user disabled this in the (Shortcut preferences)
- macOS: keyboard note input could invoke an action in a plug-in instead of playing a note in some plug-ins
- Linux: keyboard input was not working for many plug-ins (such as u-he plug-ins, and Renoise's Redux)
- Controller API: CursorTrack.createCursorDevice using a CursorDeviceFollowMode would not update correctly at the point a new device was inserted into the device chain