Given the amount of professional studios running Windows 7, smooth as silk, on similarly well-maintained systems... I kind of doubt that point. Even today. (That is, even if we were dealing with something that occurred today. Windows 10 wasn't even out when these issues first started to bother me in earnest.)nostradamoose wrote:"Windows 7", this could be a big part of your issue, since this is the most reported version from Windows users. When you start falling behind by a couple of generations of technological advancements in operating systems and hardware cohesiveness, you have to be prepared to troubleshoot your decision.
This is exactly what it has to do with, yes. In Studio One, there was a need to manage the project much sooner. Respectfully, it sounds as if you think there is something wrong (as in, borderline user error) in working with projects that, by their very nature, tax the system with large amounts of resource intensive plugins, without defaulting to bouncing and similar methods as a remedy. Or at least I get the impression you're repeatedly setting a tone of "there must be something wrong in the way you work."nostradamoose wrote:This also could have to do with your management of real time processing. Such as cpu hungry plug-ins and how many you're using. Which is usually solved by bouncing and rendering tracks, limiting the number of reverbs and other heavy processing plug-ins and management of the input and output audio buffer.
Almost like following a tech support flowchart even though it has (hopefully) been established I sort of know how to maintain an audio system
and rule out the obvious stuff.Quoting myself, though:
In the end, it's just my word against your speculation of there being something wrong in the system or my approach. Kind of pointless, hmm? And in a weird way, the tone sounding like official company support trying to bury a criticism.Guenon wrote:Also, sensing a drawn-out debate hidden in all this, hah.
It all comes down to: I was able to load large soundtrack templates of Kontakts and Zebras and Divas etc. into something else and just get on with writing a cue, with no dropouts whatsoever, as expected on my workstation. I still can. Studio One completely bottlenecked itself to oblivion on an identical loadout, which didn't even include any Studio One Multis (not to be confused with Kontakt Multis). It did when I last tried it, and I'm guessing it still would. The other DAW included sophisticated anticipative processing and extensive settings for optimizing its performance, Studio One didn't, and maxed out.
I've been messing with music tech since the 90s, so I guess you just have to take my word for it (that I did in fact troubleshoot it appropriately and meticulously and know what I'm doing
). If in doubt, just make sure it works for you. If it works, you're in for a treat, it's a gem of a DAW in many respects. That's it.
. On a well-maintained and carefully built system that runs absolutely everything else flawlessly and according to expectations, if there's a product with consistently underwhelming performance -- and it turns out, this is because it's so finicky it doesn't work on a system on which everything else does, and instead requires an OS still in pre-release at that time, before even major interface manufacturers have officially announced their products are compatible (e.g. RME in Aug 2015, the month after the actual Win 10 manufacturing release) -- I would consider that questionable design strategy.