I'm kind of in the middle, I mostly wait for stability however. Others are of course happy doing what you are doing. They just want to use them when they are stable. PreAl wrote PreAl wroteSome of us don't want or have time to test products that may have issues that may interrupt workflow (stuck midi note anybody?), and don't immediately need to use the latest and greatest new features. I think you are trying to say that no software is bug free, and that is true. ![]() Ultimately what really happens is that the developer declares a release, customers find inevitable bugs which may or may not interrupt workflow, and then they get fixed. Nowadays with the release early release often mantra of agile software development, it can take several months before it can satisfy a users perspective (and that's their judgement call). Full releases (non betas) are generally declared stable:įrom a user perspective it means they use the software without issue (how they judge that is up to them and their workflow). Stable means it works as per design for the majority of customer use cases. PreAl wroteThat's an assumption, there could be a bug that screws up backwards compatibility (rare but certainly not impossible), I've seen that in Native Instruments products before. You can finish current projects in the old version, at the same time you can work with a new update and you can switch to the older version if you experience any issues with a new update. And you can't know if you will experience any issues until you start working with it. But there is no point when a software version is stable. There may be issues that interrupt your workflow and issue that do not. There may be issues that some experience and others not. Jazzundso wrote"when they are stable" does not exist. PreAl wroteThey just want to use them when they are stable. But a possible cause is fixed now and I did a lot of MIDI editing while testing, so I am optimistic. I haven't had this happen with this version so far. Anyone noticed any positive signs yet that it might be gone? Good to see this update out now. Roland1 wroteGonna try the unstucking of stuck MIDI notes fix. Studio One songs are perfectly interchangeable between 5.3 and 5.5 so you can easily try out new updates while finishing current projects with the older versions to be safe. ![]() Since you can always install multiple versions and use them side by side, it really doesn't matter. Smart move upgrading 3 months after a major release. 3 bugfix releases, so my wish to update was due to a. the first recording session worked out, tracks were recorded, no dropouts experienced. PreAl wrote vasilykorytov wroteI'm not usually an early adopter, but today upgraded my trusty 5.3.0 to 5.5.2.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |