Cubase 9's Plug-in Manager going wrong

[noiseboyuk]

I don't get what all the hubbub is about. I have millions of plugins and there is no problem. The only things for me that got blacklisted were the VST 2 counterparts of the plugins that have a VST 3 version. I use the VST 3 versions anyway, so I have no problem with that. Everything else was fine.

I'm not sure why you "don't get" other people's direct experience? Isn't that rather like saying you "don't get cancer" because you've never personally had it?

Weasel-boy - sounds very clever, and good luck to anyone who tries it. You'll likely have to do that after every single update mind. Personally, I think its far wiser to embrace the Sentinel than try to hack it away. I constantly read people claiming of blacklisted plugins that have always worked fine, but I'm not always convinced that they did necessarily work fine. Sternberg's whole point, really, is that rogue plugins don't always wear their rogueness on their sleeves, it can cause system-wide issues that don't appear to be related.

So many people complain about their DAWs having glitches, spikes, crashes etc - this looks to me to be a serious attempt to address that, since rogue plugins are a leading cause of instability. While it's unlikely you'll get everything working smoothly for every plugin on day one of installing C9, I personally think it's a tool worth working with, rather than against. So all the best and good luck to those trying the hack - and you'll have no doubt good reason for doing so - but you'll be unlikely to get much sympathy if you continue (or start) to get performance issues.

[Orbit-50]

I'm not sure why you "don't get" other people's direct experience?

I'm sorry if I seem insensitive to people's computer woes, but out of all the years I've been into this, I've gone through 6 different computers and I've learned that it's pretty straight forward. Keep your computer clean, move forward with OS updates by getting a newer computer every 3 to 4 years, install stuff as directed, and there will be no problem. Sure, there will be bugs here and there, but the catastrophes I keep seeing all over the place are probably not the fault of the software itself. The software developers in question would be in serious financial trouble if that were the case. Macs on the other hand, I can't speak of because I left that camp a long time ago. I feel terrible for those users because every forum in the world is flooded with Mac OS issues. I actually wish every forum would make a separate area for Mac users so I don't have to keep sifting through those threads. For all the people that are not having issues with Apple computers, the people that are having issues should follow their lead. As for Windows I've never had a problem with any software not working as it says on the tin. Well, except for MOTU DP8, but that was my fault because I should have demoed it first, and I should not have put so much trust in them flawlessly porting DP to Windows. Other than that? Nada.

[fmr]

I'm with you on this. It's funny that, nowadays, the platform that "just works" as they told in some advertisings, is the one that has more complaints and needs mpore workarounds. Much of the fault, IMO, should be pointed to Apple itself, because, instead of putting out of the door a "new" OS every year that should instead concentrate in polish and make it work as supposed the OS that was already in the field.

Unfortunately, too much people is blindly following them, ands many times blaming third parties for what was to blame Apple in the first place.

[Orbit-50]

I'm with you on this. It's funny that, nowadays, the platform that "just works" as they told in some advertisings, is the one that has more complaints and needs mpore workarounds. Much of the fault, IMO, should be pointed to Apple itself, because, instead of putting out of the door a "new" OS every year that should instead concentrate in polish and make it work as supposed the OS that was already in the field.

Unfortunately, too much people is blindly following them, ands many times blaming third parties for what was to blame Apple in the first place.

Excellent post. That's the exact reason I left them a long time ago. On the flipside, I dearly miss Macintosh though. (Shows my age. ) They are the most beautiful computers, and the delightful environment is to die for. This is probably the draw for Mac freaks. I was there. I've even considered switching back just for those reasons, but all the issues I keep seeing... and as you said, it's not always the fault of the developer or the user in those cases so they are just collateral damage in this whole thing.

[noiseboyuk]

I'm not sure why you "don't get" other people's direct experience?

I'm sorry if I seem insensitive to people's computer woes, but out of all the years I've been into this, I've gone through 6 different computers and I've learned that it's pretty straight forward. Keep your computer clean, move forward with OS updates by getting a newer computer every 3 to 4 years, install stuff as directed, and there will be no problem. Sure, there will be bugs here and there, but the catastrophes I keep seeing all over the place are probably not the fault of the software itself. The software developers in question would be in serious financial trouble if that were the case. Macs on the other hand, I can't speak of because I left that camp a long time ago. I feel terrible for those users because every forum in the world is flooded with Mac OS issues. I actually wish every forum would make a separate area for Mac users so I don't have to keep sifting through those threads. For all the people that are not having issues with Apple computers, the people that are having issues should follow their lead. As for Windows I've never had a problem with any software not working as it says on the tin. Well, except for MOTU DP8, but that was my fault because I should have demoed it first, and I should not have put so much trust in them flawlessly porting DP to Windows. Other than that? Nada.

i upgraded my main W10 rig to C9 Pro today, after my trial with C9 Elements on the MBP. Essentially went without a hitch on W10. Lots of issues with the MBP though, as detailed here. Turns out iZotope has to be MacOS, while OSX will cause problems. Needless to say, other audio apps are reversed - conventional wisdom says its still too soon to switch to MacOS.

This is just one example of the myriad of gotchas out there. And no, Windows isn't immune from audio issues of course - I had so much trouble with Waves a few years ago running Radeon graphics cards. Switched to nVidia - problem vanished. Your basic rules seem fine, but I'm always wary of drawing sweeping generalisations. Computers are such complex beasts, with so many variables, anything can happen to any of us without warning.

To bring it back full circle - VST Sentinel is a step in the right direction for harmonious system running. People hacking their installs to disable it is is 100% the wrong direction imo .

[Weasel-Boy]

Weasel-boy - sounds very clever, and good luck to anyone who tries it. You'll likely have to do that after every single update mind. Personally, I think its far wiser to embrace the Sentinel than try to hack it away.

Noiseboyuk:

Just an update. I agree with you. The whole thing was an interesting experiment that actually worked, but as you say, I’d have to keep doing this with every update. And with or without the hack, I was getting less than optimal performance out of C9. Even though it worked, I was never really comfortable with the hack as a whole.

My experiment was motivated by running C9 on Yosemite more than anything else. I wanted to run Sierra, which Steinberg specs as the system requirement for this release.

Problem was that my machine is an early 2009 MacPro-4,1 dual 4 core Nehalem. Sierra won’t run on it. Once the AppleStore sees the machine as a 4,1, it won’t even download it.

However, years ago, Apple released an EFI flasher to convert the boot ROM for these machines from 4,1 to 5,1. So I tried it and hit worked like a charm and I was able to install Sierra and reinstall Cubase 9.0.1 from scratch.

The results were night and day. The Blacklist behaved correctly this time, passing pretty much everything 64 bit (there are still a couple of issues, but these are known and being dealt with). The entire feel of Cubase 9 is noticeably improved and I am quite happy with the results.

[fmr]

The results were night and day. The Blacklist behaved correctly this time, passing pretty much everything 64 bit (there are still a couple of issues, but these are known and being dealt with). The entire feel of Cubase 9 is noticeably improved and I am quite happy with the results.

I wonder WTF is Apple doing with their OS for a system that's a little more than two years old to make such a difference to the current one.

[Weasel-Boy]

I wonder WTF is Apple doing with their OS for a system that's a little more than two years old to make such a difference to the current one.

It may not be Apple as much as Steinberg optimizing C9 to run on Seirra. They do state that Sierra is the required OS for this release.

On the outside, there doesn't seem to be much functional difference between Yosemite and Sierra beyond some bloatware and the System Integrity Protection (SIP) scheme they introduced in 10.11. But there is always something they do that affects graphic performance and to a lesser degree, audio performance. You never know with Apple beyond their marketing spin.

The only other thing I'd check under Sierra is to check compatibility any audio-related drivers with the newer OS.

[dzilizzi]

So I am building a new computer and having to reload everything. So now, I only have Cubase 9 and not 8.

I loaded the Waves plugins and directed Cubase to look at the folder (in the 32 bit programs - not sure why they load there) Blacklisted all of them. So I checked Waves again and found they also load the 64 bit app to a general VST folder. Added that. I now have about 20 of my Mercury plugins not blacklisted. And very few are the ones I use. I'm kind of hoping someone figured out how to deal with this, since Waves state all the plugins are 64 bit. I also don't remember having a choice of where to install anything when installing Waves.

[Djsegwon]

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.

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 (https://m.facebook.com/groups/122940794511697?view=permalink&id=955638731241895&fs=2&ref=bookmark&notif_t=group_comment)

[Googly Smythe]

I hear that in the. 5 update Steinberg is going to do a Microsoft and delete the plugins it doesn't like.





























BAZINGA!

[Orbit-50]

I have no problem with my Izotope plugins. Cubase only blacklists the vst2 versions, and uses the vst3 versions instead. Everything works fine.

[jancivil]

I'm with you on this. It's funny that, nowadays, the platform that "just works" as they told in some advertisings, is the one that has more complaints and needs more workarounds.

Counterpoint, I don't experience anything I can't sort in a few minutes internet search. That is decidedly not because I'm particularly clever or know a whole lot about computers. There are a couple of things which really suck today, though, such as this 'signed' bullshit where maybe most of installations require me to go into Sys Prefs and force it to install it, then 'Are you sure?' - f**k off.

Workarounds aren't really much of a big deal, to get the hidden Home Library, option-click Go in Finder. Yes, it's stupid and it's to make the OS truly idiot-proof which shows them conflating their little gadgets market with the computer market, although I could be dead wrong and it's largely the same thing, and virtually nobody needs Home Library.

I've come to detest Apple, but I have used a Windows pad in the last year and it was a PITA in a whole new way for me. However solving wifi connections is easily worse on Mac, the Network Diagnostics is so idiotic it makes me want to smash the thing. Apple sucks but at least it's not Microsoft. Has more complaints, who cares, people are stupid.

[chk071]

I'm with you on this. It's funny that, nowadays, the platform that "just works" as they told in some advertisings, is the one that has more complaints and needs more workarounds.

Counterpoint, I don't experience anything I can't sort in a few minutes internet search. That is decidedly not because I'm particularly clever or know a whole lot about computers. There are a couple of things which really suck today, though, such as this 'signed' bullshit where maybe most of 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. Not a big problem in Sierra though, because you can just click to make an exception in the Security settings, and it looks like it also remembers the settings for more software of the same developer.

Workarounds aren't really much of a big deal, to get the hidden Home Library, option-click Go in Finder. Yes, it's stupid and it's to make the OS truly idiot-proof which shows them conflating their little gadgets market with the computer market, although I could be dead wrong and it's largely the same thing, and virtually nobody needs Home Library.

I'm wondering about that. It's also mentioned in the u-he FAQ to use that key combination to view the Library folder. Why not just go to Computer -> Macintosh HD -> Library? The way i understood it, the most plugins are installed there anyway, if you install them for all users? Could well be that i got something wrong there, of course, i'm totally new to the way it works on Mac.

[jancivil]

Yeah, there won't be a lot going on there.
I mean User name/Library; if you for some reason feel the need to delete caches manually (not a lot of reason to, for instance OnyX pretty much covers it) it resides there.

I needed it the other day to place a 32-bit plugin which has the same name as its 64-bit counterpart; there were some installers which actually placed it in 'User name/Library/Audio/Plugins' but last I recall that was before Apple hid it.
Oh, Cubase Preferences, too.