The All In One Source Bitwig Information & Speculation Thread
-
- KVRAF
- 42529 posts since 21 Dec, 2005
bitwig is just in beta beta beta. It was in "beta" 2 years ago........they have 2 betas to go before they get it available for public beta. But there will be no public beta (even though the thread title begs the question)
I've got my tardis, I know these things.....
I've got my tardis, I know these things.....
-
- KVRAF
- 4805 posts since 21 Jan, 2008 from oO
Ohmstudio also took years to develop, so what? It's a lot of work to code a DAW. Just chill and give them the time..
JamWide - a cross-platform Ninjam client for DAWs
-
- KVRAF
- 4805 posts since 21 Jan, 2008 from oO
the intention why its coded, like to carbon copy something is totally irrelevant imo, and where did they hype so much..its the community that hypes. just because of their webpage? well, there also was a webpage for ohmstudio.
edit: ok, its an ambitious goal to carbon copy live, wich in my eyes justifies the long time of development even more.
edit: ok, its an ambitious goal to carbon copy live, wich in my eyes justifies the long time of development even more.
Last edited by Cyoon on Thu Nov 21, 2013 10:51 am, edited 1 time in total.
JamWide - a cross-platform Ninjam client for DAWs
-
- KVRist
- 159 posts since 10 Oct, 2013 from Earth
Hi all,
My message is about bitwig's culture and delays.
Unfortunately, these delays can make many of us uncomfortable for the future.
We do not know about why it took so long, and legitimately can worry about the delays, and most probably fear, for instance, that the product will remain in V1.0 "as is" for a long time too.
Bitwig showed a lot of transparency. The product was publicly known 4 or 5 years ago before its release, I've not seen that before for a product release. Even if some will call that "teasing" and see some strategy in it, it's transparency.
Why is it so long ?
I wonder if, generally speaking, a software development process can be so long.
I know a few things on that subject, and can agree with what has been said earlier in this thread about the beta testing phase, but I guess that for a non "software architect" or "project manager", this can be difficult to understand.
After Bitwig 1.0 (support, maintenance, delays)?
It could be a daring challenge to continue with this unprecedented transparency and , in this way, strengthen a very positive image for Bitwig, a quite innovative way of doing with regards do clients, suppliers and competitors. On this track, Bitwig could dare to add product road map diagram that includes history (past) and future, being, of course, very light and simple, only major dates and events. That could make people more confident about the timeline (of course), and the company's culture (way of doing).
Cheers,
B.
My message is about bitwig's culture and delays.
Unfortunately, these delays can make many of us uncomfortable for the future.
We do not know about why it took so long, and legitimately can worry about the delays, and most probably fear, for instance, that the product will remain in V1.0 "as is" for a long time too.
Bitwig showed a lot of transparency. The product was publicly known 4 or 5 years ago before its release, I've not seen that before for a product release. Even if some will call that "teasing" and see some strategy in it, it's transparency.
Why is it so long ?
I wonder if, generally speaking, a software development process can be so long.
I know a few things on that subject, and can agree with what has been said earlier in this thread about the beta testing phase, but I guess that for a non "software architect" or "project manager", this can be difficult to understand.
After Bitwig 1.0 (support, maintenance, delays)?
It could be a daring challenge to continue with this unprecedented transparency and , in this way, strengthen a very positive image for Bitwig, a quite innovative way of doing with regards do clients, suppliers and competitors. On this track, Bitwig could dare to add product road map diagram that includes history (past) and future, being, of course, very light and simple, only major dates and events. That could make people more confident about the timeline (of course), and the company's culture (way of doing).
Cheers,
B.
Last edited by bulusglo on Thu Nov 21, 2013 10:56 am, edited 1 time in total.
Music
-
- KVRAF
- 10170 posts since 2 Jan, 2005 from somewhere in the woods
waiting is horrible, isn't it?
"It dreamed itself along"
-
- KVRAF
- 15135 posts since 7 Sep, 2008
Not sure if you're aware, but other DAWs currently exist.mellotronaut wrote:waiting is horrible, isn't it?
Where would the Stones, Beatles, Elvis etc be if they were constantly waiting for the next thing.
Just use what you have available at the moment. And when BW arrives, investigate that then.
150 odd pages of faffing about, when you all could be doing something constructive.
"I was wondering if you'd like to try Magic Mushrooms"
"Oooh I dont know. Sounds a bit scary"
"It's not scary. You just lose a sense of who you are and all that sh!t"
"Oooh I dont know. Sounds a bit scary"
"It's not scary. You just lose a sense of who you are and all that sh!t"
-
- KVRAF
- 13128 posts since 7 May, 2006 from Southern California
Here is a screen shot of the Arp that was added to the latest beta.
