Bitwig Studio 1.3.10



Changes in Bitwig Studio 1.3.10
Released on 16.06.2016.

NEW - Support for Hercules P32 DJ controller provided by Jürgen Mossgraber.

FIXED Crash when replacing a launcher clip with key assignment and then triggering the key.
FIXED Crash when showing popup browser for a device where the device sort mode was saved in the project as vendor but on loading the new sort mode is by location.
FIXED Sends of group tracks are not audible when soloing the return track.
FIXED Saving a preset that embeds two different files with the same name is not possible.
FIXED Auto/Pre/Post setting for sends of Drum machine layers resets after saving and loading the set.
FIXED Send of subtracks in groups are not muted when soloing other tracks.
FIXED Crash when openning a project that had a track group scene and a clip selected on the clip launcher when it was last saved.
FIXED Workaround for bug in OSX El Capitan that causes full-screen GUI painting being slow when using certain graphics chips (13" Retina Macbook Pro).
FIXED When you have VST window open and load a new VST from pop-up browser, the first plugin's window is on top of the newly inserted plugin.
FIXED Duplicating an audio event in arranger note editor results in overlapping events.
FIXED Window positions of multi monitor setups are not restored on OSX when quitting and restarting app.
FIXED When openning very old projects where the plugin states were stored as separate files in the project folder the plugin states would not be found.
FIXED On Windows the engine can crash but leaves child plugin host processes around causing complete lockup of the application.
FIXED Open u-he plugin while playing an automation GUI triggers automation override.
FIXED Stretch modes do not pass phase cancellation with Raw mode when playing back at original tempo.
FIXED Rare crash when dragging tracks and automation in the source tracks is deleted while we are dragging them.
FIXED Bouncing a scene or meta clip creates a track inside the group track instead of alongside it.
FIXED Roll over play button and overview are not shown on bwscene files.
FIXED Double kick bug in Clip Launcher.
FIXED When moving a window between screens with different scaling factors the window could get into a flickering state where the window couldn't decide which screen it belonged to.
FIXED Pop-up windows and context-menus had the wrong scaling-factor in certain multi-monitor setups.
FIXED Certain files are not accepted due to a problem parsing tags.
FIXED Crash on OSX when trying to paint popup window.
FIXED Audio input channels are mapped to wrong hardware channels on OSX when using audio device that has inputs for audio output and a separate device for audio input.
FIXED Sometimes, the DSP Performance Graph cannot be moved until it is resized first.
FIXED Text input on Linux only uses default keyboard layout - changing layout does not work.
FIXED Caps lock is sometimes inverted when entering text on Linux systems.
FIXED Controller Surface API: ChannelBank.scrollSends* methods may do nothing.
FIXED Control surface API looks weird on Linux.
FIXED Added workaround for Roland plugins which didn't work properly in sandboxed hosts.
FIXED Sluggish GUI response in some situations on OSX El Capitan.

IMPROVED - Improved compatibility with Seaboard RISE and EQUATOR.
IMPROVED - Move the tags column in the popup browser so it is next to the category column to which it closely relates.
IMPROVED - When searching in popup browser show hit count for all tabs.
IMPROVED - Controller Surface API: add ChannelBank.scrollToSend(position).
IMPROVED - Performance: Showing the popup browser with a very large sample library (close to 1 million sample files) would take a while to list the devices even though the samples tab wasn't shown.

More info here (DDL links)

Source

 

Don't worry, we are warm enough with it... even without you

​

 

I found Bitwig to make more sense if I looked at it less as a DAW (which it certainly is) and more as some gloriously expanded Ableton Live Operator.
It suddenly became a more intimate experience.
I even named my LFOs.

 

Only clip fades are missing from my Bitwig wish list. Still I prefer it over Ableton. Best thing - No Max For Live.

 

Blasphemer!

 

Four projects in progress... (mixing phase). It's so exciting discover its capabilities day by day ("Mid-Side Split" container is really useful and "Fx Layer" is powerful enough to let me create a multiband compressor using only Bitwig stuff).

 

With so many updates since release and the latest update still having a huge fix list I can't help wondering what the original buyers got for their money when it was first released.

Nothing wrong with fixes of course and it's good to see the developers addressing the problems but it doesn't really inspire confidence in the product. Will we still be getting 30+ fixes in a year's time?

 

For me, Bitwig is truly inspiring for electronic music. No problem with it so far, not even a single "crash"...but i'm not a pro, so...

 

Bitwig is very stable DAW. Just because developers are fixing more bugs than other software doesnt make other software more stable. It's my personal experience. Ableton crashes more than Bitwig. And Ableton is not getting frequent updates like Bitwig.