Things I hate about... - Cubase 7

[BERFAB]

I've never had a problem updating Cubase since the SX days...until now that is. For some reason, C 7.0.2 doesn't play nice with Kontakt 5. K5 is the only plug I have this problem with, but it's a biggie: intermittent usage spikes. Makes Kontakt all but unusable. And, because Kontakt powers at least half of the instruments I really rely on, it's crippling.

Strangely, no other plug has this problem that I can tell. And, I don't have any problems with any plugs in C 6.5 which I also (thankfully) still have on my machine.

I'm running the x64 version of both on a PC. It occurs to me that I should test C 7.02 x32 to see if the problem exists there. I've seen a few people post with the same issue with Kontakt, but not enough to indicate that it's a widespread problem, which really drives me crazy because it lessens the chances of a quick fix.

FWIW, Steinberg has been responsive, but the problem is not yet solved.

Cheers
-B

[Amon1973]

@ AstralExistence: You should really try and contact support.

You can have your issue looked into, if it cannot be solved in some e-mail exchanges, it will be forwarded in order to be solved. If it cannot, the source of the issue can be spotted and you'll know how to proceed.
Also, politely ask to test if a previous version runs better on your system because you have problems with 7, will most probably lead to a positive reply, as this could also help them with finding the source of the issue.

Many prefer to complain (in some cases wreck havoc) on a forum, but directly contacting a company is the way to go. They know how to help, how to put you in the right direction and are interested in knowing in which situations problems occur. As pointed out by others, it is impossible to test on every configuration out there, but if system-specific issues can be addressed without breaking the software on a larger number of machine, they most likely will.
Remember that although test are made on an as-large-as-possible number of configurations, when the product hits the market the combination of components is much larger - because beta-testers and insiders usually have tuned machines with carefully chosen components which reduce the incidence of system specific issues, leaving just some room for peculiar software configurations (as an example, most professionals use Gigabyte and Asus MB, leaving out a number of possible configurations) and because they are not going to install games and every dubious kind of software consumer computers have installed.

Just my 2c.

[BERFAB]

I keep reading the expression and it just doesn't compute. Cubase, "industry standard" - really?

If you go back a few years and read the manuals for the gear in the original Komplete package, among others, you will see that much of the code was specifically designed with Cubase compatibility in mind. Much of this, of course, has to do with the Steinberg vst protocol, which IS the industry standard (or is at least AN industry standard). Times have changed, but as far as plugs are concerned, vst has held it's own.

[Amon1973]

f the code was specifically designed with Cubase compatibility in mind. Much of this, of course, has to do with the Steinberg vst protocol, which IS the industry standard (or is at least AN industry standard).

I'd say the industry standard on Windows

[Suspended In Dusk]

For VST, agreed that it is probably as close to a standard as we've seen - it's the most widely supported. But then, we're talking about a different industry - the music software industry.

My understanding of industry standard in the previous post was - recording/music production industry.

[Amon1973]

For VST, agreed that it is probably as close to a standard as we've seen - it's the most widely supported. But then, we're talking about a different industry - the music software industry.

My understanding of industry standard in the previous post was - recording/music production industry.

Difficult to talk about industry standards, agreed - I still think Pro Tools was cosidered as such only because of the fancy control surfaces and the cost of HD-stuff... you know, it's expensive, thus used by big studios recording big artists...it must be good. But Cubase is one of the most wide-spread DAWs for sure.

[AstralExistence]

f the code was specifically designed with Cubase compatibility in mind. Much of this, of course, has to do with the Steinberg vst protocol, which IS the industry standard (or is at least AN industry standard).

I'd say the industry standard on Windows

yes, thats what i meant

[LawrenceF]

There is only real industry standard. PT.

(...runs and hides like Salmon Rushdie and waits for an ironic and clever PT quip from Roscoe's best friend Dan ... )

[jancivil]

ok so, if it is true that absynth is a resource hog, i also have padshop pro. is padshop pro also a resource hog? considering its a vst3 which shuts off when not being used, is this the better option in terms of less cpu intensive pad/atmo plugin? better meaning, less cpu intensive then absynth?

well on paper it sure ought to be. not everything in Absynth is equal however. the thing that requires so many cycles for me has been long envelopes, the things I'm interested in creating with it typically 'evolve'.

software interacting together is known as a sandbox 'who's not playing nice'... some combinations of things are not happy together. for me, I had horrendous problems introducing Amplitube 3 into my system, which isn't true for most people.

[Suspended In Dusk]

There is only real industry standard. PT.

(...runs and hides like Salmon Rushdie and waits for an ironic and clever PT quip from Roscoe's best friend Dan ... )

Well... Let's put it this way.

Logic is my main DAW, for many reasons, and also happens to be the most commonly used in my immediate professional entourage (along with Pro Tools).

Cubase I bought because I liked to mess w/ it every now and then. I know there are legions of users out there, but I know none of them in real life. I can't remember the last time I've actually heard the sentence "I use Cubase". I'm sure the situation is different in Europe.

Pro Tools I bought for compatibility reasons. Because it is the most widely used.

You can pick, say, any 20 studios in the US and pay them a visit tomorrow with a project file - I assure you that your best bet is to have it saved as a Pro Tools project, or then to have stems.

That's what industry standard (commonly agreed upon, most commonly used, default) is. Just like Windows is the standard OS on PC, as nice and even as superior as Linux may be.

[Compyfox]

I swear, when this mastering job I'm currently handling is over, I throw Steinberg a mail.


I found TONS of other bugs. And they're all related to the mixing console, the host itself, and using a Mackie Baby HUI like the BCF2000.



First and foremost, I found the "listen" channel. Actually, this was cleverly solved with the "Control Room" environment. Though you have to know, that the environment kicks in between Insert 6 and 7 of the Summing Bus. I don't know why, but putting anything "post fader" on the summing bus, while having IKM ARC on the Control Room for the speakers, it funks with the readouts of meters and stuff.


Speaking of which...
The longer I use Cubase 7, the more iffy the control behavior. Sometimes I can like double click 20 times on a darn insert, and it's not popping up.

In other times, on reloading a project, the Mixing Console adds a pre-filter of about -2,x dB on the summing bus(!!!). And on even different times, my racks vanish. Sometimes the inserts, sometimes the EQ, sometimes even the already preset(!!!) notepad section and the faders are all squashed. Wonderful.



But let's focus on HUI devices to control Cubase.
Integration is like you're used to. At least for this particular device (I only use the BCF2000 in Mackie Baby HUI mode to control the faders, solo/mute/panning and playback/stop).

But, apparently the mix console is funking around with everything. Or, the remote control doesn't read "what is accessable" on the mix console (like in earlier Cubase version), but everything that can be seen in the arranger.

ARG! Big faux pas!


Example in Cubase 6:
I turn off all MIDI channels and Inputs. My BCF then only recognizes WAV tracks, Instrument channels, Groups and FX.

Example in Cubase 7:
I turn off all MIDI channels and Inputs. The BCF ignores what I setup in the Mix Console and rather goes by what's "active" in the Arranger. And since I can't hide MIDI channels there, I need to skip through tons of pages to reach the Instrument channels. WTF?!


I think I know where Steinberg is Aiming at:
"*takes deep breath* Duuuuuude! I was like... what do you say if we drop the MIDI channel, since we don't need it anymore?! I mean... *takes another deep breath* duuuuude... who is still using... like... hardware?!".



Face... PLANT! Because a Facepalm can't describe enough what is wrong in this case.


Oh and btw... Turning off the HUB does not mean that the old "Project Splash screen" shows up on initial load. Only if you say "new project".



There are so many things that are wrong with Cubase, it's not even funny. The sad thing is... the developers don't even listen, or respond to FRs.

For example:
I have certain FRs for IKM plugins - wrote them several times - no response. Musiclab, I lost count how many times I wrote them. Slate Digital at least listens and then weights in what's good and not.

But I always talked to a wall with Steinberg.


I mean, I wrote them several times by now that Wavelab could be ported into "modern ages" with 96kHz/32bit audio montages for HD Audio. It forces(!) you to go 44kHz because it can only do CD montages, everything else "might" count as Podcast. That thing costs a sh*tton of money, and now it's collecting dust on my hardware.

Why? Because I work FASTER in Cubase in terms of mastering in HD Audio!




But only if I find that darn "channel freeze" button. And where the heck can I trigger the VSTi from the opened channel strip?! The funk?!


ARG! *smacks a virtual stick on Cubase 7*






Else, it's cool...
Just a couple of VST plugins don't work anymore. Like... TAL Dub-2 (sad), and Brainworx Plugins needed to be updated to the "Plugin Alliance" version. At least on my end.

But so far, no crashes. Just... annoying bugs on the verge to show-stoppers.

[ericj23]

I am pretty positive I have done audio montages in Wavelab at 96 khz in order to make a DVD-a, but sold Wavelab a while ago as I just wasn't using it, so all apologies if I have that wrong.

Your issue about the channels is being mentioned at Cubase.net, so hopefully 7.04 will fix it. I hope the pain of 7.0x will help Steinberg get their heads around the graphical problems that a scalable docked interface will have. Alas if that is coming it is going to be a paid upgrade.

Ho hum

[Compyfox]

The question is, when is the update due?

The next fair is "Musikmesse", so I hope by then. This is not a drastic showstopper, but it is one nonetheless.


Cubase 7 is by far the most buggy host out of Steinberg's range.



And regarding 96kHz Montages - WL dropped DVD-A montages (and the likes) with WL7. It pretty much dumbed down to stereo, surround, podcast and CD montages again.

Or I'm just too stupid for their hosts. Whichever suits this issue best.

[ericj23]

The question is, when is the update due?

The next fair is "Musikmesse", so I hope by then. This is not a drastic showstopper, but it is one nonetheless.


Cubase 7 is by far the most buggy host out of Steinberg's range.



And regarding 96kHz Montages - WL dropped DVD-A montages (and the likes) with WL7. It pretty much dumbed down to stereo, surround, podcast and CD montages again.

Or I'm just too stupid for their hosts. Whichever suits this issue best.

Are you sure about that. Wavelab 7 was the one I had, or was it six where they added the sonnox plus? I seem to remember it was an ugly setup, but I am sure it could do 24/96 montage. Don't suppose it really matters but it bugs me when my memory is off!

[lotus2035]

7.0.3 seems ok for me, no problems. I'm in the process of switching from 6.5.
It seems steiny are paying attention and moving ahead with updates. Halion 4 has some problems too but an update is on the way.

I think Steinberg should have waited longer before first release. 7.0.0. was a mess.