That is precisely why I ditched Bitwig for Cubase in 2018. I looked at the product, then looked at the things I didn't really like about it and realised that it wasn't a product made for people who want to work the way I do and that it would likely never get the things done that I'd like to see done to it, so I ditched it.Imagine being covered under the updates for support as they chase after a demographic that isn't you.
Unless, like me, you have basic issues that, over time, do get attended to. e.g. When I first started using Studio One, trying to open a song on one computer, that you'd created on a different computer, was a nightmare. It wouldn't bring any of the instrument patches across and it wouldn't always find all the instruments, even if they were installed. Partly that was because it had issues with certain instruments, like Thorn and Adam Szabo's VSTi, where it wouldn't recognise them if they had a space in the DLL's name, so I had to be very careful when setting up a new PC to make sure I named everything exactly the same. But when I was setting up my Legion Go a few weeks ago, most of those issues seem to have been resolved. I still had a couple of problems here and there, but mostly it was smooth sailing.The thing is, if you can do on-off years, nothing really changes; it isn't like the updates are getting cranked out at breakneck speeds.
Then there are all the crashing issues I have when trying to close songs. That's one that actually gets worse over time. So I still like to keep bang up to date in the hope that I will have fewer problems. Skipping an update will just feel like resigning myself to another year of regular crashes.
Yeah, I thought the free update from 6.0 to 6.2 was way more meaningful and useful than the paid upgrade to 6.0.And tbf they've kind of already been working this way in practice if not in name: the updates already seem completely decoupled from the majors and semi-majors and they're now just codifying it.
Statistics: Posted by BONES — Sun Oct 06, 2024 1:13 am