Have you seen this Steinberg announcement?

[chk071]

http://www.steinberg.net/en/newsandeven ... -3852.html

In the past months, reports by windows users have been accumulating (OS X customers are not affected), who — working with projects that contain many VST plug-ins — reach a point, at which no further plug-ins can be loaded. After selection of the required plug-in, the insert slot simply remains empty.

During our investigation concerning these events, indications have arisen that a technical limitation of the operating system could be the cause of that problem. In the next step we will therefore lead talks with Microsoft and exchange ideas with third-party VST plug-in manufacturers, to push for the solution of the problem.

Interesting. I have not run into such a problem yet. And i also wonder what they mean, Windows 10? Only Cubase affected, or a general thing? Are devs aware of this? Leaves me pretty puzzled, that sort of info.

[planetearth]

Leaves me pretty puzzled, that sort of info.

Leaves me puzzled too, are there actually girls in the forum?

Yeah.

http://www.kvraudio.com/forum/viewtopic ... 4&t=463521

There are women here, though they're not as vocal about some of these issues as the rest of us are. (They're probably too busy making music than to worry about such arcane issues as filter slopes and plug-in limits. )

The Cubase/Win 10 issue seems to be related to those two: Cubase and Win 10. Since Cubase didn't specify what the "limit" number was, we won't know if we can reproduce that in other DAWs to confirm that it's a Windows issue (regardless of the version).

Maybe some of the women here who use Cubase could join in.

Steve

[chk071]

Well, could well be that someone actually ran into such an issue... if Steinberg noticed it as an issue by reports of some of their users. The linked article isn't at all specific though, whether it is a Windows 10 related issue, or a Cubase related issue. Sounds to me as if it was a general issue. I could be wrong.

[planetearth]

Well, could well be that someone actually ran into such an issue... if Steinberg noticed it as an issue by reports of some of their users. The linked article isn't at all specific though, whether it is a Windows 10 related issue, or a Cubase related issue. Sounds to me as if it was a general issue. I could be wrong.

I'd be surprised if it's a Win10 issue. Win10 isn't perfect--but it's also not entirely re-written from the ground up after Win7 or Win8, so if it's happening in Win10, it should have happened before, too. I still think it's a Cubase issue.

What's the most plug-ins anyone here has used in a project? And what's your DAW and OS?

Maybe we can gather some anecdotal data to deliver to Steinberg.

Steve

[EnGee]

Steinberg just being a di*k! Blaming Windows 10 for ages now while their plugins are the only ones not compatible with Win 10!! Shame on you Steinberg I'm happy I left their shit out of my PC.