FLS checker shows 103 free slots in Cubase 10 on my machine while 9.5 gives me 99.
As a mini improvement we can still remove stuff we don’t need from the components folder. Euconadapter, OMFFilter (welcome AAF!), goproremoteski - whatever stuff you might not make use of anyway.
The Devs dont care. Except when customers lie on them to fix this. I contacted UA support and the response was - ‘your only the 3rd user to report this ever and because the development effort is not trivial they didnt believe it would be looked at any time soon’ (paraphrasing). Meanwhile they keep churning out plugin after plugin that are statically linked.
It will take all Cubase users to take the time to lodge support requests with each plugin vendor. Even then I’m not hopeful!
I’m getting 7-10 more FLS slots in Cubase 10 compared with Cubase 9.5. Then by taking out a bunch of the Components that I don’t use, I got 12 more slots. So that’s something. And if I need to, I’ll jbridge some stuff.
Still would be nice to never have to worry about it.
I hate spamming threads (there are a lot of threads on this topic) , but I want to make sure everyone who has run across the FLS limit sees that we’ve put a fix in the next release of Windows 10
If all goes well, the release will be the 19H1 release. We haven’t published a date for that, but the name gives you a clue that it should be in the first half of 2019.
I’m pretty excited about this. It took a while to get this implemented, but I’m happy to see that Vista-era limitation effectively go away. Some folks think only a few people ran up against this, but the more I look, the more posts I find on various forums.
If this is the case, maybe Steinberg should collaborate more with operating systems(Apple/MS), sounds kind of funked up, if you heared it thru the unofficial forum. Glad that at least you were honest.
We have been in touch with MS and Pete specifically all the time about the MMCSS issue and our developers spoke to MS about the FLS limitation in the past too.
Pete also informed our Audio Engine about the FLS change devs a couple days ago. I didn’t see this coming simply because MS didn’t communicate it directly to us before announcing it publicly.
This only shows that MS was very fast and transparent in informing the user base and 3rd parties alike about this specific change, not that there is no communication.
When it comes to insider builds, we tend to move quickly, especially right after the holidays. It made sense to get this information out to as many impacted folks as possible.
I had to manually fiddle around with the latest Windows update (1809) to get it to work, the default always seemed to give me the unsmiley face and rolled back the changes. I eventually got it to work by doing a manual download. I’m hoping that when this change gets rolled out by MS, it just works. It’s at least a 12 hour time suck to figure out how to fix MS update bugs. Getting out of date means that I’ll have less than 50 FLS slots for my projects. I’m really looking forward to this, I hope the update works.