Cubase 7.06 is out

[CableChannel]

For me the insert handling is not completely bad. I kinda like the invisible buttons. This saves space for displaying the name! But there sure are things that should be improved:

- the area where the invisible buttons show up (hoover zone) is way to small. It is way to tedious to get to see them and click them.

- it sucks that with narrow mixer channels, you must move your mouse from right to left to get the bypass button visible, because if you move left to right you get the select button of the neighbor slot.

- tooltip would be awesome that shows complete plugin and preset name!!

[Compyfox]

Again, Logic handled this GRACEFULLY, it's within the insert box. BUttons showing up on mouse over. Nothing invisible here, or crazy zones to click on.


This FR was filed like 5 times or so, with positive response, yet Steinberg gives a flying f*ck.

[Guillermo Navarrete]

Hello all,

I shouldn't have to do such a thing to run Cubase 7 in a a stable manner AT ALL.

I shouldn't have had to do 95% of the mucking around I've had to do with my computer system, sound card settings, physical and system MIDI set-up and Cubase settings. And compensating for your techs' bad advice.

An experienced Cubase user with an EXISTING Cubase set up should have been able to set up the Cubase 7 core installer, apply the current update, make a few minor adjustments and be good to go for good.

Instead I've spent as much time dicking around with Cubase 7's failings as actually working within it. This had made Cubase 7 A VERY BAD THING INDEED and a toxic working environment.

BTW, your fix doesn't work. I tried it. I need to manually toggle "run as administrator" to ensure that Cubase 7 shuts down on quit every time.

There is always some optimising that needs to be done on a DAW before it can run at its best.
That is why we have the Optimising Windows for DAW and Mac articles.
If you need to run as administrator it's because other components of your DAW require this.
Most of the time is due to the UAC of Windows, If you lower the security you shouldn't be bother by this anymore.
Also if the permanent set-up for admin rights is not working it means Windows is not doing what it should, as it is exactly the same as doing it manually, I have tested it many times on Windows 7 32 / 64 bit and Windows 8. And it runs as administrator.

Just like I need to make sure that my M-Audio keystation is on BEFORE starting Cubase if I want Cubase to recognise it as a MIDI device.

Most of the times that is normal: Turn computer ON, connect all the gear and make sure they are on, then open Cubase.
It depends on the drivers an the OS, exactly what version of Windows do you have installed?
I think there is something strange on the way windows is managing your MIDI devices... and could also be the cause of Cubase hanging.

When Cubase is about to close it sends a message to all the components of the DAW.- "I am going to close", and then it waits for a reply, when it receives the ok, it closes. But, if a component doesn't reply then it waits and waits, and eventually it just hangs.

That's a result of your tech's advice to pull my MOTU USB MIDI device and only use the Keystation's MIDI over USB functions. Screwed up my use of a second keyboard, too.

Maybe your chipset is sharing the ports somehow and do not have enough power to run all the MIDI devices....
Or you have duplicated MIDI ports, or two many emulated MIDI ports.
Unfortunately I do not know how your system is setup but there are many variables that need to be checked.

Hi I am really confused now. I am about to install cubase for the first time on my iMac, on the laptop its just the demo I had installed and when I got my license continued to use that, and its been fine. I've just upgraded every version as its come out.

But I am reading about this installing and uninstalling.. Which shouldn't be necessary.. The way my mind works is I install a program, then install updates as needed. That's it. If something goes wrong where I am advised to uninstall and kee my preferences if required (what a hassle) then reinstall, in my eyes that means the company has made faulty installers.

So now on my iMac I will put the discs in right, then let it do its little download of 500mb, then if that's not the very latest version it downloads, I will then need to do the 7.06 patch. I then would presume when 7.07 comes out, and so forth, I can just simply install ontop as needed. Are you saying that I will need to uninstall and do all this again to have a stable system when each update comes out?

No, on the mac you shouldn't have any problem.
Just install the software from the DVD or download the core installer, and install the latest 7.0.6 and keep updating as the patches are released.
We recommend to uninstall only if an issue arrises that can not be fixed by removing the preferences or starting Cubase in safe mode.

Thanks for your reply, but no matter what I do the main Midi menu function Logical Presets is greyed out, and it's never been greyed out by default before. I've even tried Edit Midi in Place in the Project window, I can select ten Midi events and a thousand notes and the menu function with all of it's sub-functions are still greyed out. I thought I would get it back with the .06 update but it's still like that in 64 bit. It's THERE in 32 bit. Now I'm wondering if I should re-download and re-install.

This might have to do with the folders for the presets.

First thing, with all installations always check that "install for all users" box. As I remember that's the way to go with Cubase installations.

Now you can try to fix the logic presets by moving them from "C:\Program Files\Steinberg\Cubase 7\Presets" to "C:\Users\%USERNAME%\AppData\Roaming\Steinberg\Cubase7_64\Presets".

Can Mr Navarrette confirm that this is the fix too? I'm not able to try it right now, but he says he's reading all the posts so maybe he can chime in on this problem with Logical Presets menu functions totally greyed out in .05 and .06 64 bit updates. But I WILL try this fix when I get to my computer in a couple of days. Thanks.

On what version of Cubase are you, Cubase 7?
On the full version there shouldn't be any problem, actually I only remember this happening in Cubase Artist 7 and Cubase Elements 7 the solution was as simple as clicking on the "Edit" menu of Cubase first, then:

-Select a MIDI part
-Go to MIDI > Logical presets.

And the presets should be there.

If that is not solving it, then make sure the folders have read and write permits.

Best regards,
GN

[fese]

For me the insert handling is not completely bad. I kinda like the invisible buttons. This saves space for displaying the name! But there sure are things that should be improved:

- the area where the invisible buttons show up (hoover zone) is way to small. It is way to tedious to get to see them and click them.

- it sucks that with narrow mixer channels, you must move your mouse from right to left to get the bypass button visible, because if you move left to right you get the select button of the neighbor slot.
!

But this is EXACTLY the problem of invisible buttons! You have to target sth with the mouse pointer that isn't there, you miss it, you have to correct your position and maybe again. Worst case, as you say, yout hit the neighbor button. Whereas with a visible (big enough) button you can move your mouse directly to the button. Simple eye-hand coordination. Invisible UI elements just don't help the user, but good UI design should exactly do that!
I don't want to rant here, but this is so plain obvious non-ergonomic that I really cannot believe this is considered "good", except by a designer on an ego trip or marketing people. Sorry, I just don't get it. I totally understand Compyfox here...

[standalone]

I've been trying to reproduce your issues locating and hitting the invisible buttons and I must be some kind of Formula 1 driver of the daw world because I don't find a single problem, no matter the size of the track.

Without being sarcastic, do you wear glasses? I do, maybe you should too. Or at least you need to check if you need new ones.

The other possibility is that your screen is smaller than mine (panoramic 23") and this makes some difference.

[SODDI]

There is always some optimising that needs to be done on a DAW before it can run at its best.
That is why we have the Optimising Windows for DAW and Mac articles.

So, not only do I have to optimize my system for running Cubase as I did last June, I also have to optimize it for running Cubase 7?

What part of the phrase "existing Cubase installation" is so hard to understand?

I have an existing Cubase 5.5 installation on the same computer that I have installed Cubase 7 on. C5.5 has run in an optimum fashion, C7.05 has been nothing but problems.

I'll repeat this, since it seems to be hard for you to understand: CUBASE 5.5.3 RUNS FINE.

A new installation of Wavelab Elements 8, installed on the same day as Cubase 7.05, runs as good as can be expected, being a down-featured version of earlier versions of this program. Native Instruments' Komplete 6 runs very well.

If you need to run as administrator it's because other components of your DAW require this.

No. It's because of the Steinberg clusterf**k chain of events that led up to needing to "run as administrator". And it's obvious you did not read what I wrote.

1. Cubase 5.5 runs well, low latency.
2. Install Cubase 7, apply 7.05 patch. Cubase 5.5 remains intact for reference.
3. Requirements for buffers/latency on C7.05 as high as 4 times that of C5.5.
4. Serious timing instability, both MIDI and audio. Well known "lazy initialization" endemic to many VST instruments (most sample-based). Bi-weekly crashes. However, Cubase does not hang on quit.
5. Three customer support requests, finally a phone call from Steinberg USA.
6. We run through my system, no serious tweaks needed, buffers OK ("gotta expect them to be larger", S'berg tech.)
7. STEINBERG TECH TELLS ME TO REMOVE MOTU MIDI DEVICE; TO INSTEAD USE M-AUDIO MIDI OVER USB. Says he'll call back in a day.
8. D/l and install M-Audio USB drivers, hook up Keystation.
9. MASSIVE MIDI timing errors, input MIDI notes delayed by one bar. Cubase does not hang on quit
10. Steinberg rep never calls back. Cubase does not hang on quit.
11. Try Cubase "system timestamp" (not in the manual) to stabilize MIDI.
12. "System timestamp" (not in the manual) works like a charm, BUT:
13. Cubase 7 hangs on quit.
14. Last ditch effort - run Cubase 7 as administrator. Success. No more hangs. MIDI notes spot on. Cubase 7 runs better than it has since installation.

If I were a betting man, I'd be willing to wager that the "hang on quit" phenomenon has something to to with the way "system timestamp" (not in the manual) works within Cubase.

But what do I know? I am only a lowly user who has successfully run Cubase since the Atari days. Something must be wrong with my chipset, huh?

[4damind]

7. STEINBERG TECH TELLS ME TO REMOVE MOTU MIDI DEVICE; TO INSTEAD USE M-AUDIO MIDI OVER USB. Says he'll call back in a day.
8. D/l and install M-Audio USB drivers, hook up Keystation.
9. MASSIVE MIDI timing errors, input MIDI notes delayed by one bar. Cubase does not hang on quit

Running as administrator and also "system timestamp" is IMO only a workaround for bad implemented drivers/plugins and M-Audio is well known to make a lot of problems and having a very, very bad midi performance.
I have no Motu but you will also find some comments about unstable drivers and problems with Motu (eg. on Gearslutz) so that some users don't recomment Motu.

I bought (after similar problems) a ESI Midi interface and don't use M-Audio for Midi directly. The M-Audio controller is connected to the ESI and I use a USB power supply so the M-Audio is not connected to the computer anymore.
I have excellent timings, don't need such settings with "system timestamp" and never run Cubase as administrator. No crashes, no hang on exit, nothing. Excellent and stable system...

After Steinberg fixed most of the bugs they often have with the first release, IMO 99% comes from not proper programmed hardware/drivers/plug-ins and maybe 1% are some bugs with Cubase.

[SODDI]

Running as administrator and also "system timestamp" is IMO only a workaround for bad implemented drivers/plugins...

I have admitted as much. I think I used the phrases "dumbass" and "improv" regarding these strictly personal fixes. I really wouldn't recommend them to anyone else. I shouldn't have to. But they worked.

Welcome to the Howard, Fine and Howard school of computer science.

and M-Audio is well known to make a lot of problems and having a very, very bad midi performance.

I never used the M-Audio's MIDI over USB interface before the Steinberg tech told me to 3 weeks ago. I tried a couple years ago, but their old Enigma software was crap for me and I went back to running the Keystation sraight MIDI through the MOTU.

I have no Motu but you will also find some comments about unstable drivers and problems with Motu (eg. on Gearslutz) so that some users don't recomment Motu.

I've run 2 MOTU devices on 3 computers for 12 years now, and I have experienced no problems whatsoever. Unless I was changing computers or mucking about with the USB ports, they existed as entirely transparent workhorses for me. Kept up with the drivers, no problems. Just solid. Until Cubase 7.

I bought (after similar problems) a ESI Midi interface and don't use M-Audio for Midi directly. The M-Audio controller is connected to the ESI and I use a USB power supply so the M-Audio is not connected to the computer anymore.
I have excellent timings, don't need such settings with "system timestamp" and never run Cubase as administrator. No crashes, no hang on exit, nothing. Excellent and stable system...

I just took a look at those again, and if I have to will definitely consider one on your recommendation. I can get one in here fast. (humor) I just never thought they were real MIDI interfaces because they're not black and wedge-shaped. Too little.

But again, the MOTU interface worked perfectly on Cubase 5.5.3 on the same computer, all of a sudden there are driver issues with Cubase 7.05? And it's the MOTU device's fault?

After Steinberg fixed most of the bugs they often have with the first release, IMO 99% comes from not proper programmed hardware/drivers/plug-ins and maybe 1% are some bugs with Cubase.

I don't think they've fixed the bugs. And I am loathe to install 7.06 after some of the fail screenshots I've seen here.

[ObsoleteAcc99]

[DELETED]

[ObsoleteAcc99]

[DELETED]

[ObsoleteAcc99]

[DELETED]

[CableChannel]

On my system I could be sailing along with maybe 50% asio meter, purring, no issue, then for absolutely no explainable reason the blue meter starts spiking like a rhythmic trance gate in 1/4 time. Once that starts nothing can stop it but pretty much disabling almost every single plug in in the project.

I had that too! Man, I didn't know anybody else experienced this. I have a lot of projects with pretty much VSTi only, and I have one project where I had 8 or 10 eguitar tracks with ampsim's loaded on each of them. This is the project where I got that "trance gate", and it always seemed to happen when I changed the project cursor position. I guess the managing of position pointers in wave file playback is buggy? Well the devs should find the bug.

[ObsoleteAcc99]

[DELETED]

[ZINO]

Hm... time for a 6.5.5 reinstallation it seems.

Theo, other than this how is the performance of 7.06 on Mountain Lion compared to 6.5.5 (if you ever used this version as well)?

[ObsoleteAcc99]

[DELETED]