![]() I also never look at it or do something about it. I never have one plugin worked out and they keep blacklisted. If has also to do that the plugin must behave alike the testsystem and pass the test. I have 3 plugins in blacklist and know why, they do not work with cubase at all.īut i have tried to make them work, cubase did not accept it and blacklisted them. Sometimes cubase test of the plugings might be the fault. If one or two fails the test i am sure most of the time the plugin is at fault. The combination of 3 vst plugin kinds and maybe a user has 50 plugins installed or more. It has to do with Windows, Cubase and all plugins tested. It may well be that there are other factors at play too, a dodgy update on the soundtoys plugins etc, but that doesn’t explain ALL of the different issues Started occurring for most with the recent cubase updateĮrgo - most likely issue is within cubase. Happens on plugins that have been working fine for months/years Often reports 32bit when plugin is 64bit - even though plugin manager shows 64bit therefore misreported. ![]() It’s happening to cubase AND nuendo but on different plugins - so inconsistent. It’s not ilok specific - as not all the blacklisted plugins are ilok protected Maybe you have another issue with your system ? 50 update, so no that’s not the reason - but thanks for trying to help. Re-enabled plugins working fine for me as they have been for months before the. Not working means not working correctly by testing live. The proof that cubase/nuendo is at fault seems to be that they are often listed as 32bit even though they are 64bit - or that they are blacklisted in nuendo but not cubase or visa-versa - so there isn’t some ‘hidden’ list of non-working plugins that is being checked at startup…if that’s what you were implying ? So it is system specific and you want them to work ? You find out why…ĭidn’t really understand this reply - sorry I can say all the plugins that are in my Blacklist are not working, and i know that because they really do not work. If Steinberg would not test it, the plugin would prob crash you Cubase while working inside a project. I work with Jbridge and have 32 bit plugins running.Īll my blacklisted plugins are there for a reason. Steinberg has directories for VST3,VST3 (64 and 32 Plugins). The best thing is to look where the plugin is installed. This means the plugins can work in other systems. Most Blacklisted plugins are really tested bij C10 and Blacklisted because of the test.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |