Cubase Plug-in Sentinel: Blacklisted plug-ins

Post general topics related to Cubase Pro 9, Cubase Artist 9 and Cubase Elements 9 here.
Locked
augusteighty
New Member
Posts: 46
Joined: Tue Nov 11, 2014 8:43 am
Contact:

Re: Cubase Plug-in Sentinel: Blacklisted plug-ins

Post by augusteighty » Tue Aug 29, 2017 10:39 pm

Anyone know what's up with UAD? Just updated to 9.3 and all UAD plugins were blacklisted (including all 64 bit which are the only ones I use).

Reverted back to UAD 9.1, which was working 20 minutes ago (and for the last 6 months), and now that's blacklisted. Deleted the blacklist xml file on the drive, uninstalled all UAD, reinstalled 9.1, booted up Cubase and it rebuilt the blacklist database with UAD on it again. Tried to reactivate, no go.

Seriously - this should be a one button switch to turn this nonsense off.

Anyone have a work around? Going to try an even earlier version of UAD. This is absolutely ridiculous.

EDIT: Now working with UAD v9.1. Have no idea what worked. Uninstalled, reinstalled 9.3 without drivers. Nope. Uninstalled, installed 902 Thunderbolt (using PCIe lol). Plugins worked, no drivers. And UAD doesn't just give driver files...dumb dumbs. Uggh. Uninstalled, reinstalled 902 with drivers. No work. Deleted all plugin databases / drivers. Reinstalled 9.3 just in case - no work. Uninstalled everything, installed 9.1 without drivers. Installed 9.02 over that. Uninstalled drivers. Installed v9.1 again. Voila! It works! Rofl.

So - if you have this problem - best bet is to just torch your computer with gasoline. Throw it out the window. Travel back in time. Pick a new career, retire young.

TornadoTed
New Member
Posts: 13
Joined: Sat Sep 05, 2015 6:14 am
Contact:

Re: Cubase Plug-in Sentinel: Blacklisted plug-ins

Post by TornadoTed » Fri Sep 01, 2017 10:56 am

Reaktor 6.2 is blacklisted and when I try to reactivate it crashes Cubase. Reaktor 6.1 was fine.
Cubase 9.0.30, OSX 10.10.5, Mac Pro 2010 12 core 2.66, MOTU 8A

User avatar
djw
Senior Member
Posts: 1661
Joined: Sun Mar 15, 2015 2:49 am
Contact:

Re: Cubase Plug-in Sentinel: Blacklisted plug-ins

Post by djw » Fri Sep 01, 2017 11:29 am

TornadoTed wrote:
Fri Sep 01, 2017 10:56 am
Reaktor 6.2 is blacklisted and when I try to reactivate it crashes Cubase. Reaktor 6.1 was fine.
This seems to be a Mac only issue, running Reaktor's latest update here.
🥕

beerbong
Member
Posts: 754
Joined: Thu Apr 07, 2011 6:06 pm
Contact:

Re: Cubase Plug-in Sentinel: Blacklisted plug-ins

Post by beerbong » Fri Oct 06, 2017 9:51 pm

Crashed my Cubase session everytime
Redskull by aura plug (latest version I could find).
Wasn't blacklisted but it should be, I think
BB - Intel Quad/RME/Nvidia Video, RME Raydat, Win10 Home
Cubase 8.5 64 bit / Cubase 9.5 / Wavelab Elements

ultradust
Member
Posts: 205
Joined: Tue Jan 08, 2013 12:37 am
Contact:

Re: Cubase Plug-in Sentinel: Blacklisted plug-ins

Post by ultradust » Fri Nov 17, 2017 4:31 am

Cubase 9.5.0 consistently places the VST2 versions of Plugin Alliance's Maag EQ2 ( https://www.plugin-alliance.com/en/prod ... g_eq2.html ) and Maag EQ4 ( https://www.plugin-alliance.com/en/prod ... g_eq4.html ) on the blacklist. If I take them off the blacklist, Cubase places them back on the blacklist.

I've contacted Plugin Alliance and they have no idea why the plugins would be blacklisted. None of my other Plugin Alliance plugins get blacklisted, just the Maag EQ2 and EQ4.

Rudie Vissenberg
Junior Member
Posts: 61
Joined: Fri Jan 28, 2011 3:16 pm
Location: Houten
Contact:

Re: Cubase Plug-in Sentinel: Blacklisted plug-ins

Post by Rudie Vissenberg » Fri Nov 17, 2017 6:50 pm

Cubase now even blacklists their own plug ins like Halion Sonic 6 and Halion Symphonic Orchestra 64bit, on my PC. When I use my laptop it is even worse and blacklists a lot more 64bit Steinberg plugins. We should be able to switch off the Sentinel, it is at our own risk and I know I only use 64bit plug ins. Cubase should not become like Apple.
Win10 64bit, Intel i5-4460 at 3.2 GHz, 12Gig RAM, AMD Radeon R7 200, Cubase 9.5 and older, UR12, MOTU micro lite, Casio PX-110 piano

skank
Junior Member
Posts: 76
Joined: Thu Nov 10, 2011 11:54 am
Contact:

Re: Cubase Plug-in Sentinel: Blacklisted plug-ins

Post by skank » Fri Nov 17, 2017 7:09 pm

Rudie Vissenberg wrote:
Fri Nov 17, 2017 6:50 pm
Cubase now even blacklists their own plug ins like Halion Sonic 6 and Halion Symphonic Orchestra 64bit, on my PC. When I use my laptop it is even worse and blacklists a lot more 64bit Steinberg plugins. We should be able to switch off the Sentinel, it is at our own risk and I know I only use 64bit plug ins. Cubase should not become like Apple.
In a way I simply couldn't agree with you more.

Haven't had a single proper session with 9.x since I bought it.
This is not what you think it is./

metrosuperstar
Junior Member
Posts: 169
Joined: Tue Mar 08, 2011 4:16 am
Contact:

Re: Cubase Plug-in Sentinel: Blacklisted plug-ins

Post by metrosuperstar » Sat Nov 18, 2017 3:13 pm

Hi - in my case, the only file being blacklisted is the izotope file "iZTonalBalanceControl.dll". Can I just click Reactivate? Is it safe to do so? I'm not sure why it is being blacklisted as it is a 64-bit vst3 version...
High-Performance and Ultra Quiet PC Which I Built Myself.... Fractal Design Define R3 | Seasonic X-650 Gold | Noctua NH-D14 Cooler | 32GB Ripjaws X PC-12800 | Intel Ivy Bridge i7-3770K OC'd to 4.5 GHz | Asus P8Z77-V Deluxe | Samsung EVO 250GB (OS + Programs) | WD Caviar Black 4TB | WD Caviar Black 2TB | Focusrite Saffire Pro 24 DSP| Cubase Pro 8.5.15

vinark
Member
Posts: 444
Joined: Wed Dec 15, 2010 5:24 pm

Re: Cubase Plug-in Sentinel: Blacklisted plug-ins

Post by vinark » Sat Nov 18, 2017 5:06 pm

This is not the plugin but a related dll that izotope puts in the vst plugin folder. The plugin will still be listed and work and is called something like IzotopeTonalBalanceControl

jimmycooper
New Member
Posts: 3
Joined: Fri Aug 12, 2016 10:45 pm
Contact:

Re: Cubase Plug-in Sentinel: Blacklisted plug-ins

Post by jimmycooper » Thu Nov 23, 2017 6:20 am

blacklist plugin.PNG
(42.57 KiB) Not downloaded yet
Ugh.

User avatar
Denis van der Velde
Member
Posts: 245
Joined: Fri Jun 23, 2017 10:41 am
Location: Netherlands
Contact:

Re: Cubase Plug-in Sentinel: Blacklisted plug-ins

Post by Denis van der Velde » Sat Dec 16, 2017 3:43 pm

Does someone know about Roland Soundcancas VA not running under C9 or C95 or C951?

It works as a 32bit plugin under my cute C6 tough. I think the 64bit version crashed and blacklisted. I allready took it out of the balcklist restart means it is blacklisted again. So it sould be Roland Soundcanves VA problems ?

Thx Beforhand.
I7 8core 16tread 32gb Aopen Board, SSD Samsung. C95,W95,Halion6,Groove Agent,etc.
Running on 8ms Latency with a Soundblaster XFI Pro.

Denis van der Velde
http://www.curioza.com
AAMS Auto Audio Mastering System for Windows

Romantique Tp
External Moderator
Posts: 3011
Joined: Fri Aug 07, 2015 3:25 pm
Contact:

Re: Cubase Plug-in Sentinel: Blacklisted plug-ins

Post by Romantique Tp » Sat Dec 16, 2017 3:51 pm

It works. Make sure it's updated.
Every time someone says "it must be easy to add/fix", a programmer dies.

Cubase Pro and Wavelab Pro (latest), Windows 7 Ultimate 64-bit, MSI Z87-G45 GAMING, i5 4690k, GeForce GTX 760, almost every Steinberg plugin and expansion, Trilian, Komplete 10, etc etc etc etc

User avatar
drhardlove
New Member
Posts: 28
Joined: Fri Nov 16, 2012 12:07 am
Location: Norway
Contact:

Re: Cubase Plug-in Sentinel: Blacklisted plug-ins

Post by drhardlove » Thu Jan 11, 2018 4:37 pm

djw wrote:
Fri Dec 09, 2016 12:41 pm
I'm getting the feeling that the same users that would blame Cubase for being unstable are now complaining that their unstable plugins get blacklisted.
Frankly, my Cubase 9 is running more stable with JBridge and lots of 32 bit plugs fully functioning, than Cubase did for quite some time.

That is a big scratch for Steinberg. Some small developer making Steinberg platforms more useful for a lot of Steinberg users, than Steinberg themselves, and for a fraction of the price. 20 euros. It is near on shameful at its worst, actually.

Steinberg is supposed to be able to take heat from users. The users pay for their service, and always deserve Steinberg doing their best.
The do also thank them for what they do good. That is why we still use cubase. For me, since 1991 on ATARI.

You yourself should be thankful for those moaning, because they actually made sure that Steinberg worked harder on issues, that might have been troublesome for you as well.

skank
Junior Member
Posts: 76
Joined: Thu Nov 10, 2011 11:54 am
Contact:

Re: Cubase Plug-in Sentinel: Blacklisted plug-ins

Post by skank » Thu Jan 11, 2018 4:43 pm

drhardlove wrote:
Thu Jan 11, 2018 4:37 pm
djw wrote:
Fri Dec 09, 2016 12:41 pm
I'm getting the feeling that the same users that would blame Cubase for being unstable are now complaining that their unstable plugins get blacklisted.
Frankly, my Cubase 9 is running more stable with JBridge and lots of 32 bit plugs fully functioning, than Cubase did for quite some time.

That is a big scratch for Steinberg. Some small developer making Steinberg platforms more useful for a lot of Steinberg users, than Steinberg themselves, and for a fraction of the price. 20 euros. It is near on shameful at its worst, actually.

Steinberg is supposed to be able to take heat from users. The users pay for their service, and always deserve Steinberg doing their best.
The do also thank them for what they do good. That is why we still use cubase. For me, since 1991 on ATARI.

You yourself should be thankful for those moaning, because they actually made sure that Steinberg worked harder on issues, that might have been troublesome for you as well.
I had to abandon C9, couldn't yet get it to see all my VTSs, and hated the idea of being forced to leave some (VSTs) behind.

Also had a shockingly slow load time at each start (seems to reinitialise at every start)
This is not what you think it is./

User avatar
drhardlove
New Member
Posts: 28
Joined: Fri Nov 16, 2012 12:07 am
Location: Norway
Contact:

Re: Cubase Plug-in Sentinel: Blacklisted plug-ins

Post by drhardlove » Thu Jan 11, 2018 5:18 pm

hopselectroniks wrote:
Wed Jan 25, 2017 10:50 am
turned my liquid mix into an expensive door stop ..

and all my TC dsp plugs
Me too.
But JBridge brought them back.

User avatar
drhardlove
New Member
Posts: 28
Joined: Fri Nov 16, 2012 12:07 am
Location: Norway
Contact:

Re: Cubase Plug-in Sentinel: Blacklisted plug-ins

Post by drhardlove » Thu Jan 11, 2018 5:25 pm

Derek Cook wrote:
Sun Apr 16, 2017 7:10 pm
Raphie wrote:
Derek Cook wrote:Well, I am using 32 bit bridged plugins in Cubase 9 courtesy of JBridge ...... Including Steinberg Virtual Bassist and Virtual Guitarist, so whilst Cubase 9 as no official support for 32 bit any more, the bloody minded of us who still need to run 32 bit plug-ins where there are no 64 bit equivalents, can do.
Sure, but your on your own there, no support from Steinberg on Jbridge, so anything 32bit you need to be with J.
Anything 64bit is an installation path issue if not blocked by sentinel. There is nothing more to it.
Fair enough, but I am glad that there is 3rd party support. I still need to run 32 bit plugins include Steinberg Virtual Bassist and Virtual Guitarist, now abandoned by Steinberg. I paid Steinberg good money for these. Why should I not wish to run them for as long as I can?

I only have half a dozen or so 32 bit plugins in this category, but they are all regularly used.

And they are running fine under JBridge - in fact they are running better under JBridge than under Steinberg's bridge that was removed in Cubase 9, so I am "not unhappy" that Steinberg removed it. ;)
My experience too.

User avatar
drhardlove
New Member
Posts: 28
Joined: Fri Nov 16, 2012 12:07 am
Location: Norway
Contact:

Re: Cubase Plug-in Sentinel: Blacklisted plug-ins

Post by drhardlove » Thu Jan 11, 2018 5:29 pm

skank wrote:
Thu Jan 11, 2018 4:43 pm
drhardlove wrote:
Thu Jan 11, 2018 4:37 pm
djw wrote:
Fri Dec 09, 2016 12:41 pm
I'm getting the feeling that the same users that would blame Cubase for being unstable are now complaining that their unstable plugins get blacklisted.
Frankly, my Cubase 9 is running more stable with JBridge and lots of 32 bit plugs fully functioning, than Cubase did for quite some time.

That is a big scratch for Steinberg. Some small developer making Steinberg platforms more useful for a lot of Steinberg users, than Steinberg themselves, and for a fraction of the price. 20 euros. It is near on shameful at its worst, actually.

Steinberg is supposed to be able to take heat from users. The users pay for their service, and always deserve Steinberg doing their best.
The do also thank them for what they do good. That is why we still use cubase. For me, since 1991 on ATARI.

You yourself should be thankful for those moaning, because they actually made sure that Steinberg worked harder on issues, that might have been troublesome for you as well.
I had to abandon C9, couldn't yet get it to see all my VTSs, and hated the idea of being forced to leave some (VSTs) behind.

Also had a shockingly slow load time at each start (seems to reinitialise at every start)
If you want to keep up with 9 and onwards, you should check out JBridge. Works like a charm form many.

skank
Junior Member
Posts: 76
Joined: Thu Nov 10, 2011 11:54 am
Contact:

Re: Cubase Plug-in Sentinel: Blacklisted plug-ins

Post by skank » Thu Jan 11, 2018 5:33 pm

drhardlove wrote:
Thu Jan 11, 2018 5:29 pm
skank wrote:
Thu Jan 11, 2018 4:43 pm
drhardlove wrote:
Thu Jan 11, 2018 4:37 pm
Frankly, my Cubase 9 is running more stable with JBridge and lots of 32 bit plugs fully functioning, than Cubase did for quite some time.
The do also thank them for what they do good. That is why we still use cubase. For me, since 1991 on ATARI.
I had to abandon C9, couldn't yet get it to see all my VTSs, and hated the idea of being forced to leave some (VSTs) behind.

Also had a shockingly slow load time at each start (seems to reinitialise at every start)
If you want to keep up with 9 and onwards, you should check out JBridge. Works like a charm form many.
Thanks!

I've had it for years. Brilliant. But it still can't bring back the older VSTs, or make my Cubase boot times acceptable and stop Cubase from blacklisting VSTs and then forcing me to unblacklist each VST *individually*. Try doing that with a 100+ VSTs :(
This is not what you think it is./

User avatar
drhardlove
New Member
Posts: 28
Joined: Fri Nov 16, 2012 12:07 am
Location: Norway
Contact:

Re: Cubase Plug-in Sentinel: Blacklisted plug-ins

Post by drhardlove » Thu Jan 11, 2018 5:45 pm

skank wrote:
Thu Jan 11, 2018 5:33 pm
drhardlove wrote:
Thu Jan 11, 2018 5:29 pm
skank wrote:
Thu Jan 11, 2018 4:43 pm


I had to abandon C9, couldn't yet get it to see all my VTSs, and hated the idea of being forced to leave some (VSTs) behind.

Also had a shockingly slow load time at each start (seems to reinitialise at every start)
If you want to keep up with 9 and onwards, you should check out JBridge. Works like a charm form many.
Thanks!

I've had it for years. Brilliant. But it still can't bring back the older VSTs, or make my Cubase boot times acceptable and stop Cubase from blacklisting VSTs and then forcing me to unblacklist each VST *individually*. Try doing that with a 100+ VSTs :(
The older plugs I don't have anymore. For me it was Liquid an Powercore, and a few minor developers, that was important. But I support anybody, claiming that Steinberg should have all possible plugs, still available. The resource issue, should not be the customers problem to solve.

Regarding blacklisting and JBridge, I actually removed all VSTplugins, when they were running so fine in JBridge. I don't think it makes sense to have two instances of dll's in Steinberg VST folder, and JBridge folder. When I removed my VST folder, all my blacklists where gone as well. So I believe you must have two instances of those blacklisted dll's, one in Jbridge, and one still in some Steinberg VST folder. I am now rebuilding my Steinberg VST folder with those plugs that don't work well with JBridge. So far only UAD2 plugs. I then delete those from the JBridge folder, and vice versa. Make sure to keep a backup folder of both, for redoing any bad move. ;-)
Last edited by drhardlove on Thu Jan 11, 2018 5:49 pm, edited 1 time in total.

skank
Junior Member
Posts: 76
Joined: Thu Nov 10, 2011 11:54 am
Contact:

Re: Cubase Plug-in Sentinel: Blacklisted plug-ins

Post by skank » Thu Jan 11, 2018 5:48 pm

:D
drhardlove wrote:
Thu Jan 11, 2018 5:45 pm
skank wrote:
Thu Jan 11, 2018 5:33 pm
drhardlove wrote:
Thu Jan 11, 2018 5:29 pm


If you want to keep up with 9 and onwards, you should check out JBridge. Works like a charm form many.
Thanks!

I've had it for years. Brilliant. But it still can't bring back the older VSTs, or make my Cubase boot times acceptable and stop Cubase from blacklisting VSTs and then forcing me to unblacklist each VST *individually*. Try doing that with a 100+ VSTs :(
The older plugs I don't have anymore. For me it was Liquid an Powercore, and a few minor developers, that was important. But I support anybody, claiming that Steinberg should have all possible plugs, still available. The resource issue, should not be the customers problem to solve.

Regarding blacklisting and JBridge, I actually removed all VSTplugins, when they were running so fine in JBridge. I don't think it makes sense to have two instances of dll's in Steinberg VST folder, and JBridge folder. When I removed my VST folder, all my blacklists where gone as well. I am now rebuilding my Steinberg VST folder with those plugs that don't work well with JBridge. So far only UAD2 plugs. I then delete those from the JBridge folder, and vice versa. Make sure to keep a backup folder of both, for redoing any bad move. ;-)
Thanks maybe I give it one more try 8-)
This is not what you think it is./

User avatar
drhardlove
New Member
Posts: 28
Joined: Fri Nov 16, 2012 12:07 am
Location: Norway
Contact:

Re: Cubase Plug-in Sentinel: Blacklisted plug-ins

Post by drhardlove » Mon Jan 15, 2018 1:51 am

I am here for discussing blacklists and related, and want to clear, and add more information about some issues I didn't have knowledge about in my last post(s). If some of the related topics should have a new thread, the moderators must decide upon. It seems to me that JBridge should be one.

Spamming, take overs, and off topics another. I might consider that myself, because I was recently accused of those things by a very rude person in here.

But for Now.
Ed Doll wrote:
Wed Dec 07, 2016 2:53 pm
In case you have issues with your plug-ins being blacklisted by Cubase 9, please have a look at this article on why this might have happened and what you can do - if you really have to.

https://helpcenter.steinberg.de/hc/en-u ... r-Cubase-9
Thank you. It might be sufficient for some, but as has been discussed later in the thread, some have issues with the blacklisted vst's coming back on the list. Wouldn't it be better to remove them completely from the VST folders, and add them via JBridge instead? Jbridge has quite a few setting options ready to diminish instability problems, globally, and in each single case as well. Naturally JBridge will be a better partner for those who needs to keep some tools, since Jbridge is on the case, whilst Steinberg has dropped it.
suntower wrote:
Wed Dec 07, 2016 10:19 pm
1. IMO, there needs to be a way to turn 'Sentinel' OFF--like ASIO Guard. At least until you guys have more real-world feedback. Disabling 32 bit support is too huge a leap with no prior warning.

2. Said it before, say it again: you guys need to COMMUNICATE. A big change like this should have been communicated to users MANY MONTHS ahead of time. I'm sure there would've been yelling, but so what? At least users like me would've had -time- to prepare!

My work is constantly re-using material from many years ago. So almost the biggest thing -I- need is backward compatibility--or at least a way to migrate older work to the newer versions without too much pain.

With no prior warning, I feel stuck... I like the new features of C9, but the unexpected cost of losing a TON of plugs is a real gut punch.
For me this is a topic too. But I don't necceceraly think Steinberg is not trying, they are I believe, really. How to be successful in communicating such an enourmous amount of information and topics, or making it easily searchable, is not a task that any company is guaranteed success with. But I really think Steinberg should put even more effort into making sure that all essential information is well displayed, warned about, and easily searchable. It is however natural for any company to keep their mind on displaying competitive information in a much more attractive manner. And many, including myself, don't read newsletters of importance these days, before they have to. ;-)

It would not be a bad move from Steinberg to inform those about to upgrade, about the challenges they might face, before they buy the new product, like in a PRO's and CON's section of the new product description. Or assemble all problems ocurring after release, in a chapter where solutions are presented. The way it is now, it can sometimes take a multitude of time to sniff out the problem, and the information solving the problem, is often found in scattered places around the web. Everyone running DAW's for 10 years or more, knows this.
ZeroZero wrote:
Wed Dec 07, 2016 10:22 pm
To be fair Suntower - they did communicate this, I knew a month or two before
You see. :-) It took me months to find out, after I bought it. :-) So some find it, and some don't. I think Steinberg must take part of the responsibility towards more people knowing. Then these frustrations that I became a spokesperson for here the other day, might be lessened.
jose7822 wrote:
Wed Dec 07, 2016 10:30 pm
Not only that, but you can always go back to a previous version of Cubase if you need to work on older projects. It's not like you have to get rid of all of them today. That said, there are plenty of 64 bit plugins available nowadays. I'm sure you can replace any 32 bit plugin with current 64 bit ones.
Nope, not really the topic for some. They have plugs and hardware that will never develop into 64 bit, but they are fully functioning, and will be rendered useless as the platforms develop. Some of these are brilliant tools, those producers really need.
jose7822 wrote:
Wed Dec 07, 2016 10:36 pm
Also, this:
viewtopic.php?f=250&t=107299
This however, was spot on, I missed out on that comment last time. And this one folks, must be the thread to discuss JBridge as a third party solution, for those with frustrations and needs in that direction.
JACKnight wrote:
Wed Dec 07, 2016 10:38 pm
I agree with the need for 32bit support.
I use some very cool old organ and percussion vst's that are obsolete, never be 64 bit, and I have tons of projects with them.
Imagine if your old 1176 hardware would no longer work because, new connectors.
Cheers
You see? If we all are forced to give up our favourites, and settle for something everyone else has, what will that do to originality and creativity. You all know the slogan. Creativity first. ;-) But wait, Steinberg has proven to be solid on their word, at least in this case. I will show you at the end of this post. Go there if you don't want to read all my quotes and comments.
djw wrote:
Wed Dec 07, 2016 11:46 pm
suntower wrote:How did you know this? How was it communicated?
This news article from June: https://www.steinberg.net/en/newsandeve ... -3778.html
The support of 32-bit technology in our applications will be discontinued.
This link it is not working anymore. I don't know since when.
geko wrote:
Thu Dec 08, 2016 12:31 am
well I have the same problem with my UAD-1 but I think i will open a new post for this so maybe i will get more direct answer, but its very disappointing
JBridge works great, and Steinberg has support for it. Check the link on JBridge as solution here viewtopic.php?f=250&t=107299 . Let me ask you also, did you make a JBridge support thread?
Down Jones wrote:
Thu Dec 08, 2016 11:18 am
JACKnight wrote:I agree with the need for 32bit support.
I use some very cool old organ and percussion vst's that are obsolute, never be 64 bit, and I have tons of projects with them.
Imagine if your old 1176 hardware would no longer work because, new connectors.

Cheers
Use Cubase 8.5 next to C9. There is no issue. Bitbridging always has been an achilles heel, other DAWs have kicked 32 bit a few versions ago.
Like others say here, JBridge works fine, to switch between platforms is not the best advise in my opinion. It takes a lot of extra time, and is unnecessary when JBridge works well. Even Steinberg recommends it, so we should use it. Then the issues it has will be developed even further.
sound4site wrote:
Fri Dec 09, 2016 9:57 am
Siegfried1974 wrote:Hello,
User of Cubase for a very long time, I rushed on the new version 9 yesterday... In the place, to wait for the first notices...
Thus the big novelty it is a module 'Sentinel' (anything that the name frightens) roughly that verifies all your plugins and without explanation that tosses 60 % of plug - in in a blacklist. Roughly, they become unusable... Thus your previous projects died ...
The AFTER-SALES SERVICE, after some messages, tells me that I need to contact the editors of the plugin while everything works under Cubase 8.5. "Cubase9 is more stable without third party plugins"
Do not lose 100€ in this update, stay under 8.5.
Thanks for the warning…. I was just about to upgrade to 9 after watching videos hyping it up.
Will remain on 8.5 for now.
Hopefully we can disable this scary sounding sentinel in the future
Hi Siegfried1974 and sound4site
Research JBridge. It works well, and you can be on the Cubase upgrade bus still. The scary Sentinel is doing a good job as well. Double happy. :D :D
djw wrote:
Fri Dec 09, 2016 12:41 pm
I'm getting the feeling that the same users that would blame Cubase for being unstable are now complaining that their unstable plugins get blacklisted.
Yeah. Great. Just splendidly on-topic this one, isn't it? What help do you bring with this attitude?

Yes people complained about Cubase being unstable, and it really was, and now Cubase did something about it. Good on both, those who complained, and the Cubase team for finding a good solution. Now people are complaining about loosing their tools. I don't get what is wrong with that, and Cubase has also foreseen that, maybe not with an optimal solution, but one must respect their choice, as long as they let JBridge take care of old users like myself. And Steinberg does say use JBridge if you need your 32 bit plugs. All well.

I will report you for this way of communicating to groups of people. I have already complained to moderator and Steinberg, about you accusing me of horrendous things here. I really wonder which of us is a spammer. Please be more polite in future communications, or stop harassing people for small stuff. Thank you.
Svenne wrote:
Fri Dec 09, 2016 1:07 pm
djw wrote:I'm getting the feeling that the same users that would blame Cubase for being unstable are now complaining that their unstable plugins get blacklisted.
No they are not, they are complaining that their stable plug-ins are being blacklisted.

It's impossible to see any pattern or ascertain why a plug-in is blacklisted. As a matter of fact, the same plug-in may be blacklisted on one system, but not on another. It's obvious that the blacklisting has nothing to do with whether a plug-in is stable or not. What the criteria are, is still a mystery.
Siegfried1974 wrote:The AFTER-SALES SERVICE.... "Cubase9 is more stable without third party plugins"
Could this be a first step in making VST a closed Steinberg only format, where no third-party developers are allowed?
I believe the Cubase team might find it challenging and exhauting to acommodate all instability issues, and in many ways, I understand their choise. However, they could probably do the same job as JBridge, but they endorse JBridge and move on, now that I know, I am fine with it.
EricM wrote:
Fri Dec 09, 2016 3:27 pm
"I'm really angry to have C9 and can't work with."
Which plugins are you missing? Are you on Windows or Mac? Have you tried reactivating the 64 Bit plugins on your blacklist?

Really? Are you a Steinberg employee for real. :-) Don't be angry, try to communicate your frustration. ;-)
jaslan wrote:
Sat Dec 10, 2016 1:14 pm
JClosed wrote:
nectario wrote:It makes no sense to remove VSTBridge. Just make it more reliable. I guess I will have to convert my 32 bit plugins using JBridge now...
You cannot make the VSTBridge more reliable if the plugins itself are not reliable. The only thing a VSTBridge would do is adding ancient 32 bit plugins that has not been updated in 5 to 10 years. I understand why Steinberg goes for the 64 bit path only. It forces the plugin makers to update their stuff, and improves the stability of Cubase. Let's be fair - Cubase is often accused of being unstable in this forum, while at the end it turned out to be a badly coded plugin that was causing this.

If you really want to use unstable plugins you can always use JBridge. It's not that there are no alternatives at all. Keep in mind though, that using 32 bit plugins using a bridge (or plugin host) can make Cubase unstable again.
This is a very important point! Worth repeating.
Yes and no. The stability issue is for real, so is the improvement in Cubase, but JBridge is willing and able to fuse more effort into making it work. Many reports of great support as well, for me an obviously quite a few others, JBridge is running very stable as well. :D :D
beerbong wrote:
Mon Dec 19, 2016 12:17 am
It seems to me that a lot of folks here think that just because some VST's are 32 bit, or old, has anything to do with whether they have "bad programming" or 'unstable'.
cheers
This is part of the misconceptions you will find in this thread, but we are here to enlighten each other, be patient. ;-)
djw wrote:
Mon Feb 06, 2017 6:55 pm
Yeah, there's still some leeway to get things working, but there won't be an official (supported) solution from Steinberg.
How do you know that? Are you working for Steinberg?
bburman wrote:
Thu Apr 06, 2017 8:39 pm
I have Cubase 9 on my mac now, and still having problems with bridged VSTs.Even plug-ins as basic as Battery 4...I've downloaded the latest version, yet it still only appears as a bridged VST. Like other VSTs it appears in the JBridge folder under instruments, works fine for a while, and then all at once it crashes Cubase and the whole computer (Mac Pro). It seems there's a host app called auxhost2 that does the crashing, I'm not sure what that is or how to deal with it, can't find any info on it, it must be connected to JBridge somehow. In any case, the Sentinel isn't doing its job of isolating dubious VSTs to the blacklist, and I've received no response to Steinberg support in over a week, same with Native Instruments (who make Battery 4)...it seems they're just abandoning the users upgrades that they haven't thought through. And I know, "Firms have had long enough to upgrade to 64 bit, bla bla bla", but that doesn't explain why Sentinel doesn't sort out the problem VSTs to the blacklist.
Did you make it work? Have you moved to, or found a thread with a good JBridge support community? If so, please share.
Several Steinberg employees is recommending JBridge, and says it as it is. It works fine. I expect Steinberg to support officially it for the future.
hopselectroniks wrote:
Wed Jan 25, 2017 10:50 am
turned my liquid mix into an expensive door stop ..

and all my TC dsp plugs
I hope you know by now, that JBridge can give your door stops a new life, for 20 euros. :D

If anybody visiting this thread still wonder about Blacklist problems, and Steinbergs position on JBridge, or other third party solutions to the problem, check out the video below. At 29 minutes Greg Ondo is saying that they allow third party solutions to this problem.

Thank you Steinberg for being constructive and professional. I am happy I didn't leave you years ago. Keep being our best friend.
I am out of here for now. I'll be back, unless I get banned for being overly helpful and constructive.

Any suggestion to JBridge support threads or communities are welcome.

Welcome to the Club Cubase Google Hangouts, where Greg Ondo, Steinberg’s senior field marketing manager presents Cubase, the advanced music production system. https://www.youtube.com/watch?v=xiJeIObQSE8

User avatar
peakae
Senior Member
Posts: 2509
Joined: Sat Jan 05, 2013 8:15 pm
Location: Bedroom
Contact:

Re: Cubase Plug-in Sentinel: Blacklisted plug-ins

Post by peakae » Mon Jan 15, 2018 8:02 am

I think you are missing the point, the plugin sentinel checks plugins for some issues and if the plugin passes it gets added, if not it gets blacklisted. A plugin could be blacklisted on one system and not the other, a simple copy protection asking to re-evaluate would do that, a missing .NET component could also do it.
32bit plugins get blacklisted as they are now finally not supported anymore, some can be made to work using JBridge.
JBridge has been around for years, and it is hardly news to anyone that it can work on some plugins if you a willing to take the risk.
The plugin sentinel (cmd line version) was made awailable to plugin manufacturers before the release, so they now have a tool to test their creations before releasing them. That is a huge benefit to everybody, less buggy plugins also benefit all other daws.

Btw if you are annoyed by some users comments, put them on the ignore list (friend/foe) and your blood pressure will thank you.
Or just get a thicker skin :-) using a none native language to communicate without the visual cues of a face in front of you can easily lead to misinterpretation. I have been guilty of that in the past, but I’m the first one to say sorry if that is the case, also for this post.
Cubase Pro 9.5.30, Wavelab Elements 9, I7 3770K , win10x64, 16Gb Ram, RME Raydat, Steinberg MR816x, Motu 828mkII, Behringer ADA8200, Yamaha moXF6, Steinberg UR242, Yamaha THR 10, Cambridge Audio DacMagic Plus, CMC TP, CMC CH.

User avatar
SF_Green
New Member
Posts: 42
Joined: Wed Jul 17, 2013 1:47 pm
Location: San Francisco
Contact:

Re: Cubase Plug-in Sentinel: Blacklisted plug-ins

Post by SF_Green » Mon Jan 15, 2018 9:04 am

jose7822 wrote:
Wed Dec 07, 2016 10:36 pm
Also, this:

viewtopic.php?f=250&t=107299
+1 for jBridge
Cubase Pro 9.5.20, Wavelab Elements 9.5.20, SonarPt-2017.10, Live 10, Reason10, Finale 25, Komplete10Ult, Omnisphere2, BFD3, ARP Omni, many things with strings.
RME FireFace 800 (D 3.119, fw 2.77), Adam A7X, UAD-2Quad, Roland A-800 PRO, CC121, Alesis QS7.1, Arturia BeatStep Pro, Maschine MkII, POD HD500
AMD FX-8370, Gigabyte 990FXA-UD3, Win7x64 SP1, 16Gb CorsairDDR3-1600
GeForce GTX 950 (390.65), SSD 525Gb (OS), SATA 3 & 1.5Tb
GrSltz My Studio

User avatar
drhardlove
New Member
Posts: 28
Joined: Fri Nov 16, 2012 12:07 am
Location: Norway
Contact:

Re: Cubase Plug-in Sentinel: Blacklisted plug-ins

Post by drhardlove » Mon Jan 15, 2018 3:35 pm

peakae wrote:
Mon Jan 15, 2018 8:02 am
I think you are missing the point, the plugin sentinel checks plugins for some issues and if the plugin passes it gets added, if not it gets blacklisted. A plugin could be blacklisted on one system and not the other, a simple copy protection asking to re-evaluate would do that, a missing .NET component could also do it.
32bit plugins get blacklisted as they are now finally not supported anymore, some can be made to work using JBridge.
JBridge has been around for years, and it is hardly news to anyone that it can work on some plugins if you a willing to take the risk.
The plugin sentinel (cmd line version) was made awailable to plugin manufacturers before the release, so they now have a tool to test their creations before releasing them. That is a huge benefit to everybody, less buggy plugins also benefit all other daws.

Btw if you are annoyed by some users comments, put them on the ignore list (friend/foe) and your blood pressure will thank you.
Or just get a thicker skin :-) using a none native language to communicate without the visual cues of a face in front of you can easily lead to misinterpretation. I have been guilty of that in the past, but I’m the first one to say sorry if that is the case, also for this post.
Thanks for the info update peakae, and thank you for taking time to both read and respond. This is why I love forums like this, were people share knowledge and help each other, without any other inclination than to do exactly that.

The information on system specific blacklisting is interesting. I get that Cubase, third party plugs, and OS, all have specifics that will have to be checked. But will hardware make a difference as well? Will Sentinel check my chipsets t.ex. ?

I have previously had enormous amounts of trouble due to a chipset in a previous beast of a machine I was running. The DELL Precision 690. I spent years with an unstable machine, where UAD1, MOTU 828 and FW items would produce all kinds of mystic problems. Finally the machine was abandoned by UAD and they blamed it on the chipset. So I unwillingly came to learn a lot about the challenges developers can be up against.

The re-evaluating issue is unnecessary terror in my view. I like to keep my machine totally of the grid. I have noticed that some developers don't care about that. I feel like they present me with a suspicious probe anytime they like, and then make me a lot of extra work, especially because I am off grid. It is actually often the bigger and more successful companies doing this. Toontrack is close to manic in my experience. But will this stop them in initializing re-evaluating, if so Sentinel has anothe big + from me. :D

I also remember a lot of problems with some .NET framework updates, that took a long time to fix, back in the days of my 690.

I don't know if I misunderstand, or you misunderstand me. I have already landed on the conclusion, that Sentinel represents a big step forward for system stability, given that we understand how it works, and are able to compensate for the troubles it might bring to some of us.

I know that JBridge has been around for years. And solved different issues since its arrival. But I think there is quite a few misconceptions about it out here, and I am sure that there are people not knowing about it also. I was one, until I lost some of my beloved 32 bit plugs with CB9.
But I am lucky to have several great techs in my friend sircut, so they always help me get on track of what I need. Some here are not that lucky, and I take it as my community service plight, to try to reach out for them as well. I am, like many others here, first and foremost an artist. A singer songwriter, who got into production since the beginning. I know the pains and challenges of the tech environment.

One of the issues for many is the enourmous amounts of time and money they have to put down, and at the same time making less than most.
I understand those who really try to hold on to what they have, due to lack of funds, workflow, and artistic decisions. Because many of us using Cubase, have artistic aspirations, often more than pro tech aspirations I believe. And It may be a big blow every time the future is at the door.

Me for One, is running what some here will call an ancient machine. A DELL Precision 7400, built on the same architecture as the dreaded 690.
I payed about 5000 euros/dollars for the 690, and would not be up and running now if it wasn't for getting the 7400 for 500 used, when the chipset issue was official.

I think there are lots of people here, that can not even dream about buying a machine for that price, and it didn't even work well. :shock:

So my intention is to help those, as I was helped. I think Steinberg actually do tremendous work to do the same, although some think they don't care. Those people face the challenges, without finding the solution, often not knowing that both Steinberg and others are working to their benefit, and try to acommodate a as full spectrum it's users, as possible. I think Cubase rocks, in so many ways.

The problem in this thread, as well as others I suppose, is that it often seems like there is a for or against culture. There shouldn't be.
My intention with yesterdays lengthy post, was to show that it is still possible to hang on to ones babies, and at the same time, be part of the Cubase development carousel :-D

Many might know this, but it is kinda hard to see that in the thread as it was when I found it. Or at least I found it to be considered a not so optimal option by many professionals. My point is that it is really a well functioning optin, even endorsed by several Steinberg associates.

Steinberg made it possible, and I love to see such responsibility. I was very enthusiastic when JBridge solved my problems. And I want others to know. I have not experienced major problems with JBridge, and I don't think it is about taking chances, but you might obviously need some skills, basic understanding, and/or good support.

I think that if you don't have the skills, one can still make it work with the support at JBridge, and forums like this one.

I have at least one person here, who I made reconsider his recapitulation over the missing 32 bit support. Even my mentor, who is extremely well informed about a lot of the tech issues, was surprised to find that it solved my issues with TC Powercore and Liquid Mix, and he is absolutely going to check it out again. Even though he has JBridge installed in his system since years ago, but for other reasons. So I think that there are a minority out here who will appreciate discover or rediscovering JBridge.

The skin issue. Yes thanks for you advise. I don't mind people taking me on whatsoever, I am usually so well spoken that I don't need to be provoked. I also work on myself to be respectful and humble. But when people act on your back, whilst having no better attitude or contribution skills themselves, I am provoked. Abusing the report system when minor mistakes are present, seems to me like something that needs to be adressed. I think the report system should be used when people are impolite, very destructive, ranting, or abusive. Not when they try to be helpful and illuminate a topic. Minor mistakes by a user, especially a new one, should not be rewarded with reports and warnings. I must say that I have heard about such abuse of the report/warning system here on the Cubase forum before, from very skilled and serious producers in my sircuit. But it is my first time to encounter it. I was advised to seek to be added to the Nuendo forum, because there is alledgedly less of this stuff there, but the moderator who considered me, didn't like my username, which happens to be my artist name as well. I wonder what was on his mind. ;-)
I don't like to make people my foes, and I didn't yet. It is not a good way to solve issues, in my view. A foe might become a friend, it is all about communication and understanding. But thank you so much again. :D

User avatar
drhardlove
New Member
Posts: 28
Joined: Fri Nov 16, 2012 12:07 am
Location: Norway
Contact:

Re: Cubase Plug-in Sentinel: Blacklisted plug-ins

Post by drhardlove » Mon Jan 29, 2018 12:02 am

skank wrote:
Thu Jan 11, 2018 5:48 pm
:D
drhardlove wrote:
Thu Jan 11, 2018 5:45 pm
skank wrote:
Thu Jan 11, 2018 5:33 pm


Thanks!

I've had it for years. Brilliant. But it still can't bring back the older VSTs, or make my Cubase boot times acceptable and stop Cubase from blacklisting VSTs and then forcing me to unblacklist each VST *individually*. Try doing that with a 100+ VSTs :(

Thanks maybe I give it one more try 8-)
Besides being halfway cleared from charges of spamming etc. I came across this for you. https://jstuff.wordpress.com/jbridge/jb ... eshooting/

The link will take you to his post on wordpress. You will have to scroll down to find it.
But here is a copy of the post. ;-)

18 – “How about DX/DXi plugins?”

Although I can’t offer (much) support for this, it was interesting to verify that DX/DXi plugins can be used in 64bit VST hosts by combining jBridge with Frank Potulski’s excellent mfx/dx/dxi wrapper dxshell. You’ll need to bridge the dll(s) created by the wrapper.

You can find Frank’s wrapper here:

http://xlutop.com/buzz/

You can read more about it here:

http://www.kvraudio.com/forum/viewtopic ... sc&start=0

Locked

Return to “General”

Who is online

Users browsing this forum: babaorum, delta, whansen and 6 guests