PreSonus Forums

Dear Studio One Users,

a new maintenance update is online!
Have a nice conversation.

viewtopic.php?f=151&t=48092&p=281743#p281743

Ari

Thanks, Ari

Thanks Ari...

● Improved tempo detection from ACIDized WAV files.

Seems to be working great now, nice one chaps. Such a small thing to fix but the browser is really powerfull for drag and drop on the fly inspiration. I will give the update more of a run out over the next few days and see how the stuck notes fix works out.

garyanderson5 wroteThanks Ari...

● Improved tempo detection from ACIDized WAV files.

Seems to be working great now, nice one chaps. Such a small thing to fix but the browser is really powerfull for drag and drop on the fly inspiration. I will give the update more of a run out over the next few days and see how the stuck notes fix works out.

Awesome! I am thrilled to see this item addressed.

Cheers

VP

I'm not usually an early adopter, but today upgraded my trusty 5.3.0 to 5.5.2. the first recording session worked out, tracks were recorded, no dropouts experienced. now let's see how that moves on.

yeah, I love those .2 and .3 bugfix releases, so my wish to update was due to a .2 wasn't released in some time.

vasilykorytov wroteI'm not usually an early adopter, but today upgraded my trusty 5.3.0 to 5.5.2. the first recording session worked out, tracks were recorded, no dropouts experienced. now let's see how that moves on.

yeah, I love those .2 and .3 bugfix releases, so my wish to update was due to a .2 wasn't released in some time.

Smart move upgrading 3 months after a major release. Less pain.

Gonna try the unstucking of stuck MIDI notes fix. Anyone noticed any positive signs yet that it might be gone? Good to see this update out now.

Just goes to show that lobbying with cash-filled envelopes does work to improve the system.

PreAl wrote

vasilykorytov wroteI'm not usually an early adopter, but today upgraded my trusty 5.3.0 to 5.5.2. the first recording session worked out, tracks were recorded, no dropouts experienced. now let's see how that moves on.

yeah, I love those .2 and .3 bugfix releases, so my wish to update was due to a .2 wasn't released in some time.

Smart move upgrading 3 months after a major release. Less pain.

Since you can always install multiple versions and use them side by side, it really doesn't matter. 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...

roland1 wroteGonna try the unstucking of stuck MIDI notes fix. Anyone noticed any positive signs yet that it might be gone? Good to see this update out now.

I haven't had this happen with this version so far. Sure, it was a sporadic issue. But a possible cause is fixed now and I did a lot of MIDI editing while testing, so I am optimistic.

Vocalpoint wrote

garyanderson5 wroteThanks Ari...

● Improved tempo detection from ACIDized WAV files.

Seems to be working great now, nice one chaps. Such a small thing to fix but the browser is really powerfull for drag and drop on the fly inspiration. I will give the update more of a run out over the next few days and see how the stuck notes fix works out.

Awesome! I am thrilled to see this item addressed.

Cheers

VP

Happy days

By the way, this one is listed as a bug but I find it a pretty neat improvement actually:

Mute/Solo in music editor mutes/solos the mixer channel not the track

The behavior used to be quite illogical when used with multitimbral instruments or instruments with multiple outputs. If you pressed S (Solo) or M (Mute) while working in the editor, it soloed/muted the channel instead of the track in the arrangement. I personally avoided these shortcuts in the editor for this reason. Now it feels way more logical and I started using them again.

PreAl wroteSmart move upgrading 3 months after a major release. Less pain.

jazzundso wroteSince you can always install multiple versions and use them side by side, it really doesn't matter. 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...

That'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...

Some 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. They just want to use them when they are stable. Others are of course happy doing what you are doing. I'm kind of in the middle, I mostly wait for stability however. Each to their own.

I tried out 5.5.2 yesterday and was getting the 666 noise and meter clipped bug. I rarely get that error but it was happening a lot yesterday. I liked how they got rid of the 666 and replaced it with a frowning face?

Im back on 5.4.1 and not getting that bug. I've been on 5.4.1 because 5.5.1 still has Graphic Acceleration greyed out. The only new plugin I installed recently was the WesAudio stuff for their hardware control.

PreAl wroteThey just want to use them when they are stable.

"when they are stable" does not exist. There may be issues that some experience and others not. There may be issues that interrupt your workflow and issue that do not. But there is no point when a software version is stable. Studio One is no exception. And you can't know if you will experience any issues until you start working with it.

Each to their own.

Exactly. 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.

Many thanks Ari. I am already missing my sticking midi notes Only joking honest.

PreAl wroteThey just want to use them when they are stable.

jazzundso wrote"when they are stable" does not exist. There may be issues that some experience and others not. There may be issues that interrupt your workflow and issue that do not. But there is no point when a software version is stable. Studio One is no exception. And you can't know if you will experience any issues until you start working with it.

Each to their own.

jazzundso wroteExactly. 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.

Just to reiterate...

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...

Stable is mostly a developer term. Stable means it works as per design for the majority of customer use cases. Full releases (non betas) are generally declared stable:
https://en.m.wikipedia.org/wiki/Softwar ... life_cycle
(See subheading "release").

From a user perspective it means they use the software without issue (how they judge that is up to them and their workflow). 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).

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.

I think you are trying to say that no software is bug free, and that is true.

Edited for typos.

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. They just want to use them when they are stable. Others are of course happy doing what you are doing. I'm kind of in the middle, I mostly wait for stability however. Each to their own.

I am all about stability and I do not like to mess up my system by piling on multiple installed versions which always leads to obscure fun and games when it comes time to clean them up.

Basically - I do not trust that S1 can actually clean itself up properly (registry, folders, etc) if I have 7 versions of S1 installed and suddenly decide today that I want to remove 6 of them.

Also - I am very dedicated to application data backups and have several very detailed backup routines which target Presonus specific folders and with 7 versions installed (Until it is very clearly explained to me exactly what gets removed during a multi-version uninstall) - I am very leery of dealing with multiple versions of any software on my DAW.

Cheers

VP

@PreAl:
No need to talk about software development here. I'm just pointing out some options of updating Studio One. You won't know if a software update will work for you until you use it.

Vocalpoint wroteI am all about stability and I do not like to mess up my system by piling on multiple installed versions which always leads to obscure fun and games when it comes time to clean them up.

Basically - I do not trust that S1 can actually clean itself up properly (registry, folders, etc) if I have 7 versions of S1 installed and suddenly decide today that I want to remove 6 of them.

Also - I am very dedicated to application data backups and have several very detailed backup routines which target Presonus specific folders and with 7 versions installed (Until it is very clearly explained to me exactly what gets removed during a multi-version uninstall) - I am very leery of dealing with multiple versions of any software on my DAW.

Cheers

VP

Spot on from my perspective.

And these type of threads are very informative indeed when it comes to working out if an update is any good or not, and whether I should be bothered to install.

Great job
As always Studio One 5 evolving ,with regular updates etc

Maybe not the place for it, but in everyone's opinion (OMG, THAT's opening a can of worms ) is the general state (bugs, features, improvements, etc) of v5 now conducive to my upgrading from V4?