Though I always get into trouble for this, nothing I ever tried or ever did ever worked with studio one on any system at any time WHEN I had problems. It was mostly NI products that I had the issues with. (which everyone conveniently forgets when they start trolling over it)nostradamoose wrote:There's been a lot of changes since Windows 7 architecture was first released nearly 8 years ago. The way the new generation of hardware, CPU, memory, BIOS, software and drivers all communicate and allocate system threads, settings and features has been vastly improved.incubus wrote:FL and win7 didn't get along well for me.
This is the same issues Studio One users are having, which requires BIOS settings to be enabled and disabled manually (Turbo, etc). Which probably has something to do with 3rd party plug-ins being coded 8 years or more ago and not performing as well on modern DAW source code design. Most companies have updated and adjusted for this already, but there's probably a lot still having issues. It took Softube a long time to get all their plug-ins to work well with all DAWS and Windows 10.
Anyways, there, I've set up the troll-bait. But I'm just happy that FL studio goes into nice-guy mode now with win 10 and power settings.