Cubase 14 problem - again :-(

[OneWorld]

There are times when I regret doing updates.

I did the recent update to Cubase 14

All seemed well, but the day after I got an update from Arturia for the Modular V3, and I noticed it said 'Not activated' that's odd, it's been activated for years.

Anyway I did the update (to Modular V3)

I didn't work any more. I had a fiddle around and got it working, basically it's like a new install, hence - 'not activated' message I guess. Now it is activated.

But Cubase 14 refuses to see it. When I try and add Modular V3 to a track, it is listed in the Cubase VSTi 'rack' I select it, but nope, no Modular V3 appears.

I read on the internet that this is most likely because Modular V3 is a .vst3 instrument, it has to go into the %commonprogramfiles%\VST3

Modular V3 is in that folder. I have tried restarting the computer, and Cubase

I opened Cubase Plugin Manager and sure enough Modular V3 is showing in the VST Instruments list. but it refuses to loaded into the Instruments rack even though it is listed.

It works as a standalone, it is just Cubase it has a problem with.

I tried adding the V3 as an Instrument track, again, it is listed in the 'rack' I select it, but nothing.

Any ideas?

[alexis]

Is that the same folder your other VSTi's reside in?

[OneWorld]

Is that the same folder your other VSTi's reside in?

No and I read that .vst3 have to go in that folder, and that seems to be confirmed by the fact that all the other .vst3 are in that folder. AFAIK, the .vst2 can go any old place, in fact I have created folders where I can put .vst2, but not .vst3

[The Elf]

All VST3s go in that single folder (much better than the VST2 debacle).

As to why you can't load it into Cubase... no idea. I can load all my Arturia VST3s and VST2s, no problem. Sorry!

Presumably your other non-Arturia VST3s load OK? And presumably you've tried loading the VST2 versions of your Arturia instruments?

[The Elf]

I've tried a few things this morning to see if I can make Modular V VST3 fail as you describe. I'm having no joy. Maybe time to consider a careful (but thorough) uninstall/re-install?

Maybe teaching egg-sucking here, but a VST3 plug-in is shown in Cubase by three lines over to the right of the name in the plug-in loading list - worth a double-check.

[Wonks]

If you are using your own list of plug-ins in Cubase (I know I do), and you say Modular V3 behaves like a new plug-in, then maybe you need to manually add it to the list of plugs you see?

[OneWorld]

I've tried a few things this morning to see if I can make Modular V VST3 fail as you describe. I'm having no joy. Maybe time to consider a careful (but thorough) uninstall/re-install?

Yes I understand the preference for the .vst3 setup as opposed to the "vst2 debacle" and so in theory, if a .vst3 is in the right place, the Cubase scan goes through its process and finds whatever is in the VST3 folder.

I have other non-Arturia VSTi3 plugins in that same folder and they load as expected.

I have been using Modular V (version 3) as a .vst3 for years, no problem with it whatsoever. This problem has occurred after the latest Modular V update

I too am thinking a fresh install of Modular V to re-establish filepaths etc

One of the things that confuses me with Arturia software installs, at the end of the process it says "Install complete, do you want to continue or re-boot to finish the process?"

I think that is so ambiguous but I think what it means is, associated files might/might not have been updated, if they have, you can continue working without a re-boot, however if you re-boot that will ensure associated files are re-freshed and the config updated, but that is me being pre-sumptious

I have also noticed that other VST3i's have the .dll (the instrument itself, in this case modularv3.dll) but also there is a content folder. The Modular V3 has nothing except the .dll

Anyway, I have contacted Arturia for support, the last time I needed do that was donkeys years ago and they did live up to their claim to respond within 48 hours, which is OK

[OneWorld]

If you are using your own list of plug-ins in Cubase (I know I do), and you say Modular V3 behaves like a new plug-in, then maybe you need to manually add it to the list of plugs you see?

No, for .vst3 plugins, they have to go into the designated folder. When I used to use .vst2, yes I created folders myself and scattered my VSTs about the computer firmanent, which as Elf comments, was a debacle, AFAIK, that hotch-potch has been dealt with by Steinberg by saying "VST3's go here, and that's that" which makes sense I reckon

[The Elf]

One thing I *am* noticing...

Even though I've manually removed almost all of my VST2 plug-ins, Cubase still has them listed (and refers to non-existent Windows folders) in the Plug-in Manager.

Hmmm...

So I wonder if you are actually trying to load a plug-in file that no longer exists, and it is failing due to this?

I have also noticed that other VST3i's have the .dll (the instrument itself, in this case modularv3.dll) but also there is a content folder. The Modular V3 has nothing except the .dll

A .dll file is not a VST3 plug-in. That's a VST2 version. .dll files should not be in the VST3 Windows folder, and .vst3 files should not be outside of the VST3 Windows folder.

And if you don't have the .vst3 file, then you do not have the VST3 version installed.

...and that might be why the load is failing - a combination of Cubase reporting a plug-in that no longer exists, and a missing .vst3 file from the 'C:\Program Files\Common Files\VST3' folder. Might be...

Could be worth installing the 'Everything' utility to see what you can find and where it lives: https://www.voidtools.com/support/everything/

[Wonks]

You misunderstand.

Yes, put them in the VST3 folder, that's a requirement.

But with the plug-in manager you don't have to create a list that shows all the VSTs/VSTis available. For instance I always get tons of demo versions of UAD plugs that make navigation of the default list a real PITA. So I use the plug-in manager to create my own list of plugs and organise them into my own folders.

If you are using such a list for your plug-ins, then Cubase may omit the missing Modular V2 from the list but not then automatically replace it with Modular V3, which you may have to manually add to your own plug-in list. It all depends how Arturia have named the files. If they aren't exactly the same name, then Cubase won't know it's a replacement and will treat it as a different plug.

[OneWorld]

You misunderstand.

Yes, put them in the VST3 folder, that's a requirement.

But with the plug-in manager you don't have to create a list that shows all the VSTs/VSTis available. For instance I always get tons of demo versions of UAD plugs that make navigation of the default list a real PITA. So I use the plug-in manager to create my own list of plugs and organise them into my own folders.

If you are using such a list for your plug-ins, then Cubase may omit the missing Modular V2 from the list but not then automatically replace it with Modular V3, which you may have to manually add to your own plug-in list. It all depends how Arturia have named the files. If they aren't exactly the same name, then Cubase won't know it's a replacement and will treat it as a different plug.

Why would I have to add what has been there since antedeluvian times? And in the past I have used it, and it's updated several times without any problem whatsoever, till now?

[OneWorld]

You misunderstand.

Au contrar, I didn't put them anywhere, the install, which I installed years ago put them where it puts them and it worked flawlessly- until now, when it went through its usual process of updating, nothing unusual, it went through the process as it has always done, and not requiring any input from myself. I was simply saying, there is a .vst3 in the VST3 folder, how it got there I do not know. It is only VST2 plugins where I have put anything anywhere, vst3 have been left alone and when they update, I just click the "Whatever Turns You ON" button and off it goes, a few minutes later I have an updated and functioning VST3

Yes, put them in the VST3 folder, that's a requirement.

But with the plug-in manager you don't have to create a list that shows all the VSTs/VSTis available. For instance I always get tons of demo versions of UAD plugs that make navigation of the default list a real PITA. So I use the plug-in manager to create my own list of plugs and organise them into my own folders.

If you are using such a list for your plug-ins, then Cubase may omit the missing Modular V2 from the list but not then automatically replace it with Modular V3, which you may have to manually add to your own plug-in list. It all depends how Arturia have named the files. If they aren't exactly the same name, then Cubase won't know it's a replacement and will treat it as a different plug.

Why would I have to add what has been there since antedeluvian times? And in the past I have used it, and it's updated several times without any problem whatsoever, till now?

[OneWorld]

One thing I *am* noticing...

Even though I've manually removed almost all of my VST2 plug-ins, Cubase still has them listed (and refers to non-existent Windows folders) in the Plug-in Manager.

Hmmm...

So I wonder if you are actually trying to load a plug-in file that no longer exists, and it is failing due to this?

I have also noticed that other VST3i's have the .dll (the instrument itself, in this case modularv3.dll) but also there is a content folder. The Modular V3 has nothing except the .dll

A .dll file is not a VST3 plug-in. That's a VST2 version. .dll files should not be in the VST3 Windows folder, and .vst3 files should not be outside of the VST3 Windows folder.

And if you don't have the .vst3 file, then you do not have the VST3 version installed.

...and that might be why the load is failing - a combination of Cubase reporting a plug-in that no longer exists, and a missing .vst3 file from the 'C:\Program Files\Common Files\VST3' folder. Might be...

Could be worth installing the 'Everything' utility to see what you can find and where it lives: https://www.voidtools.com/support/everything/

You're right. It isn't a .dll file, it is VST3 Plug-in File, and, in the same way as other VST3's, it's all over the place - common files local and roaming, in the Arturia folders (I guess that is for the standalone option, which is working)

I think you're right about the 'ghost' appearance, yes it is listed in the Cubase VST 'rack' because it is a left over. I am coming to the conclusion that the update scavenged the previous version (the pre-update version) but didn't install the update, except the standalone

[OneWorld]

I ripped it out and re-installed, it installed the latest version v 3.13.3.6106

And it works again

[OneWorld]

I can't say I am impressed by Arturia support.

Their reply to me said....

Open Cubase Plugin manager,
Scan the plugins
Add the folder to the list of folders to be scanned (All of which I had already done, and I had informed them of this in my support request)

I had done the above in full knowledge it would be futile, because the Modular V3 is .vst3 anyway

Surely Arturia could have suggested what I'd done - re-install?

[The Elf]

I ripped it out and re-installed, it installed the latest version v 3.13.3.6106

And it works again

[OneWorld]

I always approach re-installing with some trepidation after a bad experience on two occasions, where after a re-install, as a result of a broken computer, I'd used up all of of my 3 'lives' with the software.

As it happens, Arturia does allow you to get a life back by de-licensing a computer, which is handy to know. Thanks for the help anyway.

[The Elf]

I always approach re-installing with some trepidation after a bad experience on two occasions, where after a re-install, as a result of a broken computer, I'd used up all of of my 3 'lives' with the software.

As it happens, Arturia does allow you to get a life back by de-licensing a computer, which is handy to know. Thanks for the help anyway.

Been there. Some companies are sympathetic and will activate a 'reset' button somewhere, but others won't. Guess which ones I still give my business to...