Bitwig Studio 3.3 announced + beta started
-
- KVRAF
- 1524 posts since 6 Nov, 2012
So they won't release point next version until they fix issues? Such a bold statement if it is true. It should delays development pace significantly but as an update subscriber it would be relief.
- Banned
- Topic Starter
- 11467 posts since 4 Jan, 2017 from Warsaw, Poland
No, they'll just leave the bugs in 3.2.8 and fix them in 3.3.x.tooneba wrote: Mon Oct 19, 2020 12:15 pm So they won't release point next version until they fix issues? Such a bold statement if it is true. It should delays development pace significantly but as an update subscriber it would be relief.
Although obviously if they're really serious bugs - that crash the DAW or make it unusable for sizeable portion of users - then they won't release new version until previous is patched.
No software is perfect and all have bugs. Live 9.7 has them. Cubase 10 has them. Studio One 4.6 has them. Reason 10.4 has them, etc. Devs of those DAWs don't come back and fix them, they've moved to 10.1, 10.5, 5.0 and 11.3 respectively and fix problems there. There's lots of Bitwig users who are still on 1.3.16 and they're doing just fine
-
- KVRAF
- 1524 posts since 6 Nov, 2012
IIRC I got updates for Live 8 and Live 9 after successive version were released.antic604 wrote: Mon Oct 19, 2020 12:25 pmNo, they'll just leave the bugs in 3.2.8 and fix them in 3.3.x.tooneba wrote: Mon Oct 19, 2020 12:15 pm So they won't release point next version until they fix issues? Such a bold statement if it is true. It should delays development pace significantly but as an update subscriber it would be relief.
Although obviously if they're really serious bugs - that crash the DAW or make it unusable for sizeable portion of users - then they won't release new version until previous is patched.
No software is perfect and all have bugs. Live 9.7 has them. Cubase 10 has them. Studio One 4.6 has them. Reason 10.4 has them, etc. Devs of those DAWs don't come back and fix them, they've moved to 10.1, 10.5, 5.0 and 11.3 respectively and fix problems there. There's lots of Bitwig users who are still on 1.3.16 and they're doing just fine![]()
- Banned
- Topic Starter
- 11467 posts since 4 Jan, 2017 from Warsaw, Poland
From 9.7.7 release notes (which was released 4 months after 10.0 came out):tooneba wrote: Mon Oct 19, 2020 1:06 pmIIRC I got updates for Live 8 and Live 9 after successive version were released.
Well, they'd better fix s**t like thatLive could crash when loading a Set, if a Max for Live device was mapped to a macro control.
I'm not aware of any bugs crashing Bitwig in 3.2.8
- KVRist
- 485 posts since 1 Mar, 2010
Why does every Bitwig thread devolve into discussing their licensing model? We should really just start linking people to an explanation and get back to discussing the update.
- Banned
- Topic Starter
- 11467 posts since 4 Jan, 2017 from Warsaw, Poland
But most of them understand it perfectly well, but either don't like it - which is fair - or conceive some made up scenarios to get mad at itcoroknight wrote: Mon Oct 19, 2020 1:24 pmWhy does every Bitwig thread devolve into discussing their licensing model? We should really just start linking people to an explanation and get back to discussing the update.
In the end it's about maximising [ (features + fun) / money ] ratio. If one can afford it, then they shouldn't care if the DAW that maximises it for them is the most expensive, because the alternative is to use something cheap and feel miserable and/or constrained while doing so. And it's obvious that for every person those 3 elements will be different & have different weights, which adds further to making the discussion complex.
-
- KVRAF
- 2989 posts since 5 Nov, 2014
Because it's one of the "arguments" why Bitwig suck for some people who need to feel better about themselves and their life choices, only way they can be up is when they try to bring someone else down.coroknight wrote: Mon Oct 19, 2020 1:24 pm Why does every Bitwig thread devolve into discussing their licensing model?
-
- KVRAF
- 1524 posts since 6 Nov, 2012
Because it's annoyingcoroknight wrote: Mon Oct 19, 2020 1:24 pm Why does every Bitwig thread devolve into discussing their licensing model? We should really just start linking people to an explanation and get back to discussing the update.
- Banned
- Topic Starter
- 11467 posts since 4 Jan, 2017 from Warsaw, Poland
And which company told you exactly which updates you're gonna get and for how long? Definitely not Ableton.tooneba wrote: Mon Oct 19, 2020 1:54 pmIt looks company is trying to sell things without telling buyer enough idea what is going on.
- Banned
- Topic Starter
- 11467 posts since 4 Jan, 2017 from Warsaw, Poland
Because that never happened?tooneba wrote: Mon Oct 19, 2020 1:54 pmBecause it's annoyingWhy don't explicitly say you only get 0.1 update for $140.
-
- KVRAF
- 2514 posts since 28 Sep, 2012
Well, they do:tooneba wrote: Mon Oct 19, 2020 1:54 pmBecause it's annoyingcoroknight wrote: Mon Oct 19, 2020 1:24 pm Why does every Bitwig thread devolve into discussing their licensing model? We should really just start linking people to an explanation and get back to discussing the update.Why don't explicitly say you only get 0.1 update for $140. It looks company is trying to sell things without telling buyer enough idea what is going on.
https://www.bitwig.com/support/shop_lic ... an-work-5/So if you are on version 3.1 when your plan expires, you will be able to download and use 3.1.1, 3.1.2, etc. Version 3.2 will be unavailable until you renew your Upgrade Plan.
-
- KVRAF
- 1524 posts since 6 Nov, 2012
Yeah right? So it is different from Bitwig's update philosophy: Iron out almost all issue before next point release OR ditch expired subscribers. It is like "delaying new release not to betray user base" or "just betray user base and move on". Support subscription is basically "ignore expired subscribers" model. So I don't blame them for it though.antic604 wrote: Mon Oct 19, 2020 1:15 pmFrom 9.7.7 release notes (which was released 4 months after 10.0 came out):tooneba wrote: Mon Oct 19, 2020 1:06 pmIIRC I got updates for Live 8 and Live 9 after successive version were released.
Well, they'd better fix s**t like thatLive could crash when loading a Set, if a Max for Live device was mapped to a macro control.![]()
I'm not aware of any bugs crashing Bitwig in 3.2.8![]()
- Banned
- Topic Starter
- 11467 posts since 4 Jan, 2017 from Warsaw, Poland
Yes, you're right. We're all stupid and gullible. And you're the only clever person here, who've seen through their cunning plottooneba wrote: Mon Oct 19, 2020 2:05 pmYeah right? So it is different from Bitwig's update philosophy: Iron out almost all issue before next point release OR ditch expired subscribers. It is like "delaying new release not to betray user base" or "just betray user base and move on". Support subscription is basically "ignore expired subscribers" model. So I don't blame them for it though.
- KVRAF
- 26976 posts since 3 Feb, 2005 from in the wilds
That is a misunderstanding on your part and simply not true.tooneba wrote: Mon Oct 19, 2020 1:54 pmBecause it's annoyingcoroknight wrote: Mon Oct 19, 2020 1:24 pm Why does every Bitwig thread devolve into discussing their licensing model? We should really just start linking people to an explanation and get back to discussing the update.Why don't explicitly say you only get 0.1 update for $140. It looks company is trying to sell things without telling buyer enough idea what is going on.
If someone buys an update plan and activates it, they will get ANY updates during the following 12 months. If V4 comes out during that time, they get it.