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.
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ā¦
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
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.
It works. Make sure itās updated.
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)
Me too.
But JBridge brought them back.
My experience too.
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. 
Thanks maybe I give it one more try 
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.
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.
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.
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.
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.
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.
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.
This link it is not working anymore. I donāt know since when.
JBridge works great, and Steinberg has support for it. Check the link on JBridge as solution here https://www.steinberg.net/forums/viewtopic.php?f=250&t=107299 . Let me ask you also, did you make a JBridge support thread?
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.
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.
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.
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.
Really? Are you a Steinberg employee for real. Donāt be angry, try to communicate your frustration.
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.
This is part of the misconceptions you will find in this thread, but we are here to enlighten each other, be patient.
How do you know that? Are you working for Steinberg?
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.
I hope you know by now, that JBridge can give your door stops a new life, for 20 euros.
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
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.
+1 for jBridge
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.
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. 
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
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.