Bitwig 2.0

[bite_me]

- spectrum analyzer upgrade
- phaser

And the fact that this stuff has been asked since 2014 and they have obviously thought that these are such a big features that they CAN'T be released before 2.0 and so for, they sat over these like a cat guarding its treasure.

Ridiculous.

True! The last ultimate mega feature was GROUP TRACKS

[.jon]

In BWS 1, the modulation can target device parameters inside a container. How does this work with the modulator change?

[jaaypeso]

Originally, I really don't get the premise mentioned earlier that somehow by moving to a pay per calendar year model the Bitwig devs are more likely to release updates more frequently. Or that all of a sudden they can release really cool stuff instantly that they somehow couldn't before. I initially felt that, "nothing stopped them from releasing updates or new devices whenever they felt like it prior to this. But then again I kinda get it as I think it thru. Under this pay structure, you don't have to wait for version 2.0, 3.0, 4.0 to get paid like most developers because people are paying upgrade fees on different cycles. So for example, me and 50 others are paying this month if our 12 month upgrade is due, next month it'll be other people upgrading, and so on and so forth. So devs don't feel compelled to make 3.0 this amazing crazy insane update worthy of the 170 cost which leads to you holding back the TRUE latest and greatest features for that release. Since they are regularly receiving upgrade fees...effectively starting a year from now.

I don't mind the idea that DAW devs get paid more regularly as it creates more incentive to do great work and grow the team to develop faster. I understand that they have families too....can't feed your kids with customer appreciate alone.

The real problem is....bitwig's update and bugfixing speed up to this point has instilled little confidence in people that they'll actually be getting more frequent updates. I'm not so sure i'm buying at this point. I've been dancing with the bitwig beta for a good year or 2 (on and off and i'm by no means indecisive or frugal as I've bought the far more expensive ableton live suite with push 2 within that same time period). But last I checked the undo history still randomly breaks (a deadly bug in my opinion), the drum machine/rack still is missing very basic functionality, the browser is still kinda clunky, and the sampler is still pretty much not noteworthy. They fixed the issue where you had to constantly switch tools between the arranger and the editor to be able to use them both functionality, it appears (so kudos for that). So there is a bit of a show and prove element to all this. If they blow people away with what they do in the actual 2.0 release and over the next 3-6 months I think they can put out the current fire that I see in forums like this one.

The real loser here is anybody who just purchased a license before dec. Now they have to drop another 170 to get features that they basically just paid 300 to have access to. Which sucks for them. I think bitwig is a DAW full of endless potential, but its still just that.... potential.

[jaaypeso]

Originally, I really don't get the premise mentioned earlier that somehow by moving to a pay per calendar year model the Bitwig devs are more likely to release updates more frequently. Or that all of a sudden they can release really cool stuff instantly that they somehow couldn't before. I initially felt that, "nothing stopped them from releasing updates or new devices whenever they felt like it prior to this. But then again I kinda get it as I think it thru. Under this pay structure, you don't have to wait for version 2.0, 3.0, 4.0 to get paid like most developers because people are paying upgrade fees on different cycles. So for example, me and 50 others are paying this month if our 12 month upgrade is due, next month it'll be other people upgrading, and so on and so forth. So devs don't feel compelled to make 3.0 this amazing crazy insane update worthy of the 170 cost which leads to you holding back the TRUE latest and greatest features for that release. Since they are regularly receiving upgrade fees...effectively starting a year from now.

I don't mind the idea that DAW devs get paid more regularly as it creates more incentive to do great work and grow the team to develop faster. I understand that they have families too....can't feed your kids with customer appreciate alone.

The real problem is....bitwig's update and bugfixing speed up to this point has instilled little confidence in people that they'll actually be getting more frequent updates. I'm not so sure i'm buying at this point. I've been dancing with the bitwig beta for a good year or 2 (on and off and i'm by no means indecisive or frugal as I've bought the far more expensive ableton live suite with push 2 within that same time period). But last I checked the undo history still randomly breaks (a deadly bug in my opinion), the drum machine/rack still is missing very basic functionality, the browser is still kinda clunky, and the sampler is still pretty much not noteworthy. They fixed the issue where you had to constantly switch tools between the arranger and the editor to be able to use them both functionality, it appears (so kudos for that). So there is a bit of a show and prove element to all this. If they blow people away with what they do in the actual 2.0 release and over the next 3-6 months I think they can put out the current fire that I see in forums like this one.

The real loser here is anybody who just purchased a license before dec. Now they have to drop another 170 to get features that they basically just paid 300 to have access to. Which sucks for them. I think bitwig is a DAW full of endless potential, but its still just that.... potential.

[jaaypeso]

sorry for the double post above. It didn't go thru the 1st time an then both posted.

[Coockie1176ln]

sorry for the double post above. It didn't go thru the 1st time an then both posted.

No worries just go to ine off em edit and write removed and update that message

[M.L.M.]

Where can we find this?




This was announced as a part of 2.0 and the Online Collab

[Rappo Clappo]

@M.L.M.

What is that?

[anttimaatteri]

after sleeping over the initial reading about 2.0 and its payment policies, i came to the conclusion that it would have been the far better option to make the license model depending on release numbers (similar to renoise), buying the release 1.3.x gives u granted update til 2.3.x asf...ther solution now has a bitter taste on it. at least for all those who run with bitwig since 1.0 even if it was the last time they get it that way. theres one thing to keep in mind. a lot of these people bought 1.0 under a certain impression to get some stuff advertised on the website at the time of release or even from beta: the modular system.

second, compared to abletons pricing of its live suite (and other high price daws) the initial price for bitwig was a smaller budget and even with 159 bucks for 2.0 on top of it its still less then abletons live suite. but things will get tighter and tougher when 3.0 will be out (depending on what will be delivered) and at least at that point bitwig has to deliver big time!

third, fl studio lifetime update. nuff said. i can see by a mile that a lot of "classic" users (the one who dont give a dime on touch screens or waiting for modular stuff) will run in that direction.

bitwig devs aggregated a huge pile of pressure for themselves.

and to clear things out, my initial reaction to all this 2.0 hassle goin on even was "hm ok. could have been much worse. i maybe deal with it...maybe".


good luck

[M.L.M.]

@ Rappo Clappo

this was announced as the next big thing in Bitwig 2 (Modulation Polysynth) in the year 2014.

[Rappo Clappo]

@ Rappo Clappo

this was announced as the next big thing in Bitwig 2 (Modulation Polysynth) in the year 2014.

Ikr, it was *promised* in March 2014. But not the retina implementation (of course these apple dudes have the most money to waste), not the smokescreen AKA browser. And they spent several months on that stuff.

[BobDog]

Yeah, it was announced in 2012 that it would be in ver 2.

[Lejurai]

Where can we find this?




This was announced as a part of 2.0 and the Online Collab

From Mulab

[codec17]

Please..... Let multi track editing had some love.

[Lejurai]

Let there be sad cat pics

Cat.jpg