Bitwig modulation mapping preview

[VitaminD]

Those features seems quite developed, I wonder if they are reserved for a 2.0 or 1.x update???

According to Bitwig, accessing the modular structure and multi-user collaboration are for 2.0

Which sounds like a long wait, but I get the impression 2.0 will happen relatively quickly after the initial release. More speculation, but that's how I see it.

This is a bit infuriating/frustrating to me if they have already developed the 2.0 features before releasing 1.0 while we're all waiting for it..

Why not get 1.0 out of the door, appease the masses while working out kinks, and THEN work on building 2.0?

I also get the feeling there will be something near worthless like a 1 or 2 week 'open beta' which will essentially be a polished, time locked version 1. Since I don't see them actually releasing a typical beta (with bugs).. they seem to be smoothing over every possible bump in closed before releasing it to the public. Again, frustrating.

The open beta won't be an open beta. It will be an open trial. The whole product will be in place and there will be very little (if any) molding of the software through feedback as it will already be completed!


At some point the developers have to stop thinking like developers and more like businessmen in realizing the code will never be perfect and you don't get paid unless you release. Of course they are taking their sweet time to make it 'right', but what good is it to us if they never release?

Seeing 2.0 features seemingly far along in the development process (before version 1 has been released) makes me growl.. and sigh.


roars.


All could have been avoided had they not announced so soon. That was a big oops imo. They could have stole a lot more thunder from Ableton had they announced as early as February of this year. The software would be fresh news and I'm guessing more people would have held out for BWS over Live9 had they not already have been waiting a solid year..




This concludes my rant. I am better now.

[ZenPunkHippy]

meh

[UncleAge]

At some point the developers have to stop thinking like developers and more like businessmen in realizing the code will never be perfect and you don't get paid unless you release. Of course they are taking their sweet time to make it 'right', but what good is it to us if they never release?

OMG, you're advocating for a more buggy release???

[ghettosynth]

Those features seems quite developed, I wonder if they are reserved for a 2.0 or 1.x update???

According to Bitwig, accessing the modular structure and multi-user collaboration are for 2.0

Which sounds like a long wait, but I get the impression 2.0 will happen relatively quickly after the initial release. More speculation, but that's how I see it.

This is a bit infuriating/frustrating to me if they have already developed the 2.0 features before releasing 1.0 while we're all waiting for it..

Why not get 1.0 out of the door, appease the masses while working out kinks, and THEN work on building 2.0?

I don't quite see it that way. They have probably developed the modular infrastructure sufficiently to develop the devices that they are delivering, but have not yet built out all of the details of the editing environment necessary for a complete product. Think of the difference between max and Pd, only more extreme. To me, it makes some sense to build a flexible framework and then build your product on top of that, then plan user access to that framework in a future release.

Now, I'm not getting all excited, I'm quite satisfied with live 9 and (soon) reason 7. In fact, I know that I won't waste my time considering bitwig until 2.0. They've told me all that I need to know by telling me that I won't have access to the modular framework.

[trimph1]

I like what I am seeing in the previews, but, dammit, give us the ruddy thing, will ya!!!!!

[ZenPunkHippy]

They have probably developed the modular infrastructure sufficiently to developer the devices that they are delivering, but have not yet build out all of the details of the editing environment necessary for a complete product

That would be the exact answer

[ghettosynth]

They have probably developed the modular infrastructure sufficiently to developer the devices that they are delivering, but have not yet build out all of the details of the editing environment necessary for a complete product

That would be the exact answer

Man, I can't believe that I left those two giant typos sticking out like sore thumbs! I guess that it's time to head back to school already. Damn it!

[AlienForce]

So in live, if you have a synth patch and you want to make some macroknobs for it and you select for instance cutoff (which for instance currently is at 46%), it would snap back to 0% if you assigned it to a macro? Do i understand it right? Sorry for long sentence

Yep. In Live 8 and 9 as well.

There is an option you can turn on in the options.txt that gets rid of this I believe
-AutoAdjustMacroMappingRange

I think is the one, you can also add -EnableMapToSiblings, to give you the option to map the same value on a rack to the same macro for all siblings, i.e. map volume of all simpler's in a rack to the same macro knob at once

Great info! Thanks.

[vastarray]

Why are they working on a synth? I thought they were developing a DAW.

[jeffh]

This is a bit infuriating/frustrating to me if they have already developed the 2.0 features before releasing 1.0 while we're all waiting for it..

Why not get 1.0 out of the door, appease the masses while working out kinks, and THEN work on building 2.0?

I can tell you exactly why... I'm sure that they intended to release this as part of v1.0, but now they're stripping it out because they're realizing that they would have to delay the rest of it perhaps years in order to make it part of v1.0. Financially it would've made no sense to spend the time writing it when they have no product yet and therefore no income..

They really just bit off more than they could chew, and Bitwig will probably always be plagued with bugs because of it. They should've started with a simpler and more modest DAW for v1.0, and then built on top of that stable base, but they didn't, and now they are paying the price...

[VitaminD]

At some point the developers have to stop thinking like developers and more like businessmen in realizing the code will never be perfect and you don't get paid unless you release. Of course they are taking their sweet time to make it 'right', but what good is it to us if they never release?

you're advocating for a more buggy release???

Yes. Yes I am!!! ..of the BETA.


I see the reasons made for the 2.0 stuff already appearing.. I guess I'll go with that..


I guess they would need to write the underpinnings early on and then flesh it out later.. probably a lot easier than retroactively designing a modular system for one..


I still think they were too early with announcing the product... but what is done is done.. probably only 3 or 4 months left





















..or 5.. or 6... or 7...

When a release date and price are announced it will probably be out of my 200 dollar range anyways. All this wait to discover its beyond my budget

[UncleAge]

I guess they would need to write the underpinnings early on and then flesh it out later.. probably a lot easier than retroactively designing a modular system for one..

I hope they get this part right. From the propaganda that I have seen, the ability to roll your own devices is the only part that really interests me.

[zerocrossing]

Bitwig Studio comes with a Javascript API for controllers.. surely the more used controllers will have mappings shortly after release (if not AT release)


The only thing that concerns me is pricing... they are still being quiet on price.. they already know what is going to be included in the product at version 1 (all on their homepage in screenshots), so why not release the price?

I thought they announced it at $399 a long time ago. No?

[UncleAge]

Bitwig Studio comes with a Javascript API for controllers.. surely the more used controllers will have mappings shortly after release (if not AT release)


The only thing that concerns me is pricing... they are still being quiet on price.. they already know what is going to be included in the product at version 1 (all on their homepage in screenshots), so why not release the price?

I thought they announced it at $399 a long time ago. No?

$400 is not in the impulse buy range. They may have to rethink that number if they release it so close to the Live9/Reason7 releases.

[pc999]

When a release date and price are announced it will probably be out of my 200 dollar range anyways. All this wait to discover its beyond my budget

I understand you so well... and I am not even sure if I can save 200 by summer (or at all) for a DAW or anything else with the economy as it is, and worst even by summer

Irony of the ironies, it is this way because (mostly) of German/USA (and a few others) banks/hedge funds/... and in the end their citizens will be the ones to lose more. On top of that many of the countries that are starting to go the austerity route don't even have reliable news of the effect of austerity...


Maybe with a GOOD introductory deal for us ...( we know you read this)