KVR Audio

jancivil · Post by **jancivil** » Sun Sep 03, 2017 10:21 pm

chk071 wrote:
jancivil wrote:
fmr wrote: workarounds.
installations require me to go into Sys Prefs and force it to install it, then 'Are you sure?' - f**k off.
Hehe. I faced that a few times when installing some plugins from more (Waldorf), or less known developers.

Such as Native Instruments

chk071 · Post by **chk071** » Sun Sep 03, 2017 10:43 pm

Didn't notice that installing from Native Access.

jancivil · Post by **jancivil** » Sun Sep 03, 2017 10:53 pm

chk071 wrote:
Didn't notice that installing from Native Access.

Yeah, I install things which ain't in there. NA is probably why they said fvck this signing waste of time. All my BFD stuff so far been signed, OTOH.

shidostrife · Post by **shidostrife** » Mon Sep 04, 2017 12:43 am

Djsegwon wrote:still a very troublesome issue! got in touch with steinberg and they blamed izotope and izotope has yet to respond!!!!!!!!!!!

https://m.facebook.com/groups/122940794 ... up_comment

I read in Steinberg's forum that those blacklisted izotope dlls are not actually plugins. Check your non-blacklisted list. All your izotope plugins are there.

skank · Post by **skank** » Mon Nov 06, 2017 12:15 pm

Anyone know of any workarounds at all for the Cubase blacklisting? To force it to accept all plugins?

Freaqpeak · Post by **Freaqpeak** » Mon Nov 06, 2017 12:41 pm

Jakob / Cableguys wrote:
arne wrote:Just to let you know, Steinberg did release the vst scanner to all developers on their developer support forum back in early august.
So as a developer I am asked to check all forums of all DAWs regularly to look for any announcements that might have an impact of plugins that have been released years ago?

First of all, you can enable the plugins that has been disabled by Sentinel. No problem. Some of them are actually crashing Cubase, so it's better that they are blacklisted than loaded later on.

So.. with all due respect. It is your job as a commercial developer to keep your customers happy. If your plugin doesn't work in one of the most used DAWs in the world, who's problem is that really? I would be pretty pissed off if I bought anything and the developer won't fix issues, esp if they just haven't been using best practices while developing the plugin. If everybody followed the VST specs it should not be a problem, right?

The vast majority of plugins are not caught with Sentinel, since the developers are following VST dev best practices...

I do the exact same thing in my line of work, I can complain all I want.. But in the end I have to anything in my power to keep users happy.

Jakob / Cableguys · Post by **Jakob / Cableguys** » Mon Nov 06, 2017 1:40 pm

cnt wrote:The vast majority of plugins are not caught with Sentinel, since the developers are following VST dev best practices...

I do the exact same thing in my line of work, I can complain all I want.. But in the end I have to anything in my power to keep users happy.

In our case, Cubase disabled plugins on old OS X version if the plugins used a certain OS X library. Nothing that's conflicting with VST spec, and nothing that you'd expect as a developer.

cnt wrote:If your plugin doesn't work in one of the most used DAWs in the world, who's problem is that really?

Well, the plugins did work without issues for years. But anyway, it still would have been better to inform the plugin developers beforehand. Anyway, problem has gone now, all set.

felis · Post by **felis** » Wed Apr 04, 2018 2:07 am

I'm having a similar, but I think more serious problem than blacklisting.

I recently downloaded a bunch of fx plugins.
They're in the correct folders, and the plugin manager sees them and shows their paths, and none of them are blacklisted.

But when I go to the left side to put them in as 'insert fx', none of them are listed.

Anyone else run into this?

jclosed · Post by **jclosed** » Wed Apr 04, 2018 10:07 am

Maybe you changed something in the VST setup window?

You can make personal listings, and if you created one by mistake and left it empty, you would not see any plug-in listed when you start working in Cubase.

jancivil · Post by **jancivil** » Wed Apr 04, 2018 7:14 pm

felis wrote:I'm having a similar, but I think more serious problem than blacklisting.

I recently downloaded a bunch of fx plugins.
They're in the correct folders, and the plugin manager sees them and shows their paths, and none of them are blacklisted.

But when I go to the left side to put them in as 'insert fx', none of them are listed.

Anyone else run into this?

You mean the Inspector on the left side? Are you perhaps looking to instantiate Audio FX as though they're MIDI FX or like that?

felis · Post by **felis** » Wed Apr 04, 2018 10:59 pm

I got it straightened out with a little help. I had to delete and reinstall Cubase and everything shows up as it should now.

My elicenser was 'deprecated' by Steinberg.
I never switched computers, but did go from Win 8 to Win 10 on this one.
Still not exactly sure what caused the snag, but it can be worked out after a hassle.

Cubase 9's Plug-in Manager going wrong