Hi Guys,
After the recent updates OP-Xa has gone missing from my Windows desktop (shows a document icon) and Cubase blacklists the VST3 file.
I tried to re-install with no result.
Sorry to put this on you before Christmas!
Hey @Starburst and welcome to The Sound Explorers Forum.
Ok, let’s see if we can sort this out together.
I take it you’ve used ASC to manage your OP-Xa?
Have you checked the plugin manager in Cubase to see if it is there or is in the blacklist?
If you don’t know where this is, look at the top of the screen in Cubase for the ‘Studio’ option, click this and select ‘VST Plugin Manager’ from the list, i cannot screenshot this for you on Windows unfortunately.
I can screenshot the plugin manager though so once open you’ll see this…
Click on the VST Instruments tab that i’ve highlighted in yellow and it will take you to the VST instruments you have and Cubase has recognised, see if it is in here, if not then click on the ‘blacklist’ tab as in the pic below…
If it is listed in here, i just have some old residual 32bit plugs left over from ‘the old days’, so i cannot show you how to reinstate a blacklisted plugin, from memory though you should just select it by clicking on it either right click or a menu box will open under the main panel that lists what’s in the black list, if it’s there you should be able to reinstate it.
If it’s not in either of those it would be worth forcing Cubase to rescan your plugins, this might take a while if you have A LOT of plugins.
To do this, Click on the ‘refresh’ icon i’ve highlighted below…
Let us know how this goes for you, if it doesn’t sort it then we’ll try the next step.
Ps,
Please make sure to subscribe to our Newsletter to be the first to know about the latest from Arturia.
Hi Mat,
Thank you for your reply and assistance.
Attached are screenshots, I have tried reinstall from ASC and rescan in CB13.
Best regards
Adam.
HI @Starburst
Yes i can see that OP-Xa is in your blacklist, as i mentioned earlier, i do not have anything that shouldn’t be in the blacklist, so am unable to screenshot how to move it from there back into your normal plugins, this article from The Cubase 12 manual will walk you through it.
I’m not sure about your standalone version though.
It might be worth you logging in to your account to contact our support team that will help you to fix this situation.
Best 
HI @Starburst
Ok, it sounds like you might want to un/reinstall OP-Xa, this is a bit of an odd one.
Before we look into that, are you running both Cubase and ASC in admin mode? It sounds like there MIGHT be some kind of permissions issue.
Hi Mat,
I tried to uninstall and reinstall without any result.
The OB was working AOK and used in a number of projects, ASC recently updated all the plugins and the OB hasn’t worked since. There doesn’t seem to be a problem with any other unit as I am aware.
I think I am the only user so I guess I am in admin mode.
Thanks for your help, it’s really appreciated.
Adam.
HI @Starburst
You can check to see if you are in Admin Mode by right clicking on an app’s icon/properties/advanced. You’ll get a pop up box that will tell you what state it is currently in and the option to change it to the other.
I’d see what your DAW, ASC and other Arturia instruments are being run as.
HTH!
Hi @matjones
The interesting point here was that when I tried to uninstall through ASC it didn’t seem to complete the task and the files were still within the program folder. I tried to uninstall from the program folder and this popped up errors. I then tried to run the OP-X standalone and that wouldn’t load either. So something was seriously wrong with the files.
So I re-downloaded the installation files directly from the Arturia website and installed from the download file and not ASC and it worked!
So it’s sorted, result happiness! 
Thanks for all your help.
Adam.
There is a major problem with the OP and I have discovered it.
I see you also had the problem. I have spent 2 years suffering with this since I bought the V Collection 8.
Regard this simple screenshot I took tonight:
Seriously, spent 2 years without this plugin in Studio One because the list there only showed “OBxa” which I finally discovered a week ago pointed not to an Arturia plugin (though the heading of that section of Studio One’s instrument plugin browser was clearly “Arturia” and all the surrounding synths were V Collection synths.
No, when I finally instantiated the instrument listed there ON a track which I created as an Instrument track and pointed towards that item (I forgot to mention, that item could not be placed on a track or dragged into the edit window as a new track creating item, which is the regular way to do it in S1) it finally gave me a readout of the error, which was that it pointed towards the OBxa from KVR (something like 10 year old plugin now). Not the Arturia at all.
Don’t know how much of this was your problem, but it was definitely mine, THE CULPRIT. Presumably the Arturia plugin shown here was renamed after first coming out in 2021 due to maybe some licensing restriction placed by Oberheim. At any rate, once I finally removed this item (which I must have got as a Demo version in 2021) I was finally finally able to get OP X to show up in Studio 1 after 2 frustrating years without the possibility!
And I just realized I may have grabbed the wrong plugin somehow when I did make that track as an instrument track, just looking for a plugin with the same name, but regardless, the OBxa V listed there in the browser would NEVER open up. So I feel that it really is an Arturia problem, as this was even today still in my VST3 folder after yesterday upgrading to Arturia V collection X and doing a complete re install of all Arturia plugins. Only upon finally finding this little dickens there in the VST3 folders and removing it, did I finally get the OP X V to show in S1 Browser!
I cleaned so many files out of my VST3 tonight. It was such a big mess of duplicates and things. Some of the vendors with many plugins (Analog Obsession) I placed into their own folder the largest group I could find, then cut and pasted into the general VST3 folder, which gave the option to overwrite, then cut the new grouping, of all and pasted back into the dedicated folder. I did this with several vendors and it really helped to clean things out.
The ASC V Collection install, not replacing this OBxa V VST3 is a definite problem in my opinion they should remedy. We don’t after all, get any choice where our VST3 install takes place. In my opinion they want to create an Arturia dedicated folder in the Common Files/VST3 folder so the things can be better organized and not just loose there in the melee of hundreds of other VST3s from all sorts of vendors.
Hi @nModular
To clarify a little, OB-Xa WAS the original name of the plugin OP-Xa, the name was changed a little while after its release, i do not know why, possibly an objection from Oberheim i’m guessing.
From memory, when the name was changed, ASC handled the issue, of course if there were any active versions of the original name in someone’s project, then it’s likely they would have had to change the plugin over manually in said project/s.
This is one of the reasons Arturia encourages people to use ASC to manage their software products and in general it does a VERY good job.
HTH!