Things I hate about... - Cubase 7

[Compyfox]

See if you had read though the posts properly you would have seen that I mentioned 7.0.3. on the 30th.
You even responded to the 2nd part of the same post!

You mentioned something about .0.4, not .0.3 actually. So I thought that there is an update due, not out already.

In any case 7.0.3. has a long list of bug fixes included. Check it out dude.

I did check out the list, and 99% of my issues were not(!) adressed. So my support email is still valid. And should I get an answer by Steinberg "install the latest version and see what's up", they will get the answer "issues still exist".


There is nothing about proper color coding, nothing about remote controls, nothing about crazy clicking behavior of the mix console, the "Always on Top" bug was not adressed.

There was however something changed in terms of looks if a plugin is active or not. But then again, it was pretty understandable already. Still, no changes in terms of coloring the console.



So all this is, is just a maintenance update for stuff I did not encounter. Now I have to sit down and wait what the Borz will say to my mail. And maybe even other mails with similar issues.

But we users are usually ignored, as long as there are people saying "i don't have a problem with it, you're just too stupid for Cubase - use their official hardware with it".

Oooooh-kaaaaaay~!

[andrew71]

7.0.3 is very unstable for me. Quite a few plugins caused it to crash during the initial scan and then Alchemy's preset update scan caused it to crash too. I had to go back to 6.5 to get Alchemy to complete its preset scan.

[cubic13]

Which 4 RCs are listed?
4 is very meager in deed...!

Here they are (checked again with the recent Cubase 7.0.3 version) :

- Yamahe NUAGE
- System 5-MC (Euphonix)
- Artist Series (Avid)
- WK-Audio ID

And sorry for the naming mistake : insted of the 'Generic Remote Editor' it's actually called the 'Remote Control Editor', but the issues are the same : basically, you can't use it if you don't have one of these, which are clearly out of my financial ability... It also means that, even if you have defined, say, two generic remote devices as I did, you are not able to use RCE for them.

So yes, for me, as well as for the great majority of Cubase users, this one is useless...

[cubic13]

7.0.3 is very unstable for me. Quite a few plugins caused it to crash during the initial scan and then Alchemy's preset update scan caused it to crash too. I had to go back to 6.5 to get Alchemy to complete its preset scan.

To be honest again, C7 is stable here. As I use Alchemy, I can say that it works without issue within Cubase at its 1.50.1 / 1.55.0 64 bits versions.

Just a suggestion. Try to remove the following files from your preferences folder :

- Vst2xBlacklist Cubase.xml
- Vst2xPlugins Cubase.xml
- VstPlugInfoV2.xml

Then relaunch Cubase.

[Compyfox]

Aaaand... I found yet another thing.


Fire up Wavelab BEFORE Cubase 7. And if Wavelab searches for new plugins (even though it did already), Cubase does so as well.

It just took that darn host 10 minutes(!) to go through all my plugins! 10 Minutes, for only like 50 plugins from different suites. And no, it was not the the infamous DST "rescan feature".


I don't think tha I will update to .0.3 (neither will I with Wavelab 7 to a higher version - the longer I use it, the more features I find that were dropped from earlier versions)

Cubase 7 is acting REALLY strange. So I don't know what crap Steinberg pulled, but this is not(!) what I am used to from my every-day-use host.


Might as well learn a new host alltogether.

[cubic13]

Aaaand... I found yet another thing.


Fire up Wavelab BEFORE Cubase 7. And if Wavelab searches for new plugins (even though it did already), Cubase does so as well.

It just took that darn host 10 minutes(!) to go through all my plugins! 10 Minutes, for only like 50 plugins from different suites. And no, it was not the the infamous DST "rescan feature".


I don't think tha I will update to .0.3 (neither will I with Wavelab 7 to a higher version - the longer I use it, the more features I find that were dropped from earlier versions)

Cubase 7 is acting REALLY strange. So I don't know what crap Steinberg pulled, but this is not(!) what I am used to from my every-day-use host.


Might as well learn a new host alltogether.

Cubase (even in its 5.1.1 and 6.5.4 versions) is still for me the best host available. What is happening with 7.0.x is an obvious failure but well... I'm still as happy as before to use the previous versions.

And I will certainly not try again another host (already tried to get something as efficient with Sonar, Samplitude, Reaper, Podium...) as, for different reasons, it always ended up by a failure. Maybe I have a way to apprehend and use a host in a special way but, after all these years, Cubase is still the only one that suits perfectly my way of doing.

Now, to each his own...

[kelvyn]

Aaaand... I found yet another thing.


Fire up Wavelab BEFORE Cubase 7. And if Wavelab searches for new plugins (even though it did already), Cubase does so as well.

It just took that darn host 10 minutes(!) to go through all my plugins! 10 Minutes, for only like 50 plugins from different suites. And no, it was not the the infamous DST "rescan feature".


I don't think tha I will update to .0.3 (neither will I with Wavelab 7 to a higher version - the longer I use it, the more features I find that were dropped from earlier versions)

Cubase 7 is acting REALLY strange. So I don't know what crap Steinberg pulled, but this is not(!) what I am used to from my every-day-use host.


Might as well learn a new host alltogether.

.... Logic?

[Compyfox]

If I had a Mac, and Logic 10 would be out, I might consider it. On top of what I already know.

BUT... I actually have Reaper or Studio ONE in mind. Then again, Reaper is in constant motion, and I hear as much horror stories about Studio ONE, as I hear about Steinberg Cubase.


If you forget all that mojo stuff like new Mix Console, or that you ever used a remote control like the BCF/BCR, but rather stick to "Steinberg only hardware" - maybe you have the best experience. But currently, this host is getting the finger from me.

Sad thing is, now that I updated, I need to work with it. Because Cubase 6 can't load Cubase 7 projects, and I have two jobs currently that are already in native Cubase 7 format.



I also just jumped a bit through the Steinberg boards - the rage over there is massive to a certain extend. Last time I read something similar, was taking a dive towards Ardur/Harrison MixBus.

I mean, WTF seriously?! Can't there be any host these days that is bug free on launch, or even after updates? No, before all bugs are fixed, you're forced to go "paid update" to the next major version.


Maybe I should do it like back in the days with Cubase VST5 and my jump to SX3. Almost 7 years without(!) updating, and I was fine. But these days, you can't do that either. Update a VSTi, and suddenly it's not working in your old host anymore. Same sh*t all over.


Happy easter, Steinberg. You sure hid the easter eggs good this time.

[cubic13]

BUT... I actually have Reaper or Studio ONE in mind. Then again, Reaper is in constant motion, and I hear as much horror stories about Studio ONE, as I hear about Steinberg Cubase.

Didn't try Studio One, but looking at its user manual, I know that I would miss too much things, compared to Cubase. And about Reaper : setting up multi-outputs VSTis is a nightmare, as well as trying to get the equivalent of what the Cubase musical/linear timebase switch allows you.

Sad thing is, now that I updated, I need to work with it. Because Cubase 6 can't load Cubase 7 projects, and I have two jobs currently that are already in native Cubase 7 format.

Are you sure of this ? I think that I've read on Steiny forum that it is possible to do so. Suggestion : make copies of your ongoing projects folders and try to launch them with C6.5. Worth a check...

I mean, WTF seriously?! Can't there be any host these days that is bug free on launch, or even after updates? No, before all bugs are fixed, you're forced to go "paid update" to the next major version.

No, there is not, and I understand your anger ; I'm more or less in the same state, seeing the regressions since 6.5. My feeling is that there is a sort of panic in Steinberg headquarters, presently : already 3 updates since C7 release, last december. They are trying to fix the most obvious issues but the problem is that they made choices that they are unable to ensure : the first of them is launching C7 too quickly, the second is the MixConsole which obviously wasn't ready, the third is removing features without a second thought (see the .vmx dropped support and the 'Appearance/Work area' page, among others...).

And about the business model, which consist of launching paid update before fixing what is existing, well... I think it has always been more or less like this. Still waiting for C 6.5.5 final release, by the way...

[SJ_Digriz]

And about Reaper : setting up multi-outputs VSTis is a nightmare,

I'm no Reaper lover, but all I do is drag a multi out and it asks me if it wants me to create the outs. It does. Super simple. Plus, you can save the damn template so that once you get a complex routing done, you never have to do it again. Which kicks Cubases ass.

as well as trying to get the equivalent of what the Cubase musical/linear timebase switch allows you.

This is odd to me. Reaper devs seem indifferent to the various alignment needs for the modes. Including video sync. They are adding all kinds of video capability, but you can't align audio to frames. Makes no sense to me.

[cubic13]

I'm no Reaper lover, but all I do is drag a multi out and it asks me if it wants me to create the outs. It does. Super simple. Plus, you can save the damn template so that once you get a complex routing done, you never have to do it again. Which kicks Cubases ass.

Well.. improvements have been made since 3.x, then : happy for reaper users. I don't know if it kicks Cubases ass, presently, but what I remember is a several stages process, which always failed in the end.

But anyway, what keeps me from using Reaper, among other things, is the UI : for a specific track you don't even know if what you are dealing with is MIDI or Audio. You see the meters moving. Fine... Is it MIDI volume or audio level ? The kind of thing that prevents me considering Samplitude which has more or less the same layout.

But let's not start another Reaper debate. There have been enough here, I think...

[SJ_Digriz]

I don't know if it kicks Cubases ass

Just the saving of track presets. I do a lot of orchestration and large percussion ensemble type things that have very large multi-out maps with a shit load of articulations. They are a nightmare to handle in Cubase for new projects. They are super simple using the Reaper method. As painful as it is in Cubase, MIDI editing has to come a long way in Reaper before I'd even consider switching. The MIDI editors in cubase are $$$$$$$$

[Compyfox]

Are you sure of this ? I think that I've read on Steiny forum that it is possible to do so. Suggestion : make copies of your ongoing projects folders and try to launch them with C6.5. Worth a check...

I'm on 6.0. Never bothered to go 6.5.

And about the business model, which consist of launching paid update before fixing what is existing, well... I think it has always been more or less like this. Still waiting for C 6.5.5 final release, by the way...

I think this will never happen. Even if they promised. I remember similar promises with every version prior - it did not happen. So called "final versions" or "beta updates" introduced even more bugs.



I really ask myself, when can I get back the functionality I had with Cubase SX3 until Cubase 6... I guess that won't happen until 2015. Waste of money yet again.

Though I still have hopes for a 7.1 version, where we get back at least "some" functionality. But when will that happen? 2014? Yeah, being on a dry walk for 9 months until then at least, and then paying 50 quids for it for something that SHOULD HAVE been there in the first place?

Lost words, really.

[SJ_Digriz]

I really ask myself, when can I get back the functionality I had with Cubase SX3 until Cubase 6... I guess that won't happen until 2015. Waste of money yet again.

I'm still waiting for them to return functionality from VST/32 when they ripped all the MIDI studio support. Basically, it was the beginning of the bail on external MIDI support.

M-Points were better than the current method of warping.

You had independant, scaled region automation.

geez, I could go for an hour again.

[cubic13]

Just the saving of track presets. I do a lot of orchestration and large percussion ensemble type things that have very large multi-out maps with a shit load of articulations. They are a nightmare to handle in Cubase for new projects. They are super simple using the Reaper method. As painful as it is in Cubase, MIDI editing has to come a long way in Reaper before I'd even consider switching. The MIDI editors in cubase are $$$$$$$$

Here, you have a point : the vst/trackpresets are close to unusable in Cubase, especially for multi-outputs VSTis. And, actually, I don't use them. I'm sticking on what is the more efficient for recovering specific setings : the templates.

But there are so much things that makes Cubase valuable. Is there another host which could give me, in one package :

- The input tracks : perfect for applying, say, a guitar effect plug-in at it is recorded,
- The external instruments integration as VSTis,
- The score editor : it's not Sibelius but easily matches my need, mainly for training purpose,
- The input transformer : thanks to this one, among others, I am allowed to use my old Yamaha pedals with a full 0-127 MIDI CC values range,
- Already evoked, but still : the musical/linear timebase switch,
- The MIDI implementation,
- The complete sample editor,
- And finally, the ease of use : I've seen many complaints about it and I don't get it. For me, it is the more efficient UI available and this is why I am raging against C7 regressions.

Guess I forgot others...