Bitwig Studio 1.3.13 RC-1

​

Changes in Bitwig Studio 1.3.13 RC 1
Released on 17.08.2016.

FIXED - Entering in invalid file name characters for the exported audio file name causes strange problems when exporting.
FIXED - Regression: Recording automation into a new clip on the clip launcher causes automation points to be written at an incorrect time.
FIXED - Regression: tempo in beat marker inspector shows always -0.
FIXED - Rare crash when undoing the moving of a track to the effect track area.
FIXED - Copying a scene between 2 projects does not copy nested chain sends correctly and the nested effect track names are also not copied.
FIXED - Recording clip launcher automation still records into the first clip if you start a second one.
FIXED - Dragging a layer or drum chain to a new track still leaves macros mapped to volume, pan or send of the layer.
FIXED - Crash when undoing the move of a drum pad to a new track with a macro mapped to the pad's volume.
FIXED - Automation thinning sometimes didn't work when writing clip launcher automation.
FIXED - Crash when parsing metadata out of plugins that write lots of data and get into an infinite loop (e.g some versions of the RapidComposer.vst plugin on Mac OSX).
FIXED - Potential fix for "White Screen" problem experienced by some Windows users.

More info here (DDL links)

Source

 

They should add time signature changes (in the middle of a song), bug fixes are great but this is a basic feature that is greatly needed. Bitwig doesn't get much love here saddly, it's such a fun and great DAW for songwriting.

 

I totally agree. I don't know why this DAW isn't more popular?

 

I think it's because most people are already comfortable using Live and are not interested in giving Bitwig a try.

 

Well they don't know what they are missing out on Ferdinand!

 

That's been my main, if not sole, complaint about Bitwig. Otherwise, it's a great DAW. For me, it's similar to Live but easier to use (mainly due to Live's GUI being so unwelcoming and Bitwig's being really cozy. Bitwig is otherwise thoughtfully-designed accommodating. Greater AU compatibility would help, though.

 

Exactly. To me Bitwig combines the best of Live (creativity, fun devices) and S1 (almost identical workflow and interface). I just can't get enough of it, it deserves more recognition. I also love the GUI, very inspiring and easy on the eyes.

 

worth to mention that because Bitwig has quite free routing system the ReaJS based JFSX devices working quite nicely in it

the inner-track routing system of Reaper can be converted to outer-track routing one in BWS easily

for ex. this is the chord splitting one

http://www.reaper.fm/reaplugs/

there are some

...

ofc. it can work in any DAW just in Bitwig the routing system is a modular like so can be used more comfortable than in the other DAWs

(started a topic about in the official forum, seems JSFX based VST devices are not an obviously known things https://www.kvraudio.com/forum/viewtopic.php?f=259&t=468474 )

 

Last edited: Aug 19, 2016

still no fadercaps ?

 

Nope, not yet unfortunately.

 

Bitwig lacks a lot if you compare it with Ableton. Ableton lacks major things as compared to Bitwig.

 

That's why I use both. But Bitwig does lack a few fundemental features, I'm sure they'll add them sppm in upcoming updates.

 

Mates, why the hell are you used to compare Ableton Live 9 and Bitwig 1.3? The first one is born a lot of years ago. The second is still a baby and needs to grow up. Live is a standard (for who like its ugly UI and use it year by year) even if it will never be like ProTools (imo the KING of DAWs - I'm in love with its lovely mixer).

There was a day I was used to think FL Studio was the best. I am a Bitwig user now (FL Studio is still my first "lover") 'cause it let me do some "things" easier than FL. I use both and, maybe, waiting the next black friday, I'll could buy Live to try it to figure out pros and cons and why @ArticStorm says "switching is a wasts of time for me" every time I post news about that DAW.