3.2 (Beta 1) is OUT!!!

[ChrisDW]

There is no time for anyone to be up to silly antics in this productive forum.

**Antics definition: foolish, outrageous, or amusing behavior.**

[SLiC]

Reading 17 pages per KVR threads takes a lot of time, requires the capacity to digest a lot of negativity and some people are much more vocal than other, which implies an higher bias.

We thank you for taking the time to be active in this forum during the 3.2 beta period!

Absolutely, please hang around, there are some good ideas and useful feedback mixed in among the....other stuff.

[antic604]

There is no time for anyone to be up to silly antics in this productive forum.

**Antics definition: foolish, outrageous, or amusing behavior.**

I'm speechless. Just like you were for 10+ years.

[ChrisDW]

Some people make it so easy for Bitwig devs to simply ignore them.

[PhilipVasta]

Haven't messed too much with this beta yet, but it seems fine overall. I am curious though - when will they get around to actual workflow updates? I don't mind getting a new device or two, they're cool. But there are plenty of little tweaks they could make that would improve its function as a DAW.

Rather than simply complaining, I'd be interested in having a discussion about what we think Bitwig's long-term direction is. Thoughts?

[billcarroll]

Haven't messed too much with this beta yet, but it seems fine overall. I am curious though - when will they get around to actual workflow updates? I don't mind getting a new device or two, they're cool. But there are plenty of little tweaks they could make that would improve its function as a DAW.

Rather than simply complaining, I'd be interested in having a discussion about what we think Bitwig's long-term direction is. Thoughts?

What if devices are part of workflow?

[Kongru]

The way I see it, this is still a .1 update. I wasn't expecting any major changes, even if Bitwig's update subscription ( ) seems to suggest that they wont follow the same pattern as other DAWs. I think Bitwig would still be interested in keeping the highly requested features for numbered versions (i.e 4) to bring in new users and give online publications something to write about.

Ableton took a long time to introduce some features that I would consider essential. It took until version 10 to get multi clip editing, input/ output naming, groups in groups, MP3 export, note chasing, VST3 and some others.

I last used Bitwig in version 1 (and I hated it to be honest) so seeing how much it's changed by version 3 stops me from worrying about their direction too much.

One thing I would like to see is the integration of native devices into the Grid, I'm sure that's on their Trello somewhere.

[PhilipVasta]

What if devices are part of workflow?

I know, there's definitely some grey area here. But to take one example from 3.2, was a new EQ really necessary? Don't get me wrong, I like it. But if we're talking about DAW development, not plugins, then we should examine more general concepts of what a DAW actually is used for. The idea behind the rainbow, for instance, is a good one, and to my mind embodies that workflow improvement idea (of course, the implementation may not be to someone's liking). Even so, I have a feeling that there are a few highly requested items that should be addressed sooner than later.

Anyway, I guess I'm getting caught up in critique. My intention is to ask: do you think bitwig will continue to prioritize devices over more general DAW issues?

[SLiC]

I think ‘devices’ can be developed stand alone and added without affecting everything else, adding something like comping will fundamentally change the structure of the program at the deepest levels....lots to test, lots of affected code, much bigger deal...

[antic604]

When I think of the live arranger, my inner OHM levels raise up high So glad to have Bitwig in place.

What is it exactly that you don't like?

Live v10 made the clips & tracks more easily readable, you can have tracks of all sizes all at once and I'm slowly getting used to - and actually appreciate! - separate automation view. Those new automation tools from 10.1 are fantastic, making a lot of modulation tools redundant. Not having Session and Arranger at one screen doesn't seem to bother me like I thought it would, because you can just grab clip(s) or scene(s), hit Tab and place them on timeline, so you don't have to drag the mouse as much. Live v10 also added full support of trackpad, so you can scroll and zoom around quickly without ever touching that dreaded bar up top. Lastly it's now possible to sidechain directly into VSTs, so there's no need to create extra tracks and routing.

[billcarroll]

What if devices are part of workflow?

I know, there's definitely some grey area here. But to take one example from 3.2, was a new EQ really necessary? Don't get me wrong, I like it. But if we're talking about DAW development, not plugins, then we should examine more general concepts of what a DAW actually is used for. The idea behind the rainbow, for instance, is a good one, and to my mind embodies that workflow improvement idea (of course, the implementation may not be to someone's liking). Even so, I have a feeling that there are a few highly requested items that should be addressed sooner than later.

Anyway, I guess I'm getting caught up in critique. My intention is to ask: do you think bitwig will continue to prioritize devices over more general DAW issues?

Great question. I'd love some focus on MIDI editing.

It occurs to me that I want the Bitwig team making the DAW they envision. I don't think we need another Ableton, or Cubase, or Logic, etc. Those DAWs are amazing in their own right for their own purposes.

Bitwig is a DAW that "sees" music creation in new ways. Choosing a beginner's mind when using a new DAW like Bitwig is pretty key.

Bitwig is obviously a vision by someone to achieve something. Making that vision real is the development process. Staying true to your vision while still taking in a healthy mix of user input (which I think the Bitwig team does) is no easy task.

[antic604]

I think ‘devices’ can be developed stand alone and added without affecting everything else, adding something like comping will fundamentally change the structure of the program at the deepest levels....lots to test, lots of affected code, much bigger deal...

One would think it's such a fundamental feature for many (most?) producers, that architectural decisions would factor it early on, ESPECIALLY if they wanted to set themselves apart from Live? Like the supposed on-line collaboration thing is allegedly built-in already, just not exposed yet.

[Cyoon]

When I think of the live arranger, my inner OHM levels raise up high So glad to have Bitwig in place.

What is it exactly that you don't like?

Live v10 made the clips & tracks more easily readable, you can have tracks of all sizes all at once and I'm slowly getting used to - and actually appreciate! - separate automation view. Those new automation tools from 10.1 are fantastic, making a lot of modulation tools redundant. Not having Session and Arranger at one screen doesn't seem to bother me like I thought it would, because you can just grab clip(s) or scene(s), hit Tab and place them on timeline, so you don't have to drag the mouse as much. Live v10 also added full support of trackpad, so you can scroll and zoom around quickly without ever touching that dreaded bar up top. Lastly it's now possible to sidechain directly into VSTs, so there's no need to create extra tracks and routing.

just the visual appearance of it and the right to left concept, feels unnatural to me. Also when I was working with it last time, I think Live 7-8 it was always really frustrating me. It has so many horizontal lines and no clear color separation that it was difficult to distinguish between the tracks for me. It annoyed me especially because I was used to Cubase 4-6 as my first DAW. Then Bitwig came along and it provides the best of both and even more for me. So never regret, never looked back.

[SLiC]

I don't know, I’m not a coder, but if it isn’t difficult why isn’t real ‘comping’ in Live which has a far, far bigger coding team than Bitwig and has been around almost 20 years! I would still back Bitwig implementing it (probably in a cleverer and fun way) before Ableton, let’s wait and see who gets it first...Also as far as I am concerned Bitwig have already set themselves apart from Live!

[pdxindy]

Good luck with Live... seriously.

Life is too short to spend time being frustrated with software.

Strangely I found that NOT having all those modulators at my disposal so readily lets me do finish stuff and move on more quickly. It helps I started with Live, so I find my way faster than I would 3 years ago. Similar thing with keyboard shortucts - in Bitwig I'd experiment with different versions all the time, switch them around, etc. In Live it's either there or not. Learn & move on. It's refreshing to look at it that way. Perhaps simpler is sometimes better, but then I shouldn't be surprised having tried Cubase and liking the much simpler, "limited" Studio One more

I like simple... GarageBand on iOS is fun!