Neither ...nor I think...it was just not noticed in this regard...learnkeys wrote: The scary part is, it took so long to discover that the bug even existed and then ultimately fix. I'm not sure if it's a sign of poor development, testing or priorities. Makes me wonder what other lurking bugs still go unnoticed or ignored for decades.
Sure, there were often claims, that FL Studio uses too much CPU, but as long as you don´t isolate the problem it´s hard to find the real cause
I am the one who was complaining at looptalk after noting a ridiculous behaviour and doing some test on other DAWs... and by accident I could isolate the problem to the mixer routing...
This brought reflex to have some deeper look and found this bug...
If somebody had noticed this before, it would have been solved long time ago...
