Things I hate about... - Cubase 7

[arkmabat]

And the "always on top" thing is a major showstopper for me.

I don't have Cubase but this app is wonderful at doing what it does:

http://www.pcworld.com/article/218511/Windows.html

It simply lets you choose if a window is "normal" or "always on top", which is great for anything from playing a background movie to keeping a synth's gui from disappearing. I'm guessing it works both ways. Does that help at all? Like I said, I don't have Cubase.

Edit: It can change windows to normal that are started with the "always on top" thing on. It even works with the Windows 7 Task Manager!

[Compyfox]

Aparently, with 7.06 the "Always on Top" bug worsened.

On a single screen, if you have several windows marked as "always on top" and you have both the arranger and the mixer overlapping, the same issues happen as with having the mixer in fullscreen.

Wow, don't even know what to say about that(!).

[ObsoleteAcc99]

[DELETED]

[SJ_Digriz]

Wow, don't even know what to say about that(!).

I do, it f'n blows monkey nuts.

[Matsun]

Hello,
Initially, I'm sorry for not reading all the posts by heart.
I had been Ableton user since like ever and a month ago I decided to switch to Cubase 7.

I hoped to be able to handle big orchestral templates along with video tracks, but all I have is actually no more that 10 instruments (yes that's it for i7, 16gbs, ssd, rme soundcard).

For a test I've decided to rewrite a project from Ableton to new Cubase (about 30 tracks). All went ok, until I started tweaking automation...
my daw cpu usage meters are red all the time!

I've read on several forums and it's a common problem, which...
makes this daw TOTALLY UNUSABLE!

[Compyfox]

Now well us you're using RME/Maudio or UAD with most recent drivers, and you pretty much ran into the exact same issues as TheoM and I are describing.


If you bought Cubase, get in touch with the support, send some friendly greetings by "Studio Compyfox" (ASIO Guard bug!!!) and ask them to fix your issues ASAP, or ask for a refund.



EDIT:
Scratch the last part... I'll get in touch with Steinberg anyway by next week (again!). But I ask them to call me(!), cause I'm definitely not calling them for 1EUR/minute.

I paid them enough with my money and wasted time already. It's their move now. This isn't a pr0n line.

[Matsun]

I like you being so active here!

I hope they are going to fix this soon...
However, having some programming history - the memory handling problems were always the worst to solve

[SODDI]

I like you being so active here!

I hope they are going to fix this soon...
However, having some programming history - the memory handling problems were always the worst to solve

It seems like a lot of of the problems are with the audio handling - with ASIO, which is Steinberg's patented baby.

If they went into the Cubase 7 development process without THAT locked down then there is no excusing them.

[Freaqpeak]

I agree the insert handling is a joke. If a GUI designer was involved with that I would like to see his diploma.
Insert handling has to be improved. But otherwise the new mixer is not too bad after all, my 2 cents.

There is a poll over at the Steinberg-forum about this:

http://www.steinberg.net/forums/viewtop ... 81&t=49861

[Compyfox]

I kind of feel hurt now, because I filed a FR regarding the Insert Handling in the FR thread, which showed how it's working in Logic, and how it could work with Cubase.

NO INTEREST AT ALL!

And this poll, well... people can ask as much as they want, Steinberg won't do it. Even if the feedback is devastating.

[CableChannel]

Yeah that is my experience, too, the Steinberg Forum oftentimes gives a damn. I see so many threads there, including mine, that hardly get any answer.

[BERFAB]

This might already exist, but I really wish there was a way to organize a one screen GUI that included the mixer (or a cut-down version of it), and a dedicated location for at least one .vsti/.vst plug.

That way you could tinker with the tracks, read the mixer and fiddle with an effect insert or two without having to click all over the place.

I know I can currently pile all these things onto one screen and resize them, but it would be nice to have some template that 'locked in' this stuff so you didn't have to recreate the wheel each time.

Cheers
-B

[mkdr]

This might already exist, but I really wish there was a way to organize a one screen GUI that included the mixer (or a cut-down version of it), and a dedicated location for at least one .vsti/.vst plug.

That way you could tinker with the tracks, read the mixer and fiddle with an effect insert or two without having to click all over the place.

I know I can currently pile all these things onto one screen and resize them, but it would be nice to have some template that 'locked in' this stuff so you didn't have to recreate the wheel each time.

Cheers
-B

I usually just switch between Workspaces. Quick and painless..

[Freaqpeak]

Seems like Steinberg changed voting options on that topic so you have to re-vote.

http://www.steinberg.net/forums/viewtop ... 82&t=49861

[Compyfox]

This post is not to fuel any more flames - I think I made my point pretty clear. It's just to show you with what I have to deal every day while working with C7. I just forwarded this to Steinberg as well.

And yes, this is ridiculus... unfortunately...

C7.06 on i7 920 with CWItec TX16Wx - ASIO load beyond 25%!
(sorry, large image, 780kb, 2x1680x1050)


This is Cubase 7.06, 32bit version, Cubase.exe uses 580MB RAM
I am still on an OC'd i7 920, 3,2GHz, 6GB RAM, Win7 x64 SP1

ASIO Guard is on, VSTi's are automatically "Guard off"
Guard being on or off shows no difference

CWITec TX16x is the latest version (snagged off of their page today), 32bit
I access 3 SF2's, the good old Maestro Drumkits, together 140MB samples
No modulation or FX inside TX16Wx (it's the free version)
No Insert Effects

The ASIO load is average about 20%, peaking way above 25%. And that's one VSTi alone!

C7 x64 version (both host and VSTi) gives 5% performance boost. No difference with sampling puffer (tried from 64, which showed 35% ASIO load - to 2048, which showed roughly 18%). RME Digiface, driver v3.36, firmware 20.



Now imagine using additional FX or VSTi.

This... shouldn't happen!
And I'm still being put on hold regarding the ASIO engine issues.



Seriously - as of this moment, stay the hell away from C7, folks. Do NOT update or think of updating and holding back until C7.5. Wait at least until C8. It's not(!) worth the trouble as of this moment.

Let us users handle the drama - you can only benefit from that.
Unfortunately sad but fair warning.