Question A.) Why would someone who has a purchased version install the R2R version to see what runs faster.
Answer A.) "just to see if any performance improvements?"

Question C.) Why do you ask ?
Answer C.)"just to see if any performance improvements?"

 

on closer inspection I found that there is a problem finding most of the VST3, I have specified the Common Files\VST3 folder but it doesn't find them..... Anyone having the same problem?

 

VST plug-in locations on Windows
https://helpcenter.steinberg.de/hc/en-us/articles/115000177084-VST-plug-in-locations-on-Windows

 

I added the Common Files\VST3 folder, but the DAW just doesn't detect them. Apparently I will have to install newer versions

 

Are your 3rd party VST3’s 64bit and in the following folder " C:\Program Files\Common Files\vst3 " ?

Try installing any VST3 plugin in that folder.

 

I know they are in that folder I have quite a few VST3 installed in there, but Cubase 12 doesn't detect them.

 

The same Problem here…Cubase 12 does NOT SCAN
C:\Program Files\Common Files\VST3 !

The only VST3 Folder scanned is
C:\Program Files\Steinberg\Cubase 12\VST3

So I created a new folder in
C:\Program Files\Steinberg\Cubase 12\VST3

and made a symlink to
C:\Program Files\Common Files\VST3

Now it works. For all: Search for a program called JunctionMaster Pro by Bitsum (can’t post links here), with it you can make symlinks.

https://forums.steinberg.net/t/cubase-12-stuck-on-scanning-vst3-plugins/770145/22

 

How to Fix Blacklisted Plugins in Cubase 10

Re-setting the Cubase plug-ins cache manually Print
Modified on: Tue, 12 Jan, 2021 at 3:12 PM
https://acusticaudio.freshdesk.com/...re-setting-the-cubase-plug-ins-cache-manually


Windows and VST3 format:

Close Cubase.
Press Windows key plus R.
Enter “C:\Users\%username%\AppData\Roaming\Steinberg\Cubase 11\Cubase Pro VST3 Cache\” (without the quotes), and click on OK.
Manually delete the vst3blacklist.xml file (to delete the blacklist).
Manually delete the vst3plugins.xml file (to force a complete plug-in to rescan).
Re-open Cubase.

After deleting the plug-ins cache files, on the next run, Cubase will re-scan all of your VST2/VST3 plug-ins, and depending on the number of VST2/VST3 plug-ins installed, the process may take several minutes.

 

and to add to that
Cubase will, as soon as one plugin misbehaves, blacklist it/them again.
when that happens, just go to the plugin manager and, de- Blacklist it again
happened with a few arturia fx on my end.

 

The VST3 update solved the problem. "I want to tell those who installed''VST_Transit_64bit'' To uninstall it because it may cause Cubase to crash or slow down.

 

Last edited: Apr 20, 2022

"VST_Transit_64bit" It's in the R2R release

 

VST Transit
Embedded in Cubase Pro and Cubase Artist, VST Transit offers an unprecedented cloud service that allows you to upload audio and MIDI tracks to cloud storage. Work on your projects from different locations, write a song together with your band members and synchronise all changes. VST Transit is just one of many professional tools in Cubase and the possibilities are endless!

Steinberg – Cubase Pro 12 v12.0.0 x64 + Steinberg Silk Emulator R2R

install
———————————————— ————————————————– –
Uninstall previous versions.
Mount ISO file. Run “Cubase12.msi” and install.
Install “Generic_Lower_Latency_ASIO_Driver_64bit.msi” if you need.
Install “VST_Transit_64bit.msi” if you need.
If you have “Steinberg Library Manager (SLM)” installation,
=> Run SLM.
=> Drag & Drop included “Content” folder to SLM GUI.
=> Install all. Done!

 

I have about 20-30 more plugins blacklisted but I attribute it to 32 bits, I read somewhere that Cubase 12 doesn't accept 32 bits VST.

 

Cubase does not support 32 bit plugins anymore. Quite an audacious decision.
You can just move the 32 bits to use them in another DAW !

 

Yes, there is a lot of good stuff in 32 bits that isn't in 64 bits unfortunately.

 

Just sharing my experience, in case someone finds it useful:

I installed the 12.0.0 V.R. version because it appeared first in the sister site. It was running without any problems, apart from a message I was rarely getting at the start that Cubase didn't shut down properly (even though it did).

Then I installed the 12.0.10 V.R. (without uninstalling the previous one) and now I'm experiencing this:
Cubase suddenly shuts down (the window disappears as it never existed) which is, of course, frustrating.

But I'm not gonna ditch this version, nor I want to start (or continue) a V.R./R2R war. Here are my thoughts:

- I'm on Win 10 20H2 - which is officially not supported by Steinberg and maybe this update is more picky to that.

- I stopped running Cubase in Administrator Mode, because I couldn't drag n drop audio files from the explorer right into the project (I had to do this only via Pool, which was PITA), so that may cause the stability issue. (?)

- This issue appears in specific projects, so that may be a conflict caused from a plugin (I recently installed the Digitalis from Aberrant, which is in 1.0 version, so that may be an early bug).

- Maybe I should have uninstalled the previous version and done a clean install for the 12.0.10. (?)

I'm still investigating it, but any opinions are more than welcome

 

I have found both versions eminently usable despite my disappointment with cubase as a DAW.

 

If you read the enclosed NFOs, i.e. the installation instructions, and stick to them, you will clearly live a
more stress-free and error-free life. In other words, those who can read are clearly at an advantage.

Steinberg Cubase Pro 12 v12.0.10-R2R

* No SteinbergLibraryMangager is required (optional).
* No SteinbergActivationManager is required.
* Loads faster than legit version.
* No compatiblity issue with other legit Silk and Silk powered apps.

Read included R2R.txt to see how to install.

 

I agree with that, but I don't find any connection between the one you quoted and your answer. Care to elaborate?