Cubase 9

Audio Plugin Hosts and other audio software applications discussion
Post Reply New Topic
RELATED
PRODUCTS
Cubase Pro 15$579.99Buy

Post

fmr wrote:
chk071 wrote:Just get rid of 32-bit plugins. Problem solved. :) Well, each to his like. I always thought that bridging sucks, and there's always something which doesn't work, the GUI is glitchy and so on. Also devs shouldn't be encouraged to go on developing 32-bit only. It's 2017, everyone has a 64-bit system, most are running a 64-bit DAW... wtf really. Even my phone will be 64-bit soon.
Well, but what if we have some projects created with 32-bit plug-ins that don't exist anymore? Being able to open them, if needed, is something comforting.
Fair enough.

Post

fmr wrote:
dzilizzi wrote: What sucks even more is that they don't give me the option of downloading 8 or 8.5 anymore. Fortunately, I found the 8 installer on my old computer drive. :tu:
You must be doing something wromng. I just checked, and I am still able to download the full installer for Cubase 8.5 (besides Cubase 9).

EDIT: But that's probably because I have another eLicenser with Cubase 8.5, though.
I actually waited to update to 8.5 to when they announce 9, so I never really got the full download. I think if you submit a ticket they will give it to you. I think I will load it just in case since it seems you can have both 8 and 9 running on the same computer.

I updated my Waves plugs and pretty much all of them still show as blacklisted, but now there are VST3 versions in the accepted pool. It is funny though, they took all the Nomad VST2 plugs that came with Sonar without a problem. After I get everything loaded, I will have to go back and figure out what is missing and if I really care. Mostly it's the instruments that bother me if they are gone. I have enough FX that if something is missing, something else will work just fine.

Post

Terrafractyl wrote:Gotta say 9 Feels like quite an upgrade from 8.5

After a few weeks of use I think I have only had one crash, which is actually pretty unbe#$%(#lievable
Especially after 8.5 which was always a bit of a crash fest on my computer, but maybe this was to do with 32 bit plugins...

I had to buy Jbridge to keep using some of my favourite 32bit plugins that are littered through my unfishied projects and I was hesitant about this from the get go, but it turns out to be waaay more stable than the built in bridge that came with Cubase 8.5. I Should have demoed Jbridge and realized this before.... don't know why I didn't!

Loving the Lower Zone, after using live and Bitwig quite a bit. it just feels normal.

Also everything is quicker for sure. Best Cubase ever! :party:
Yes, I have to agree, likely the best version yet.

Post

I've updated to Cubase Artist 9 yesterday. Downloaded the installer, and installed it, and booted it up the first time then... set up the plugin folders, and let it scan the plugins. The first thing it did was to blacklist 3 of its own (!) plugins, i think a surround thingie, a panner, and something else, which was weird. I then chose to update the plugin info, and it then showed me an error message that Voxengo Curve EQ, which obviously is also a part of Cubase's included plugins now causes a eLicenser license error. What is that all about? Known issues?

Post

fmr wrote:
chk071 wrote:Just get rid of 32-bit plugins. Problem solved. :) Well, each to his like. I always thought that bridging sucks, and there's always something which doesn't work, the GUI is glitchy and so on. Also devs shouldn't be encouraged to go on developing 32-bit only. It's 2017, everyone has a 64-bit system, most are running a 64-bit DAW... wtf really. Even my phone will be 64-bit soon.
Well, but what if we have some projects created with 32-bit plug-ins that don't exist anymore? Being able to open them, if needed, is something comforting.

I keep older versions of cubase installed exactly for that reason.
HD space is cheap.
Also if you are on Mac you can use 32lives, works fantastic for using 32bit plugins in Cubase 9, including bringing them in from older projects.
jbridge on PC doesn't work as well as that unfortunately.
rsp
sound sculptist

Post

dzilizzi wrote:
chk071 wrote:Just get rid of 32-bit plugins. Problem solved. :) Well, each to his like. I always thought that bridging sucks, and there's always something which doesn't work, the GUI is glitchy and so on. Also devs shouldn't be encouraged to go on developing 32-bit only. It's 2017, everyone has a 64-bit system, most are running a 64-bit DAW... wtf really. Even my phone will be 64-bit soon.
See, that sounds good. But it is blacklisting my 64 bit stuff as well. Like pretty much every Waves thing I own.

And I am still loading stuff on my new computer, so I haven't tried half of my plugins yet. What sucks even more is that they don't give me the option of downloading 8 or 8.5 anymore. Fortunately, I found the 8 installer on my old computer drive. :tu:

https://www.steinberg.net/en/support/downloads.html

I see as far back as Cubase 6.
rsp
sound sculptist

Post

FTR, i sent Steinberg a support message about the issues i described above. Let's see what they will reply.

Post

I don't have artist, but did you ensure you have the latest e-licenser?
Worth a try maybe.
rsp
sound sculptist

Post

Thanks for the tip, i updated to latest eLicenser, it was pretty old indeed. May have solved the Curve EQ eLicenser issue too, but i'm not sure, as nothing really happens now when i refreh the plugin informations in the plugin manager. The three Steinberg plugins are still blacklisted:

Image

Post

Welcome.
Glad that worked for at least one of the issues.

I am on Mac for Cubase 9, but indeed odd that their own plugins are giving issues. I assume of course you are running the latest Cubase 9 update and by refresh you mean you used the rescan all button?

All the windows issues had to be solved by plugin updates (whilst on mac, bumping to sierra circumvented waiting on plugin developers to update). But surely SB plugins that came with Cubase 9 should be up to date.

rsp
Screen Shot 2017-01-25 at 11.49.02 AM.jpg
You do not have the required permissions to view the files attached to this post.
sound sculptist

Post

I don't have surroundpan on my cubase system,
and my mixconvert is named mixconvert6.

Did you perchance use to use Nuendo?
Those look like Nuendo plugins, left over and indeed may not be updated for Cubase 9 as yet.

rsp
sound sculptist

Post

I don't have Nuendo, but, i had several Cubase versions installed on this computer, Cubase Elements 6, 7, Cubase Artist 8.5, and 9 now. Maybe those are leftovers from a former Cubase version, i don't know. Weird that it copies those in its own folder then though, because they are in the VST2 plugins folder of Cubase Artist 9. I also checked if they're 32-bit, thus got blacklisted, but, no, they are 64-bit. Weird that you don't have them at all.

Post

Indeed odd.
This Mac still has Cubase 6-9 installed and indeed I don't have those plugins.
That is my default location for VST's in PC (where I use Nuendo), so other applications other than Cubase 9 could have installed them there.

rsp
You do not have the required permissions to view the files attached to this post.
sound sculptist

Post Reply

Return to “Hosts & Applications (Sequencers, DAWs, Audio Editors, etc.)”