Things I hate about... - Cubase 7

[mkdr]

Caveat: asio guard missing and phantom notes bug, no asio guard on multi out instruments.

Small correction; ASIO Guard does work on Multi Out instruments.
It doesn't work on Multi In instruments (many input midi streams).

[ObsoleteAcc99]

[DELETED]

[Compyfox]

IF one is using a 32 bit host its best to use it in a 64 bit OS. Of one has access to a 64 bit host and is happy with what plugins they have in 64 bit then its best to use the 64 bit host, of course. I was simply saying there's no benefit (only even more memory restrictions) to using a 32 bit host in a 32 bit OS. Many call the 32 host in 64 OS the happy medium compromise, as you can use all your plugins natively and in many cases have enough ram for projects "approx 3.5 gb" real world ram vs 1.5 to 2 in a 32 bit OS.

In most cases, that is working if I don't use a lot of samples/VSTi or RAM hungry plugins. So far I didn't reach 3GB with the Cubase7.exe


But what does that help me, if the 32bit version actually runs just as sluggish (if not worse) than the x64 version, and Steinberg gives a royal F about actually fixing bugs. Including both our findings!


It can't be that you constantly have to run at 1024 samples as buffer in order to even work somewhat stable and with enough headroom. On either x86 or x64. This is nonsense, and realtime usage barely possible. Especially on high class systems like RME.


As you wrote earlier, this is unacceptable and needs to be fixed instantly. Then again, Cubase 7 is out for over a year now, and the issues don't get better, they get worse.

I got word again yesterday from a "Junior Technical Support Representative" (I didn't make that up!), with the same touch of arrogance as the early answer to my bugreports since 7.03. That they can not help me, or can tell me when updates are due (which is somewhat logical), when certain things might be fixed, they also still can't point out what's wrong with my rig other than "reinstall, use x64!". Which also clearly contradicts with what was written at the Steinberg boards that Nuendo 6.07 is pretty much done already, but certain bugfixes/improvements didn't make it for this version. And the most recent post by GN regarding the funked up CoreAudio2ASIO engine on Mac, there I still think that this is all related!


We users are intentionally left in the dark, don't speak, don't tell, no harm. It's like a big scary monster in the middle of the room, but nobody dares to take a closer look at it if it's just there to ask for cookies!


This, is a big issue.
One year of "nothing" compared to Ableton Live. And I currently really expect the worst by end of the year (paid update).


Steinberg support is definitely sub-par, with the one rare exception I had contact with (not anymore it seems!) a couple of weeks back.

If I had the nerve, and the funds, I'd travel over to Hamburg, knock at the company doors of Steinberg and ask for a solution in person! And I won't go away until I spoke with the CEO. Because critism is obviously not(!) forwarded to the higher ranks.

And we have to admit, the user critism (not only mine alone, just see what's going on at the Steinberg boards or GearSlutz) is currently more than devastating.

[mkdr]

OK but usually when use a MULTi i am assigning a different OUT per midi channel. This is what i meant.

We should've read your mind


Anyhow. You actually can run a Multi with different Midi channels and different Audio outputs and still make it work with ASIO Guard. Here's how to do it:



How to:
1. Load a plugin in the vst rack
2. Load instruments in the plugin on different channels (+with different outputs)
3. Make a track to send midi to the plugin and change the channel to "Any"
4. Record notes on different channels to the same track
or create lanes with different channel notes on them (like on the picture)

This way you are using only one "midi source" and ASIO Guard works flawlessly.
You can also convert your old projects easily to this by simply opening up lanes on a track that is sending to channel "any" on the multi-timbral plugin, and drag and drop your earlier track midi's to the lanes(and possibly change the channel info of the notes). Just make sure no other track is sending midi to it or ASIO Guard won't work.

It's not perfect.. but works.
Bitch Steinberg to fix it if you have the time..

[Painmooser]

On my end a 32bit Cubase on 64bit WIn8 has more Processing /Asio/Power than a 64bit Cubase on 64bit WIn8


http://abload.de/img/unbenanntmyqoz.jpg

Stock plugs and ozone (64bit of course) nad massive 64bit of course

And this is if I remember correctly expected behaviour with other users aswell...

heres why:

"While x64 architecture has a few more registers which allows easier optimizations, this is often counteracted by the fact pointers are now larger and using any structures with pointers results in a higher memory traffic."

64bit has still a bit less power than 32bit.. It handles larger addresses yes - but if not needed.. then maybe better stay in 32bit.

and i dont only believe the asio meters - i could add 1 more CPU function inside ozone in 32bit till it started crackling. 64bit version crackled earlier. so 1 less function - anyway its not a big diff as I stated earlier. but if youre a happy32bit man why dont stay?

[HydrogenHuman]

I seem to recall reading somewhere that while the Performance Meter depends on the CPU, it also depends on the Audio Interface you are using.

I use the 64-bit version of Cubase 7 and I get all kinds of weird "spikes" on the performance meter, but then it goes back down.

I also get a weird issue where if I try to change a parameter while playing a note, like cutoff for example, I get a crackling noise and Cubase 7 starts to stutter.

It doesn't happen often, but it's a weird issue.

For reference I'm using a Scarlett 2i2 audio interface.

[mkdr]

On my end a 32bit Cubase on 64bit WIn8 has more Processing /Asio/Power than a 64bit Cubase on 64bit WIn8


http://abload.de/img/unbenanntmyqoz.jpg

Stock plugs and ozone (64bit of course) nad massive 64bit of course

And this is if I remember correctly expected behaviour with other users aswell...

heres why:

"While x64 architecture has a few more registers which allows easier optimizations, this is often counteracted by the fact pointers are now larger and using any structures with pointers results in a higher memory traffic."

64bit has still a bit less power than 32bit.. It handles larger addresses yes - but if not needed.. then maybe better stay in 32bit.

and i dont only believe the asio meters - i could add 1 more CPU function inside ozone in 32bit till it started crackling. 64bit version crackled earlier. so 1 less function - anyway its not a big diff as I stated earlier. but if youre a happy32bit man why dont stay?

Maybe that is the situation with slower memory.. dunno. It behaves quite the opposite over here. Could you run the Reaper test i posted earlier? I'd love to know if that's behaving similarly. Would be cool to get to the bottom of this.

Also, could you post your system specs(cpu/chipset/memory/soundcard&buffer).
I'm running an AMD FX8350/AMD970/8GB(1600-DDR3)/PCI RME Multiface @32 buffer.



Oh, and this is the way it behaves on my other two computers too. Seems odd.
Shame i can't run a test on Cubase just now...

[faun2500]

Just been demoing cubase 7 today. What a joke! lol Can't even right-click to remove an insert.

[no_barcode]

Just been demoing cubase 7 today. What a joke! lol Can't even right-click to remove an insert.

You could left-click the effect selector and choose "no effect" which is always at the top of the list. Same number of finger/hand movements. I agree it's odd that it's not in the insert's right-click context menu, but it's not exactly a show-stopper either.

[zvenx]

Just been demoing cubase 7 today. What a joke! lol Can't even right-click to remove an insert.

or you can left click and hold and drag the insert plugin off the rack.

rsp

[CableChannel]

Just been demoing cubase 7 today. What a joke! lol Can't even right-click to remove an insert.

You could left-click the effect selector and choose "no effect" which is always at the top of the list. Same number of finger/hand movements. I agree it's odd that it's not in the insert's right-click context menu, but it's not exactly a show-stopper either.

I don't agree. It is totally tedious to scroll up the whole plug list to remove a damn plug. This is ridiculous.

The dragging to nowhere is quicker, but Cubase asks for each session if you really wanna do that. The setting is not persisted on Windows.

[no_barcode]

Just been demoing cubase 7 today. What a joke! lol Can't even right-click to remove an insert.

You could left-click the effect selector and choose "no effect" which is always at the top of the list. Same number of finger/hand movements. I agree it's odd that it's not in the insert's right-click context menu, but it's not exactly a show-stopper either.

I don't agree. It is totally tedious to scroll up the whole plug list to remove a damn plug. This is ridiculous.

The dragging to nowhere is quicker, but Cubase asks for each session if you really wanna do that. The setting is not persisted on Windows.

You could just click in the top corner of the scrollbar and it'll page up pretty quickly. Or just click the insert and hit the delete or backspace keys if you don't mind getting the keyboard involved.

Not sure why I'm trying to solve these issues. I guess if your workflow involves you spending a great deal of time deleting insert effects then this is certainly a major drawback.

[CableChannel]

Clicking on the insert and hitting delete was my way of choice in 7.0.5., but it doesn't work anymore in 7.0.6. because once you click on an insert, the GUI shows up and keyboard focus is in the plugin window.

Really, the insert handling and all the changes back and forth made by Steinberg remind me of a blind man poking around with his stick to find his way (no offense to the blind man!)

[no_barcode]

Clicking on the insert and hitting delete was my way of choice in 7.0.5., but it doesn't work anymore in 7.0.6. because once you click on an insert, the GUI shows up and keyboard focus is in the plugin window.

Really, the insert handling and all the changes back and forth made by Steinberg remind me of a blind man poking around with his stick to find his way (no offense to the blind man!)

Well, now I'm actually starting to get irritated with it. You could click the bypass/power button on the insert (since you're deleting it anyway) to select it, and then hit the delete key.

[SODDI]

Clicking on the insert and hitting delete was my way of choice in 7.0.5., but it doesn't work anymore in 7.0.6. because once you click on an insert, the GUI shows up and keyboard focus is in the plugin window.

Really, the insert handling and all the changes back and forth made by Steinberg remind me of a blind man poking around with his stick to find his way (no offense to the blind man!)

Well, now I'm actually starting to get irritated with it. You could click the bypass/power button on the insert (since you're deleting it anyway) to select it, and then hit the delete key.

It's just a clumsy, ill thought-out thing that gets in the way as often as not.

I have a hard time finding that "sweet spot" where you can click to open the FX edit window. Like I said, poorly thought-out.