As you may or may not be aware of, Cubase 9.0 only supports 64bit vst and dropped support for 32 bit vst.
They also added a new feature called Sentinel which examines all of your vsts and blacklists all 32 bit vst and any vst it has determined that can risk stability of the program. If a 64 bit plugin gets blacklisted, you may try to reactivate the plugin but it won’t always work.
The latest: Sub Phatty Editor-VI(x64).dll (version 1.1.0) not only gets blacklisted but reactivating fails as well.
See below:
Now the vst effect plugin: Sub Phatty Editor(x64) will run in Cubase but there seems to be a few issues (on my system at least) but I will start another thread for that.
SPHE VI 64bit is blacklisted and cannot be activated, and SPHE VST 64bit loads and works (except for general Editor bugs) ?
Are you confident you did place the 64bit VI dll in the 64bit folder, and not the 32bit one, by mistake ?
We would really appreciate if you could also install S37E and MTRE in the same system and let us know how VST and VSTi of any of them act in C9. Latest S37E is 1.0.0 and MTRE is pinned on top of the forum. No need for the actual hardware.
Yes, it was definitely the 64bit instrument. See pic below:
I tried both (64bit) VST2 and VST3 of the Mintaur and both seem to run fine in Cubase 9.0. I even tried automation lane recording in realtime and both responded well. Receiving and Sending from what I could tell without having the hardware. I just used a midi controller.
The only Sub 37 .dll I could find on the forum was the effect. I did not see an instrument vst anywhere. Is this correct? Anyway, that ran fine also in Cubase 9.0.
Going back to the Sub Phatty, I was unable to successfully use the current SPE inside Cubase without the USB AND DIN connected. After the latest firmware update, I was able to use just the USB connected with the standalone without hardware disconnects. Inside Cubase, however, I needed both USB and DIN. It also seemed more successful to hide the Sup Phatty USB port inside Cubase to avoid hardware disconnects. Once I had it working, it worked a little better than before. I wasn’t able to record lane automation in realtime but I could draw it in and the editor and hardware seemed to respond okay.
Also, on the midi drivers, I was unable to install the 3.30 successfully. I tried many different times in many different ways and no matter what, I would always end up with an exclamation in device manager. I would never be able to see the port inside the standalone editor either. What worked for me was uninstalling all the moog drivers, cleaning them from system32, and just letting Windows do its thing. I read and reread the info from the latest thread and I was a little confused if we are suppose to use 3.30 on windows or not?
No VSTi for S37E at this point (may add that later).
As for the SPH driver, once all existing moog drivers are removed you should basically install the dedicated moog drivers for each product (S37, MTR and SPH).
This should allow sharing USB connection between the DAW and the Editor.
In Windows 7, use v3.30.0 for SPH and MTR, and v2.23.0 for S37.
I was finally able to successfully install the midi driver once I did a needed Windows security update. I saw a post way back by Amos that mentioned this and that definitely fixed it. Now I am able to connect successfully to Cubase with just the USB.
Everything is working great but I still noticed that I am unable to create lane automation in realtime in Cubase. It responds to automation that is manually drawn in but not any that’s done in realtime on the lanes beneath the track. Is this something that will be addressed in the editor update?
Other than that, everything is working great in Cubase 9.0!!!
I tried both the Minitaur and the Sub37 vst, using the SubPhatty hardware to control them, and they both work correctly with lane automation. So that’s good!!!
So I will wait on the new SubPhatty Editor before doing these tutorials, okay? I want to show how to set up automation in the tutorials just to cover everything.
If this is okay, will you let Amos know? I don’t want to bug you guys about a new editor release date so I will just come by here every other day or so and see if there is a new SPE released. If you need me to beta test the editor in Cubase when it’s ready, just let me know here or shoot me an email.
