Bitwig Studio 1.3.6
- KVRist
- 368 posts since 29 May, 2005 from Berlin
Hi everybody,
Bitwig Studio 1.3.6 is available for download on http://www.bitwig.com/en/download.html. Here is the list of changes:
NEW - Added Post Recording Actions to clip launcher which are activated after a specified duration has been recorded. This can be used to record clips of a predetermined fixed length as well as to record multiple takes automatically to multiple clips.
IMPROVED - Added support for track and instrument name metadata to MIDI file import.
IMPROVED - Much lower memory usage and better overall application performance on OSX.
FIXED - Crash when changing drum machine preset for another preset using the popup browser and having previously selected a pad that does not have a chain in the preset selected.
FIXED - Phase is inverted when recording audio from an external source using ASIO at 24-bit.
FIXED - Muted clips are not visually distinguishable from unmuted clips in clip launcher.
FIXED - Moving notes by a tiny amount using the inspector creates lots of duplicates.
FIXED - Creating a clip in the clip launcher using different time signature than 4/4 still creates a clip with 4 quarters duration.
FIXED - When importing MIDI files the clip length should be calculated from the content instead of from MIDI metadata.
FIXED - When opening timeline context menu only update time selection when clicking outside of selected time range, otherwise delete command will not work correctly for automation.
FIXED - Rare crash when deleting a track or moving it out of it's group.
FIXED - On Linux the window shifts down by the size of the title bar each time the application is started.
FIXED - Exporting MIDI file should ignore muted notes.
FIXED - When saving a new clip the BPM is set to 110 and not the project's current tempo.
FIXED - Zoom to fit leaves too much space in timeline editors.
FIXED - Clip launcher note editor sometimes jumps to time before content start when stopping playback with playback follow enabled.
FIXED - Dragging a track from one project to another that referered to a sample that was collected and saved on a different machine in the source project would not find the samples when dropped in the destination project.
FIXED - Effect track is called audio track in context menu.
FIXED - Moving multiple continuous clips with "automation follows clips" activated creates unnecessary automation dots at the boundaries of the clips.
FIXED - When clicking on header area of a drum note lane that does not contain notes, it should also reset the time selection to avoid accidental deletion with standby time selection.
FIXED - Undo history breaks if you move an automation point and hit the right mouse key while doing so.
FIXED - Instrument notes are not truncated at the clip boundary when consolidating.
FIXED - Pasting text from the clipboard on OSX does not work.
FIXED - Free running automation is not shown correctly in content preview section of launcher clips.
FIXED - Importing corrupt midi files that have track names that contain the null character results in a project that cannot be opened once saved.
FIXED - When there is a long list of items that needs to be scrolled in a menu it is not possible to select menu items using touch that are not visible.
FIXED - Changing track color while detail editor being open does not repaint notes.
FIXED - Macro section displays "Default Preset" after loading a saved VST preset via the popup browser into an existing VST plugin.
FIXED - Projects with editors set to triplets don't show correct value in grid subdivision fields.
FIXED - Some devices get clipped along the bottom edge when scaling is not 100%.
FIXED - Notes in drum MIDI files that have zero length should be interpreted as 16th when importing into Bitwig Studio.
FIXED - Playhead starts in wrong position and not from the blue play marker after bounce.
FIXED - Controller API: Crash when creating named device cursors from onMidi callback.
FIXED - Regression: pasting text does not work on OSX.
FIXED - Not possible to move the loop start for a clip beyond bar 250 using inspector but dragging loop region allows this.
FIXED - Controller API: crash when using device layer bank.
FIXED - Crash if bouncing a track region in place and before the bounce has completed deleting the track.
FIXED - OSX engine crash when scanning certain audio devices.
FIXED - Sometimes engine crashes on OSX when connecting to document.
Important note for Windows users:
Windows might show a warning during installation about the installer not being trusted software. This is only a temporary issue and should disappear soon. In case you see such a message, you can still install the software by clicking "install anyway" (or something similar).
Best wishes from the Bitwig team!
Bitwig Studio 1.3.6 is available for download on http://www.bitwig.com/en/download.html. Here is the list of changes:
NEW - Added Post Recording Actions to clip launcher which are activated after a specified duration has been recorded. This can be used to record clips of a predetermined fixed length as well as to record multiple takes automatically to multiple clips.
IMPROVED - Added support for track and instrument name metadata to MIDI file import.
IMPROVED - Much lower memory usage and better overall application performance on OSX.
FIXED - Crash when changing drum machine preset for another preset using the popup browser and having previously selected a pad that does not have a chain in the preset selected.
FIXED - Phase is inverted when recording audio from an external source using ASIO at 24-bit.
FIXED - Muted clips are not visually distinguishable from unmuted clips in clip launcher.
FIXED - Moving notes by a tiny amount using the inspector creates lots of duplicates.
FIXED - Creating a clip in the clip launcher using different time signature than 4/4 still creates a clip with 4 quarters duration.
FIXED - When importing MIDI files the clip length should be calculated from the content instead of from MIDI metadata.
FIXED - When opening timeline context menu only update time selection when clicking outside of selected time range, otherwise delete command will not work correctly for automation.
FIXED - Rare crash when deleting a track or moving it out of it's group.
FIXED - On Linux the window shifts down by the size of the title bar each time the application is started.
FIXED - Exporting MIDI file should ignore muted notes.
FIXED - When saving a new clip the BPM is set to 110 and not the project's current tempo.
FIXED - Zoom to fit leaves too much space in timeline editors.
FIXED - Clip launcher note editor sometimes jumps to time before content start when stopping playback with playback follow enabled.
FIXED - Dragging a track from one project to another that referered to a sample that was collected and saved on a different machine in the source project would not find the samples when dropped in the destination project.
FIXED - Effect track is called audio track in context menu.
FIXED - Moving multiple continuous clips with "automation follows clips" activated creates unnecessary automation dots at the boundaries of the clips.
FIXED - When clicking on header area of a drum note lane that does not contain notes, it should also reset the time selection to avoid accidental deletion with standby time selection.
FIXED - Undo history breaks if you move an automation point and hit the right mouse key while doing so.
FIXED - Instrument notes are not truncated at the clip boundary when consolidating.
FIXED - Pasting text from the clipboard on OSX does not work.
FIXED - Free running automation is not shown correctly in content preview section of launcher clips.
FIXED - Importing corrupt midi files that have track names that contain the null character results in a project that cannot be opened once saved.
FIXED - When there is a long list of items that needs to be scrolled in a menu it is not possible to select menu items using touch that are not visible.
FIXED - Changing track color while detail editor being open does not repaint notes.
FIXED - Macro section displays "Default Preset" after loading a saved VST preset via the popup browser into an existing VST plugin.
FIXED - Projects with editors set to triplets don't show correct value in grid subdivision fields.
FIXED - Some devices get clipped along the bottom edge when scaling is not 100%.
FIXED - Notes in drum MIDI files that have zero length should be interpreted as 16th when importing into Bitwig Studio.
FIXED - Playhead starts in wrong position and not from the blue play marker after bounce.
FIXED - Controller API: Crash when creating named device cursors from onMidi callback.
FIXED - Regression: pasting text does not work on OSX.
FIXED - Not possible to move the loop start for a clip beyond bar 250 using inspector but dragging loop region allows this.
FIXED - Controller API: crash when using device layer bank.
FIXED - Crash if bouncing a track region in place and before the bounce has completed deleting the track.
FIXED - OSX engine crash when scanning certain audio devices.
FIXED - Sometimes engine crashes on OSX when connecting to document.
Important note for Windows users:
Windows might show a warning during installation about the installer not being trusted software. This is only a temporary issue and should disappear soon. In case you see such a message, you can still install the software by clicking "install anyway" (or something similar).
Best wishes from the Bitwig team!
Volker Schumacher, developer at http://www.bitwig.com
-
- KVRist
- 32 posts since 12 Aug, 2015
Thank you for the update! 
-
- KVRAF
- 5144 posts since 3 Oct, 2013
next should be the clip selection speed, it's still super slow (win7x64, Corei7-3770CPU@3.4GHz) if put them "more than 10" midi notes

thx for the update!!!

thx for the update!!!
"Where we're workarounding, we don't NEED features." - powermat
- KVRist
- 198 posts since 20 Jan, 2014 from Latvia
Yes, it's very slow on large projects ;(xbitz wrote:next should be the clip selection speed, it's still super slow (win7x64, Corei7-3770CPU@3.4GHz) if put them "more than 10" midi notes
thx for the update!!!
Thanks for update guys!
Good luck in NAMM!!!
Mac OSX, Bitwig Studio, Spire, Massive
- KVRian
- 797 posts since 2 Nov, 2014
volker@bitwig wrote: FIXED - Creating a clip in the clip launcher using different time signature than 4/4 still creates a clip with 4 quarters duration.
Thanks, i especially appreciate this one
abique wrote:Damn! I forgot to set the default BPM to 140!
Last edited by WXLF on Tue Jan 19, 2016 3:39 pm, edited 1 time in total.
-
- KVRist
- 174 posts since 11 May, 2013 from United States
Is the choke feature for the Drum Machine included? I did not play with the release candidate but I did see the choke feature mentioned in the 1.3.6 RC-1 post.
http://www.kvraudio.com/forum/viewtopic ... 9&t=453209
http://www.kvraudio.com/forum/viewtopic ... 9&t=453209
- KVRian
- 797 posts since 2 Nov, 2014
right click on the drum machine cellstefangx wrote:Is the choke feature for the Drum Machine included? I did not play with the release candidate but I did see the choke feature mentioned in the 1.3.6 RC-1 post.
http://www.kvraudio.com/forum/viewtopic ... 9&t=453209
- KVRian
- 510 posts since 27 Apr, 2013 from Denmark
Is
from RC-1 still in?IMPROVED - Made pencil tool smarter - it now lets you move and extend notes/clips without having to switch to the arrow tool.
- KVRian
- 797 posts since 2 Nov, 2014
I'm not sure what type of document this "FIXED" was addressing but it seems there is still some funny business going on.volker@bitwig wrote: FIXED - Sometimes engine crashes on OSX when connecting to document.
maschine doesn't seem to like bitwig sometimes.

On a side note: When the audio engine button turns orange and indicates it is ready.. Does it ever do so prematurely? sometimes the plugins (like maschine) are not really ready to play. is this normal?
- KVRian
- 1353 posts since 31 Mar, 2014
Great fixes and improvements!
Thank you!
- if the free automation isn't looped, its playhead in the launcher is looped with the clip content
- if the free automation is looped but with a different loop length than the clip content, the playhead isn't looped correctly (different (both incorrect) behaviour when automation loop is shorter/longer than the clip content loop!)
Shouldn't be hard to fix
Cheers!
Yes, the time range of free running automation is displayed correctly now. But the automation play marker in those launcher clips isn't displayed correctly:volker@bitwig wrote:FIXED - Free running automation is not shown correctly in content preview section of launcher clips.
- if the free automation isn't looped, its playhead in the launcher is looped with the clip content
- if the free automation is looped but with a different loop length than the clip content, the playhead isn't looped correctly (different (both incorrect) behaviour when automation loop is shorter/longer than the clip content loop!)
Shouldn't be hard to fix
Cheers!
