Things I hate about... - Cubase 7

[vasilis_et.ma]

Where is the email of steinberg;s tech support?

i dont find it!plz help me

[CableChannel]

I think you can't email them directly. You need to login on the Steinberg website and generate a ticket there.

[Compyfox]

Since I wasted days on this:

I've seen exactly the opposite stated as a cure-all. "Let Windows choose what's best for my computer". Allegedly, (from a poster in the Cubase forums) modern machines do not need that tweak.

Barely any effect.

I dunno, I had it the other way, I'll try the "background services" tweak again. Seems like all I do is tweak shit for Cubase 7.05. ASIO buffers, Windows shit, MIDI settings...

Yes, this is pissing me off as well. You invest hours of tweaking, and nothing works compared to earlier versions. In my case, I turned off drivers, ports, did PCI latency checks, even used "windows found drivers" just to rule out that it's not driver hogs like NVidia!

So... stick to what's realy working and ignore the tweaking. Especially with modern rigs.

And some guy suggested that you only run Aero graphics on Windows.

I can somewhat confirm that certain graphic modes speed up things, but this has nothing to do with ASIO load. Again, I even used the standard Windows found drivers for my GPU. And things worked just as bad as before.

It's all hoodoo mumbo jumbo.

Sure is.



So again...
If you experience this problem... get in touch with the support through your user account. Ask for a remote session, show them the ASIO behavior. Especially if you reinstalled your rig just for testing.


Something is wrong since ASIO 2.3/Cubase 7.
We now have the chance to back that up, and get it fixed. Whenever that might be.

But if nobody does give any feedback, and may it only be small, or Steinberg saying "that's not related to that particular issue" - nothing is happening.

So speak up, don't let yourself be put off.

[SODDI]

So again...
If you experience this problem... get in touch with the support through your user account. Ask for a remote session, show them the ASIO behavior. Especially if you reinstalled your rig just for testing.


Something is wrong since ASIO 2.3/Cubase 7.
We now have the chance to back that up, and get it fixed. Whenever that might be.

But if nobody does give any feedback, and may it only be small, or Steinberg saying "that's not related to that particular issue" - nothing is happening.

So speak up, don't let yourself be put off.

The Steinberg techs (at least here in the U.S.) seem to be at as much of a loss for solutions as us lowly users. And they do not return phone calls.

All the company has to do is put up a stone wall of indifference to user problems; to supply updates that do not address major issues; to have technical support that seems to be stumbling around in the dark just as much as the user base; to pretend that everything is just hunky-dory in Cubase land, and everything will be just so.

From the responses of the "product specialist" here in KVR, to the notable lack of response on the Cubase forums and the sad state of update .06, I am firmly convinced that Steinberg/Yamaha is willing to lose 10-20% of their user base over this version of Cubase.

Why? Maybe 8.0 will see Cubase folded into Yamaha's product line; they're running a skeleton crew in Germany; and no one much cares what happens to Cubase 7 because they won't have a job in a year so why work hard to fix problems?

[D-Lay]

In my whole time , while i were useing Cubase 7 (about 1 year now) , He crashed only 1 time! Personally i think that Cubase 7 is really good if you learn how to use it right. The second thing is to have good PC/mac

[lotus2035]

Personally i think that Cubase 7 is really good if you learn how to use it right. The second thing is to have good PC/mac

MixControl is a joke no matter how good you are with Cubase or how good your computer is. Sure I can get used to it but you can say that about any music software no matter how badly designed.
It's easier for me to just stick with Cubase 6.5. Honestly I would rather use Cubase 5/4 or even SX3 than work with Mixcontrol. I hate it that much.
Although personally I will continue to use 6.5 for as long as I can, (it's probably the best DAW ever made) officially Cubase is dead for me.

Unless of course Steinberg do a u-turn on Mixcontrol which is highly unlikely.

[Compyfox]

Again, it's not about crashes, it's about instability of the host in general. Namely the ASIO system.


I think I'm the only persistent idiot in here to actually get Steinberg to react. What did I do different? Other than insisting on getting support?


Why shouldn't it work for the users shuffled over the rest of the world? The issues are staring into your face. We are not imagining things. Yet it's "non existant"?

Er... what?

[filtafreq]

the thing I hate about Cubase 7 is that .............. I LOVE IT SO MUCH
and my 25 year addiction carries on ........ Steinberg I love you xxxxxx

[Vintage73]

Am I still on someone's ignore list?

Look, ma! No Reaper in my signature!

[filtafreq]

kitty have you got fatter I swear you were only 2lb ?

[murnau]

Personally i think that Cubase 7 is really good if you learn how to use it right. The second thing is to have good PC/mac

MixControl is a joke no matter how good you are with Cubase or how good your computer is. Sure I can get used to it but you can say that about any music software no matter how badly designed.
It's easier for me to just stick with Cubase 6.5. Honestly I would rather use Cubase 5/4 or even SX3 than work with Mixcontrol. I hate it that much.
Although personally I will continue to use 6.5 for as long as I can, (it's probably the best DAW ever made) officially Cubase is dead for me.

Unless of course Steinberg do a u-turn on Mixcontrol which is highly unlikely.

yeah, here to. 6.5 till the end!

[xphen0m]

I have to play devil's advocate here. I don't see what's so horrible about MixConsole. I've used REAPER and Studio One, and I actually like MixConsole a little better than both. (Although, Studio One's mixer is quite great to me, too)

I've had some crashes here and there in C7, but no problems to the degree that others are facing. (I'm not saying they're not happening; I'm just saying that I haven't experienced a lot of these problems)

The only real thing that bugs me about Cubase 7 is that the ASIO meter reports higher usage than anything else. While I think the meter is pretty wrong, it's still pretty troublesome to see.

[vasilis_et.ma]

[SOLVED] Realtime meter spikes

Postby promotouk » Fri Apr 19, 2013 1:38 pm
Hi eveyone I know a lot of you are having this problem well today I sorted it out and it was simpler than I thought. It was right under my nose and I just did not see it.
I was scratching my head for weeks on WHY was the real time meter bouncing all the time. If you have an older version of Cubase sat on your system then the preference file from that is the issue. When you load 7 in it loads the older version preference file so if you are keeping an older version on your system you will have to move the old preference file to the desktop or if you have deleted the old version the preference file will still be sat in C drive under users your name then appdata roaming Steinberg delete cubase 7s preference file and re load 7 and you will find that the bouncing meter goes away totally. I have just done it about 10mins ago and NO MORE bouncing of the real time meter
No trashing the drive for me.
Big thanks to SB support and Creamware

IT works for me!:D

[SODDI]

The ASIO buffers for my machine needed to be set at least 3 to 4 times higher than they were set for Cubase 5.5.3. The higher the buffer size the lower the usage on the ASIO meter... but the higher the buffer size, the more unstable the timing and playability.

If I ran 1024 samples latency like Compyfox has been forced to (no offense to the Foxster, just an illustration) my soundcard would show a 23.2 msec latency and Cubase would report a 26.12 msec input latency and a 49.342 msec output latency. Yoiu can't tell me you wouldn't be able to perceive a 50 msec latency.

Unlike many of you, I actually trust the ASIO meter and the rest of Cubase's internal metrics. And that's what pisses me off. The more or less constant spikes, the spikes when sample-based instruments are loaded, the requirements for almost ridiculously high buffers... this means something. This is important.

Cubase tech's response (verbatim): "Well, you've got to expect that."

[Compyfox]

[SOLVED] Realtime meter spikes

Did never work for me.

Just fresh installed C7.06 (yes, actually did it). With 32bit and 64bit version side by side (that is possible, folks!).

Realtime meter spikes are still happening with third party plugins.

The ASIO buffers for my machine needed to be set at least 3 to 4 times higher than they were set for Cubase 5.5.3. The higher the buffer size the lower the usage on the ASIO meter... but the higher the buffer size, the more unstable the timing and playability.

Since I just made tests with the x64 version of C7.06, I can also confirm that the RAM usage is higher (about +500MB more from lowest buffer size, to highest). And depending on the used buffer size, chances are that the CPU fluctuates by 15% at maximum peak (Cubase7.exe)

Example:
256 samples = 28% CPUI peak
512 samples = 25% CPU peak
1024 samples = 22% CPU peak
2048 samples = 35% CPU peak
4096 samples = 21% CPU peak

I reported that to the tech support. Along with corresponding ASIO behavior.

If I ran 1024 samples latency like Compyfox has been forced to (no offense to the Foxster, just an illustration) my soundcard would show a 23.2 msec latency and Cubase would report a 26.12 msec input latency and a 49.342 msec output latency. Yoiu can't tell me you wouldn't be able to perceive a 50 msec latency.

50ms to 100ms in unacceptable to me. I'm used to 256 samples from Terratec days, and now I'm on RME. The fastest and most stable ASIO system on the market. And Cubase is forcing me to go up to 4k samples in order to use 24 channel with like 3x third party plugins per channel in realtime, without hitting 90% ASIO load.

That can't be right.

Unlike many of you, I actually trust the ASIO meter and the rest of Cubase's internal metrics. And that's what pisses me off. The more or less constant spikes, the spikes when sample-based instruments are loaded, the requirements for almost ridiculously high buffers... this means something. This is important.

Cubase tech's response (verbatim): "Well, you've got to expect that."

No, you do not need to expect that. That is simply not right.

Insist on further support, again - mention the "ASIO System/Driver issue", especially in combination with RME cards. Again, the German development section is aware of this already. Mention "Studio Compyfox", I filed this already in June/July and it got confirmed end of August to me through mail support. It is not in the public tracker however.

I just asked for another confirmation and status. With further test results. I don't think I'll get an answer before Monday/Thuesday.



Don't let yourself be put off. Some things are in motion. And the more people report such issues, also ask for TeamView sessions to "show them", the sooner it will be fixed.

Hopefully at least. I actually fear something worse. But certain people made enough noise recently, and Steinberg is trying to steer back.