If it were true for all systems, but it's only a small fraction of users. That's the important fact here that seems to be missing in most the debates and arguments from people who just can't understand the entire situation.jtrake wrote:Everytime someone have mentioned that S1 performs worse than other DAWs on their system there is always someone who claims that the system is wrongly configured , they don't know how complicated DAWs are, they are using S1 on an underpowered computer.
I have come to the conclusion that they who are making these claims cannot think logically, don't know anything about computers, has never compared S1 to another DAW on the same system with small buffer setting, cannot understand that not everyone uses their DAWs the same way that they are or has to be on Presonus payroll.
Just accept that S1 has bad CPU performance compared to other daws when using small buffer settings. Also accept that not everyone but you are computer noobs out there and that you are not the only one in the world who knows how computers should be configured for best DAW performance. I know Its abscary thought but consider that it might be the case before claiming that a user has a badly configured or underpowered system.
If S1 performance is enough for someone does not mean that it is for everyone.
Well, we are spoilt with DAW options today and everyone can probably find one that works for their personal workflow. I have abandoned S1 for another DAW but will maybe give it another try, the day they do something about the CPU performance. DubbleBuffers or something like that.
You happy with Studio One 3?
- Banned
- 55 posts since 4 Nov, 2016
- KVRAF
- 1950 posts since 17 Jun, 2005
Then it must be nice to see it isn't missing in minenostradamoose wrote:If it were true for all systems, but it's only a small fraction of users. That's the important fact here that seems to be missing in most the debates and arguments from people who just can't understand the entire situation.
Yes, I would guess it's exactly a small fraction of Studio One users who have tried using it for large hybrid production templates or other similarly resource intensive cases (for example, technical EDM genres with high instance counts and a lot of creative routing). When the system itself is configured and maintained to professional standards, it's unlikely to be the culprit, especially if other environments on the same system don't falter as easily. Understanding that use cases range very dramatically seems to be missing in most arguments to the contrary.
nostradamoose wrote:Unfortunately I don't have time to read your long winded opinion, let's just agree to disagree.
No comments on any of the technical or historical points? Cool. I don't have more time to deal with your opinion either. Agreement on disagreement reached.
Last edited by Guenon on Thu Nov 10, 2016 7:32 pm, edited 1 time in total.
-
- KVRer
- 19 posts since 21 Aug, 2007
My understanding is that Studio One underperforms for the majority of users, compared to other daws.nostradamoose wrote:If it were true for all systems, but it's only a small fraction of users. That's the important fact here that seems to be missing in most the debates and arguments from people who just can't understand the entire situation.jtrake wrote:Everytime someone have mentioned that S1 performs worse than other DAWs on their system there is always someone who claims that the system is wrongly configured , they don't know how complicated DAWs are, they are using S1 on an underpowered computer.
I have come to the conclusion that they who are making these claims cannot think logically, don't know anything about computers, has never compared S1 to another DAW on the same system with small buffer setting, cannot understand that not everyone uses their DAWs the same way that they are or has to be on Presonus payroll.
Just accept that S1 has bad CPU performance compared to other daws when using small buffer settings. Also accept that not everyone but you are computer noobs out there and that you are not the only one in the world who knows how computers should be configured for best DAW performance. I know Its abscary thought but consider that it might be the case before claiming that a user has a badly configured or underpowered system.
If S1 performance is enough for someone does not mean that it is for everyone.
Well, we are spoilt with DAW options today and everyone can probably find one that works for their personal workflow. I have abandoned S1 for another DAW but will maybe give it another try, the day they do something about the CPU performance. DubbleBuffers or something like that.
The important fact here is that you don't seem to understand the entire situation.
- KVRian
- 711 posts since 19 Jan, 2008
As I've said earlier, most people us it for mixing and recording and at that task is not so noticeable, that's why most people don't report such problems, because they think it's suppose to work this way. People start reporting problems when it's annoying and can't finish work, that's why people that use a lot of VSTi's report this problem.
-
beatmangler443 beatmangler443 https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=306784
- KVRist
- Topic Starter
- 421 posts since 11 Jun, 2013
Not most some users. It's some users. When I look at the studio 192 and presonus studio one facebook some people actually have underspeced computers. We can talk about presonus, but how many years did it take for Steinberg to fix the cpu load and cpu spikes for cubasecoolbass wrote:My understanding is that Studio One underperforms for the majority of users, compared to other daws.nostradamoose wrote:If it were true for all systems, but it's only a small fraction of users. That's the important fact here that seems to be missing in most the debates and arguments from people who just can't understand the entire situation.jtrake wrote:Everytime someone have mentioned that S1 performs worse than other DAWs on their system there is always someone who claims that the system is wrongly configured , they don't know how complicated DAWs are, they are using S1 on an underpowered computer.
I have come to the conclusion that they who are making these claims cannot think logically, don't know anything about computers, has never compared S1 to another DAW on the same system with small buffer setting, cannot understand that not everyone uses their DAWs the same way that they are or has to be on Presonus payroll.
Just accept that S1 has bad CPU performance compared to other daws when using small buffer settings. Also accept that not everyone but you are computer noobs out there and that you are not the only one in the world who knows how computers should be configured for best DAW performance. I know Its abscary thought but consider that it might be the case before claiming that a user has a badly configured or underpowered system.
If S1 performance is enough for someone does not mean that it is for everyone.
Well, we are spoilt with DAW options today and everyone can probably find one that works for their personal workflow. I have abandoned S1 for another DAW but will maybe give it another try, the day they do something about the CPU performance. DubbleBuffers or something like that.
The important fact here is that you don't seem to understand the entire situation.
-
- KVRian
- 721 posts since 23 Jun, 2004
Thanks. I had been trying to stick with one format to avoid potential problems by not mixing AU with VST in the same session. However some of my plugs don't have VST3 so I'd be forced to use AU with VST. In fact I was just instantiating SoundToys (VST2) which crashed S1, and my only alternative for that would be to use AU (which would then violate my do-not-mix-both-formats rule). Do you notice any issue having both AU and VST3 in a session?aMUSEd wrote:Yeah because S1 supports aupresets better than most other hosts except Logic it's nice to be able to use the presets interchangeably so that was one factor. I use AU and VST3 as some VST3 plugins don't come as AU or visa versa. I stopped using VST2 after finding S1 crashing frequently when I tried to load one onto a track. tbh it's possible that was a bug that has since been fixed but I don't really need them anyway.macmuse wrote:Are you using VST3 then, or just AU? What differences do you find now? I use only VST in my projects (mainly because of the MIDI out) but I dint disable the AU and things seem Ozk, so I wondered what problems you were having (e.g. if mine could be even further improved).aMUSEd wrote:I'm pretty happy with it now - since I removed VST2 support it's a lot more stable on my Mac. What I particularly like about it is it's the only DAW I have that fully supports all major plugin formats on Mac which makes it much easier to access all my plugins and their presets (don't need VST2 since on Mac I don't have any that are just VST2). I also find it the easiest to create whole albums with and publish music with.
When deciding which format to stick with, The one draw of AU was the presets that I had saved in the past that could also go back and forth with Logic, but ultimately the MIDI out won (VST).
-
- KVRist
- 388 posts since 2 Mar, 2003 from UK
Yes.beatmangler443 wrote:You happy with Studio One 3?.
- Banned
- 55 posts since 4 Nov, 2016
Are these poll results coming from the same ones Hillary fanboys were using?coolbass wrote:My understanding is that Studio One underperforms for the majority of users, compared to other daws. The important fact here is that you don't seem to understand the entire situation.
- Banned
- 55 posts since 4 Nov, 2016
When will Studio One 3 work with McDSP, SofTube, & Kush plugins on Win10 without win 8 compatibility Mode engaged?
http://answers.presonus.com/7566/studio ... ty-engaged
http://answers.presonus.com/7566/studio ... ty-engaged
These plugins are all iLok dependent and as such are subject to the iLok Manager and its compatibility with Windows 10. PreSonus did put out an announcement addressing this issue:
http://support.presonus.com/hc/en-us/ar ... Windows-10
In recent months iLok has released 2 major updates to the iLok Manager and many of our customers have since, no longer had an issue with the iLok Plugin / Windows 10 Compatibility issues that were first seen with the public launch of Windows 10. This is not a PreSonus software issue, but rather a compatibility issue with iLok Plugins and Windows 10.
- KVRist
- 36 posts since 4 Jan, 2016
I am kind of tired of explaining the performance issue with Studio One to people who can't see it or don't understand it. But here we go.nostradamoose wrote:Are these poll results coming from the same ones Hillary fanboys were using?coolbass wrote:My understanding is that Studio One underperforms for the majority of users, compared to other daws. The important fact here is that you don't seem to understand the entire situation.
If you use Studio One for mixing where you don't have to think about latency and can have the buffer settings high like 1024, it works as good as any other DAW.
The performance issues surface when you for example compose with VSTi instruments by playing them on midi keyboard or record guitars using vst smp simulations. In these situations a buffer 128 samples is about as high as one want to go and in these situations S1 performs much worse than the other major DAWs like Logi,Cubase, DP, Protools.
The other daws has functionality like running tracks that is not record enabled with much higher buffers than the record enabled track or freezing recorded tracks in the background, to free up CPU cycles so that one can can preserve the low latency buffers (<=128) for as long as possible without having to stop and start manually bounce tracks or rise the buffer wich will affect the performance when recording.
At this point S1 does not have a functionality like this. The buffer setting that you set is the same for all tracks and becadu of this you will hit into cpu performance issues much earlier that with the other DAWs shen you compose music using ITB instruments and effects.
In thesd scenarios S1 performs worse than the other DAWs any system and that is not s matter of user error or system config error. It is just how S1 is coded and there is no way around that.
Where you just can keep adding tracks and continue recording with low buffer settings/latency with other DAWs you have to start bouncing tracks or rise the buffers and introduce higher latencies when working with S1.
So this is what I am waiting for. Some kind of hybrid buffer engine for S1 or other solution to fight this issue. Until then I am using other options but would seriously consider S1 if it was more CPU effective in low latency scenarious. Just because everything else is really nice with it
- KVRian
- 711 posts since 19 Jan, 2008
jtrake, it's not only that. I've made a test myself with Serum on Studio One 3 and Bitwig and on Studio One core 0 is hitting 100% while the rest are at 20-30%. In Bitwig the load is evenly distributed between all cores and I don't get dropouts and I am left with some headroom so I can add even more.
- KVRist
- 36 posts since 4 Jan, 2016
Ok, that also adds to the CPU issues then.nIGhT-SoN wrote:jtrake, it's not only that. I've made a test myself with Serum on Studio One 3 and Bitwig and on Studio One core 0 is hitting 100% while the rest are at 20-30%. In Bitwig the load is evenly distributed between all cores and I don't get dropouts and I am left with some headroom so I can add even more.
- KVRAF
- 37409 posts since 14 Sep, 2002 from In teh net
Yes this is the main thing I still run into as that's almost entirely how I use a DAW - as a live plugin recording host not a mixing host.jtrake wrote: If you use Studio One for mixing where you don't have to think about latency and can have the buffer settings high like 1024, it works as good as any other DAW.
The performance issues surface when you for example compose with VSTi instruments by playing them on midi keyboard or record guitars using vst smp simulations. In these situations a buffer 128 samples is about as high as one want to go and in these situations S1 performs much worse than the other major DAWs like Logi,Cubase, DP, Protools.
Much as I'm increasingly drawn to S1 for its completeness - it is literally the only DAW I have that can load all my plugins and all their presets; with others like Logic, Bitwig and Tracktion there are always either plugins/formats I can't load or presets are not supported for a certain format. So I like to have all my tools in one place, but I would also appreciate better performance.
Plus if only it had T7's retrospective record.
-
- KVRAF
- 1991 posts since 12 Mar, 2004
Omg, cant you haters stop hating, it is all the users fault, non of these issues exist, never ever, not in a million years.
Add a few more lines of hyperbolic passive aggressive nonsense.
Am i an acceptable S1 user now ?
Obviously Presonus either dont care about these isdues or they lack the knowledge needed to fix them, this is not a recent issue and has been going on a while !
Add a few more lines of hyperbolic passive aggressive nonsense.
Am i an acceptable S1 user now ?
Obviously Presonus either dont care about these isdues or they lack the knowledge needed to fix them, this is not a recent issue and has been going on a while !
Duh
- KVRAF
- 2110 posts since 5 Oct, 2015 from Swedish / Living in Hong Kong
They want the response and attention. Just don't give it to thembungle wrote:Omg, cant you haters stop hating, it is all the users fault, non of these issues exist, never ever, not in a million years.
Add a few more lines of hyperbolic passive aggressive nonsense.
Am i an acceptable S1 user now ?
Obviously Presonus either dont care about these isdues or they lack the knowledge needed to fix them, this is not a recent issue and has been going on a while !
Win 10 -64bit, CPU i7-7700K, 32Gb, Focusrite 2i2, FL-studio 20, Studio One 4, Reason 10