3.2 (Beta 1) is OUT!!!

[Cyoon]

I don't see comping as an essential feature for synth sound or electronic productions. It's a recording feature and for things like recording 5 takes of a drummer and pic the best parts of his timing etc. Not sure if that is really a requirement in a world where we have quantize and generally a more experimental product instead of a traditional recording DAW. But that's just my personal view on it. Also because I barely record something I guess.

[pdxindy]

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.

Enough about Live already. This is a thread about the Bitwig beta... for reporting and discussing issues, features requests and so on. There have been plenty of Bitwig vs Live threads, so please go post in one of those... preferably in the Hosts forum.

[dreamstate42]

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!

Being simply to develop and being developed are not necessarily related in any way in software development. If it's not fitting into the development plan in terms of working from a backlog, even easy features will not be implemented unless priority gets bumped up.

Live is not focused on recording, and Ableton's UX philosophy has always revolved around "cognitive load", i.e. only essential features that are very straight forward to understand and used. Maybe they haven't found a way to apply this to comping yet, or maybe it's still something they don't consider essential for their core demographic.

Team size is also nothing to draw any conclusions from, because bigger teams are usually organised in specialised teams (devices team, instruments team, core engine team etc.), while small teams are more of a "everyone does whatever is needed". It's a moot point to compare team sizes and say "look how much quicker they are with fewer devs", because you would need to know product and development priorities, as well as organisational structure to say anything about development speed.

[jarnold]

Bitwig was a precocious child and now it's turning in to an underachieving sullen teenager with issues. Lets hope it gets over this period and becomes a high-achieving adult

[lxm]

I don't see comping as an essential feature for synth sound or electronic productions. It's a recording feature and for things like recording 5 takes of a drummer and pic the best parts of his timing etc. Not sure if that is really a requirement in a world where we have quantize and generally a more experimental product instead of a traditional recording DAW. But that's just my personal view on it. Also because I barely record something I guess.

So you are the authority of what electronic music is and how it's made?

Why does it have to be electronic music? I produce lots of other music in Bitwig.

Many many people disagree with you regarding it as being essential.

PS. Don't quantize That's not REAL music

[antic604]

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.

I was reading my old posts here and indeed that's what you said 3 years ago Lots of changes happened since then, on both sides, though:

viewtopic.php?p=6796080#p6796080

Too bad I've not listened to my own advice then

All, thanks for your input and feedback - it's greatly appreciated.

For the time being I'll enjoy my brand new Surface Pro 4 with Ableton Live and impatiently will await what v10 brings to only then decide whether or not branch out to Bitwig.

Thanks again!

[antic604]

Enough about Live already. This is a thread about the Bitwig beta... for reporting and discussing issues, features requests and so on. There have been plenty of Bitwig vs Live threads, so please go post in one of those... preferably in the Hosts forum.

We've been already through the ohhs and ahhs, discussed the new stuff, went through complaining and moved on to conjecturing. Skip my posts if they bother you

[pdxindy]

Enough about Live already. This is a thread about the Bitwig beta... for reporting and discussing issues, features requests and so on. There have been plenty of Bitwig vs Live threads, so please go post in one of those... preferably in the Hosts forum.

We've been already through the ohhs and ahhs, discussed the new stuff, went through complaining and moved on to conjecturing. Skip my posts if they bother you

Uhh... no, 'we' haven't done anything of the sort. I haven't even tried half the new stuff, and there are bugs to report and so on. That is what the beta threads are for and it is useful to keep them on point. There are lots of places you can ruminate about Live.

You of course are far too important to ever respect what a thread is for... thankfully there is the ignore list.

[antic604]

Uhh... no, 'we' haven't done anything of the sort. I haven't even tried half the new stuff, and there are bugs to report and so on. That is what the beta threads are for and it is useful to keep them on point. There are lots of places you can ruminate about Live.

Where are you getting this from? This is a thread I've put up to announce & discuss the beta. I'm not part of Bitwig team or a moderator here, so there's nothing official about it and thus there's no guidelines on what can or can't be discussed.

[Cyoon]

I don't see comping as an essential feature for synth sound or electronic productions. It's a recording feature and for things like recording 5 takes of a drummer and pic the best parts of his timing etc. Not sure if that is really a requirement in a world where we have quantize and generally a more experimental product instead of a traditional recording DAW. But that's just my personal view on it. Also because I barely record something I guess.

So you are the authority of what electronic music is and how it's made?

very logical yes, my personal authority. It's my opinion of course, as I made pretty clear in post, if you read it again.

Why does it have to be electronic music? I produce lots of other music in Bitwig.

because that's the market Bitwig is in for

Welcome to Bitwig Studio 3, the innovative music creation and performance software.

not recording software^^

Many many people disagree with you regarding it as being essential.

great, so be it, that's essential for democratic process.

PS. Don't quantize That's not REAL music

And you are the authority of what is being REAL music then? love when people outperform themselves in the same post. Quantize has it's usecase and there are certain styles of music that require a few things to be perfectly in time..

Have a good day..

[xbitz]

When dragging multiple notes, small chords (up to four notes) will preview all notes; larger chords will sound only the note clicked on
When moving multiple notes with the keyboard, only the earliest note will sound

Cubase can play back all the notes at a given position with alt+clicking on one of them, so chords also can be listened back (not just single notes), please devs

[antic604]

When dragging multiple notes, small chords (up to four notes) will preview all notes; larger chords will sound only the note clicked on
When moving multiple notes with the keyboard, only the earliest note will sound

Cubase can play back all the notes at a given position with alt+clicking on one of them, so chords also can be listened back (not just single notes), please devs

But that's what it says in your own quote - if you select "small" chord (up to 4 notes), Bitwig will audition it.

[xbitz]

"when dragging" ... yepp but I don't want to move them

[antic604]

Many many people disagree with you regarding it as being essential.

Are you aware of "post recording action" feature, ability to edit multiple tracks of audio simultaneously and then bouncing of the Group track? It's a pretty usable workaround for comping if that's not something your whole workflow is based on (i.e. tracking bands, 'traditional' singer-song writer stuff, etc.).

[antic604]

"when dragging" ... yepp but I don't want to move them

Well, all the devs saw on this board was "why doesn't the whole chord play when I select it!" so they've added that. Maybe they were not aware of that further 'requirement'