Most Bitwig lead programmers are former (and best) programmers from Ableton Company in Berlin.
So what do you really expect?
That's why nothing special happened to Ableton the last couple of years.
Ableton was fucked, they have lost a lot of good mastermind programmers.
Stupid and messed management was the finally reason for that.
(If you have friends in Berlin, sometimes you can get some inside informations)

 

Last edited: Apr 6, 2019

Changes in Bitwig Studio 2.5.1, RC 5 [released 11 April 2019]

Improvements

• When switching presets in a plug-in GUI and a parameter has modulation apply the modulation to the value in the preset

Fixes

• SFZ files that set a default path cannot be loaded
• In some cases VST 3 parameters could jitter slightly when moved
• If a plug-in parameter is modulated allow the user to still interact with it in the plug-in GUI (disable modulation while they do this) and then re-enable when they finish
• Add workaround for all plug-ins from Acustica that say the user interacted with parameters when they didn't

Regression Fixes

• In 2.5.1 RC 4: Disable the begin and end edit simulation for plug-ins that don't send this as it causes some problems in plug-ins that actually do
• In 2.5.1 RC 4: MIDI mappings in VST 3 were all mapped to the pitch bend instead of the correct message
• Is 2.5.1 RC 4: Some settings in a VST 3 plug-in GUI may not have any audible effect (e.g. Fab Filter Pro Q-3 filter band preview)

 

Changes in Bitwig Studio 2.5.1 [released 03 May 2019]

Plug-in Fixes

• Reduce loading time and memory usage for some VST3 plug-ins
• Improve the error messages when we find problems scanning plug-ins (less redundant information)
• If a plug-in constantly reports latency- and IO-changes then ignore these to avoid audio drop-outs
• Don't show errors found when trying to treat a shared library as a plug-in if it is just a normal shared library and not a plug-in (Linux/Windows)
• When switching presets in a plug-in GUI and a parameter has modulation apply the modulation to the value in the preset
• Better handling of VST3 plug-ins that list the same parameter ID multiple times - choose the most likely one based on the metadata
• In some cases VST3 parameters would jitter slightly when moved
• If a plug-in parameter is modulated allow the user to still interact with it in the plug-in GUI (disable modulation while they do this) and then re-enable when they finish
• If a VST3 plug-in parameter was modulated it was hard to edit it inside the plug-in window as it jumped while you tried to edit it
• Some VST3 parameters did not update in their plug-in window when they were automated or modulated
• Plug-ins that incorrectly list their parameters with non-unique IDs didn't work correctl
• Workaround for Acustica VST3 plug-ins: Was incorrectly stating a parameter change came from a user interaction
• Workaround for Acqua VST3 plug-ins: Ignore MIDI mappings interface it was returning invalid data

Fixes

• Sampler didn't trigger envelope on notes that were shorter than one sample - this could happen with certain drum kits
• SFZ files that set a default path to find its samples cannot be loaded
• ALSA might fail to scan the devices if the previously selected device is disconnected (Linux)
• Undoing the move of a scene could result in a broken layout of the arranger clip launcher if some scenes had a custom width
• Sliding content does not work correctly on reversed audio events
• Reordering scenes in a nested track results in a broken clip launcher layout
• Crash in Maschine JAM script when stepping through parameter pages of DRC VST plug-in
• Control scripts that don't require any hardware (eg MIDI or USB) don't automatically start when added
• Controller visualizations shown in the status bar may not always show the correct value when the parameter is changed in the Biwig Studio user interface
• Stereo Split Device is -6dB too quiet
• The timing on some modulation routings would be one processing buffer late

Regression Fixes

• Value displays for plug-in parameters not updated on controllers in 2.5 if the parameter is not currently visible in the parameter list in the device chain
• Some very old projects that were create in 1.1.x where the user had copied the master track into a nested track group's track list meant that the project could not open in 2.3.x or later

 

Checking daily for v3 beta. Dragging out now, i watched a video from NAMM today which was dated 29th january and they said theyd be rolling out public beta in 4 weeks with release 2nd q 2019. Been a while since then. Hope its as good as i anticipate. People have said they dont need the Grid as they have Reaktor, but it looks like the Grid is much more user friendly and fun to use. I watched a video interviewing two of the creators of Reaktor today too, and the guy asked if they could delete a module and not break the patch they were creating and the NI guys said it would be nice but it was too difficult to impliment, while bit devs demo being able to hotswitch modules and the patch still working. I think bitwig is so innovative and the devs so good that the grid will be as good or better than Reaktor.

Still thankfull for updates to 2.5 today obviously - just cant wait for grid

 

for sure this is going to be the DAW of the future!! just have some questions. Any chances we can see the features Ableton capture, simpler(slice, sample chop) and logic comp/flex pitch for easy vocal/instrument recording?? recording with capture is so easy and intuitive no more recording buttons, just play... a device like Ableton simpler for chopping instruments/vocal samples would be so nice and the logic comp/flex pitch so finally stop opening logic just to record the vocals. Almost forgot, will akai force have compatibility with bitwig? sorry for so many questions, you guys are the best anyway