Safest / least buggy Windows version of Studio One 3?
-
- KVRAF
- Topic Starter
- 2215 posts since 27 Jan, 2011
The latest version. 3.5.2, seems to have some quite major bugs:
https://forums.presonus.com/viewtopic.php?f=151&t=27074
In general I never liked being on the bleeding edge of latest versions, as -- in this case, according to some in the thread -- early adopters sometimes end up doing double-duty as beta testers. I don't need a bunch of new features; I just need the spec which I paid for to be less buggy.
I'm on 3.2.3, which I haven't used to much due to CPU spikes and general crashiness. I'm on W7 64 Pro with an i7, 2.7 ghz CPU, 16 GB of RAM, using a Focusrite Scarlett 2i4.
Do any S1 users have views on which of the versions later than 3.2.3, but earlier than 3.5.2, is mosty stable / debugged / useable?
https://forums.presonus.com/viewtopic.php?f=151&t=27074
In general I never liked being on the bleeding edge of latest versions, as -- in this case, according to some in the thread -- early adopters sometimes end up doing double-duty as beta testers. I don't need a bunch of new features; I just need the spec which I paid for to be less buggy.
I'm on 3.2.3, which I haven't used to much due to CPU spikes and general crashiness. I'm on W7 64 Pro with an i7, 2.7 ghz CPU, 16 GB of RAM, using a Focusrite Scarlett 2i4.
Do any S1 users have views on which of the versions later than 3.2.3, but earlier than 3.5.2, is mosty stable / debugged / useable?
Last edited by lingyai on Mon Nov 27, 2017 11:50 am, edited 2 times in total.
-
- KVRAF
- 1893 posts since 12 Mar, 2004
I was on MacOS with Studio One, it was so poor i sold it and moved on, it's a nice idea of a DAW, but back to back against all the others i own it was the flakiest most resource intensive , again, I was using it with MacOS, supposedly Windows is better.
So the most stable for me was a different DAW entirely, at some point getting work done is more important than a nice idea.
So the most stable for me was a different DAW entirely, at some point getting work done is more important than a nice idea.
Duh
-
- KVRAF
- 2279 posts since 9 Jun, 2002 from East of Santa Monica
Lingyai, you don't say what O.S. you're on. The more info we have, the more helpful it might be to others.
So, folks, if you're going to add your experiences to this thread, please also mention the specific O.S. version you're using (Not simply Mac or PC). Thanks!
So, folks, if you're going to add your experiences to this thread, please also mention the specific O.S. version you're using (Not simply Mac or PC). Thanks!
-
- KVRAF
- Topic Starter
- 2215 posts since 27 Jan, 2011
You're quite right. Should have thought of that. The OS might be especially important in this case, as from what I can gather, Mac people have different / different patterns of problems etc. I've updated the OP.flugel45 wrote:Lingyai, you don't say what O.S. you're on. The more info we have, the more helpful it might be to others.
So, folks, if you're going to add your experiences to this thread, please also mention the specific O.S. version you're using (Not simply Mac or PC). Thanks!
-
Funkybot's Evil Twin Funkybot's Evil Twin https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=116627
- KVRAF
- 11519 posts since 16 Aug, 2006
3.5.1 was a solid version over here.
3.5.2 has been one of the rare "not ready for primetime" S1 releases IMO. Some people have had MIDI notes dropping and I had a few crashes on my desktop when turning on MIDI devices and exiting that didn't happen in prior versions. I'd stick with 3.5.1 until 3.5.3 comes out.
3.5.2 has been one of the rare "not ready for primetime" S1 releases IMO. Some people have had MIDI notes dropping and I had a few crashes on my desktop when turning on MIDI devices and exiting that didn't happen in prior versions. I'd stick with 3.5.1 until 3.5.3 comes out.
- KVRAF
- 5486 posts since 15 Dec, 2011 from Bucharest, Romania
I have the 'not playing all MIDI notes' behavior. And they didn't fixed it yet...
Stay with 3.5.1.
Stay with 3.5.1.
-
- KVRist
- 105 posts since 16 Nov, 2016
No worries, I'm sure they will fix it because it's an obvious issue and overall the PreSonus developers have a good track record in fixing issues the QA specialists understand. Unfortunately some QA specialists have a hard time understanding things, else probably even more would be fixed.e@rs wrote:I have the 'not playing all MIDI notes' behavior. And they didn't fixed it yet...
- KVRAF
- 5486 posts since 15 Dec, 2011 from Bucharest, Romania
I only switched to S1 v3 a few days ago, but this problem has been reported for quite some time on their forum (lots of angry guys there). Hope they didn't sell the DAW to Gibson...
S1 v2 was incredibly stable for me.
S1 v2 was incredibly stable for me.
-
- KVRist
- 105 posts since 16 Nov, 2016
3.5.3 came out today, which fixed the dropped MIDI notes at certain tempos.e@rs wrote:I only switched to S1 v3 a few days ago, but this problem has been reported for quite some time on their forum (lots of angry guys there).
- KVRAF
- 5486 posts since 15 Dec, 2011 from Bucharest, Romania
-
- KVRAF
- Topic Starter
- 2215 posts since 27 Jan, 2011
Sorry, I need to revise my question a bit. This admittedly getting a bit ridiculous, and sorry to be asking for such a piece of historical trivia, but ... which version between v3.3 and whichever preceded v3.5 seems least problematic?
--------------
(That's the question. If you want to know why I'm asking it (not essential, really) it's as follows.
Some folks are reporting new problems with yesterday's 3.5.3 release ... time will tell whether they are exceptional / get solved ... I'd never consider installing somehting so new on principal anyway
https://forums.presonus.com/viewtopic.php?f=151&t=27626
I downloaded 3.5.1 yesterday and was about to install it today, but then I happened to read here
https://forums.presonus.com/viewtopic.php?f=151&t=25825
something that gives me pause -- starting with version 3.5, a number of folks reported that automation was being ignored in some mixdowns, it's hard to reproduce but a fix was to wiggle the mixdown progress indicator box every 30 seconds or so throughout the whole mixdown process. (I'm not making this up!) It appears that the official fix only appeared in yeterday's release, which as mentioned has problems of its own.
This automation -- plus the painful-to-read-about debugging / isolation steps -- is exactly the kind of crap I was experiencing with Sonar Platinum last year, it was really infuriating to spend so much time crafting envelopes and have them ignored during rendering ... defeats the whole purpose. Which is what drove me into the arms of ... S1 v3, specifically v3.2 at the time, which is what I'm on now, but what I need to move on from as a) for me it's a crashy CPU hog and b) to continue to use Melodyne in ARA mode in S1 (which is majorly important to me, now that Sonar is on borrowed time), I had to upgrade to Melodyne 4 , which only works in S1v3.3 and above.
So I'm now having to go back in time to find something which can handle my new Melodyne but avoids the various problems which seem to have started with 3.5.
This side of the hobby sucks out loud. )
--------------
(That's the question. If you want to know why I'm asking it (not essential, really) it's as follows.
Some folks are reporting new problems with yesterday's 3.5.3 release ... time will tell whether they are exceptional / get solved ... I'd never consider installing somehting so new on principal anyway
https://forums.presonus.com/viewtopic.php?f=151&t=27626
I downloaded 3.5.1 yesterday and was about to install it today, but then I happened to read here
https://forums.presonus.com/viewtopic.php?f=151&t=25825
something that gives me pause -- starting with version 3.5, a number of folks reported that automation was being ignored in some mixdowns, it's hard to reproduce but a fix was to wiggle the mixdown progress indicator box every 30 seconds or so throughout the whole mixdown process. (I'm not making this up!) It appears that the official fix only appeared in yeterday's release, which as mentioned has problems of its own.
This automation -- plus the painful-to-read-about debugging / isolation steps -- is exactly the kind of crap I was experiencing with Sonar Platinum last year, it was really infuriating to spend so much time crafting envelopes and have them ignored during rendering ... defeats the whole purpose. Which is what drove me into the arms of ... S1 v3, specifically v3.2 at the time, which is what I'm on now, but what I need to move on from as a) for me it's a crashy CPU hog and b) to continue to use Melodyne in ARA mode in S1 (which is majorly important to me, now that Sonar is on borrowed time), I had to upgrade to Melodyne 4 , which only works in S1v3.3 and above.
So I'm now having to go back in time to find something which can handle my new Melodyne but avoids the various problems which seem to have started with 3.5.
This side of the hobby sucks out loud. )