ENOUGH IS ENOUGH STEINBERG...

It’s okay man, we all get a bit frustrated from time to time, and it’s very easy to get hung up chasing down little issues because “that shouldn’t happen”. But ya know, I work on a PC. Lots of things shouldn’t happen haha. But I just have to grin and bear it and take the rough with the smooth. Thankfully there’s way more smooth, at least in my experience. I spent months trying to get rid of every trace of noise/interference in my guitar signal. Spent money on isolators, new cables, moving all my stuff around. And then I realised I hadn’t made any music. All I’d been doing was loading up Cubase and looking for the noise. Wasn’t until I watched some documentary about the recording of a famous album and they had TONNES of noise in their signal haha. I was like, “ya know what, stuff it. I’ve got the tools I need to make music. Stop obsessing, get it done.”

But it happens to us all at some point. I hope you can get done what you need to, and again good luck with your Triebwork issue. Let us know if you get it sorted.

Yeah well we have all been there in one form or another. Computers and software are frustrating devices. I just try to remember that it is all about the music. Also that the Forum is filled with users who know a lot more than me. I hope!

First let me say i do feel the OPs frustration. Ive often screamed at Cubase. A Lot.

But i must say, i had similar graphical glitches in Cubase…cursor problems, VST plugin windows going scrambly… etc etc

problem was my graphics card. It was dumping its guts. Some problems in the graphics card memory, probably some old driver problems as well. Just went out and brought myself a new card for $100 bucks, installed latest NVidia graphics drivers and…all problems gone.

Graphics cards dont just die man. sometimes they just get glitchy under CPU strain. Something to think about. Id start there. i think you will be surprised.

Cheers,
Blackout

Most video cards are optimized for game frame rates and pushing there imterrupts throught everything else. Probably better to avoid expensive gaming graphic cards.
However there are reports of users experience the same behaviour with onboard video cards, go figure!

The solution could be to put the head developer of NVidia on a stick and throw (EDIT: Rotten) tomatoes at him :slight_smile:

Hmmm - I’ve never had problems with any of the NVIDEA cards I’ve used in by computer builds!

[Post to multiple forums removed]

Need to clarify a bit, I had problems with some versions of drivers. Now my system is operating stable with a GTX 650ti card.

Exactly what I was thinking! I wonder what the OP’s system specs are, including interface…would you mind posting onemidi?

I just find it funny how there’s a handful of forum members complaining that Cubase is always riddled with bugs, yet I have never encountered them (on both PC and Mac), and I’m sure there are literally thousands of satisfied users. Maybe I’m lucky :smiley: , but I can contest it’s been solid for me since C7.

Odd that yours is the firat post I read after posting this:

I agree with you.

Hugh

Hi,

my Impression is that something is “going on” in the Forum concerning “this Software is full of bugs”. I am working with cubase since a decade at least and it is ridiculous to say it is “full of bugs”. Of course there have always been issues, like with any other complex Software, sometimes affection oneself and sometimes not - often depending on the personal workflow.
Steinberg is working professionally. Some of the “This Software sucks”-Posters somehow seem to do so as well: Work profesisonally. But the Profession is different… trolling maybe. Or is it only the personal style of People? Or… which I suspect based on the talking on some posted Videos… or… are they on any Kind of drugs?

Cheers, Ernst

Onemidi, please run dxdiag and post the resulting file.

To do it in Windows XP, Vista, or 7, simply click the start button, select ‘run’ and type in
dxdiag
And hit enter.

On windows 8 or 8.1
in desktop mode tap the left ‘windows key’ and r at the same time then type:
dxdiag
Hit enter.

If you’re on Windows 10:
Right click the start button and choose ‘run’
Type in dxdiag
hit enter

Once dxdiag has run and collected the information, click the save all information tab.
Post the resulting DxDiag.txt file.

If you file bug reports…always do that and include the DxDiag.txt file. Also look in your Documents folder and zip up everything in the 'Stienberg/CrashDumps" folder. Attach that as well.

The crash dumps may be too big to post here on the forum (and few of us outside the people at Steinberg would find much useful in them anyway), but quite a few of us would like to take a gander at your system configuration.

I know I’ve had to weed out a few bits of hardware and drivers in the past that just flat out sucked for DAW purposes…

I agree completely with your post! Cubase is a SOLID piece of software; myself and thousands of others rely on it for professional work (film scoring, trailers, etc). It’s funny how most of the “bugs” I read about end up being user/hardware error by the end of the threads. Like you said, of course there will always be annoyances and minor “bugs”, but nothing show-stopping as usually noted (which is a bad first impression for someone looking at purchasing Cubase). Heck, I also use Logic and Pro Tools. Love Logic X, but if you want to talk about real headaches, PT is a real doozy lol! It will be interesting to see Onemidi’s posted results, along with the system specs.

Probably people who have zero trouble with Studio One barely scratched the surface. Studio One has some annoying issues for years too. Big difference is, Studio One users don’t really care if MIDI CC data is reset, or events within parts jump all over the place, or copied automation lands on different lanes. As long as they can drag and drop, it works as expected :laughing:

Who said I didn’t? I bought 3… A 2010 MacBook Pro in 2010, a maxed out 2012 iMac in 2012 and another maxed out MacBook Pro late 2013. Buying another computer won’t fix Cubase!

Thank you… I’m sorry about that.

My Specs:

Cubase Pro 8.5
Mac OSX Yosemite 10.10.5
MacBook Pro (Retina, 15-inch, Late 2013)
Processor 2.6 GHz Quad Intel Core i7
Memory 16 GB 1600MHz DDR3

My Specs:

Cubase Pro 8.5
Mac OSX Yosemite 10.10.5
MacBook Pro (Retina, 15-inch, Late 2013)
Processor 2.6 GHz Quad Intel Core i7
Memory 16 GB 1600MHz DDR3

I have the same MacBook. Granted, I run a slave from it for heavy libraries, but still have no issues with Cubase 7 or 8. And yes, I work professionally.

What are you using for an interface?

To everyone saying Cubase is “solid as a rock” head over to the “issues” forum and have a look, according to you guys this forum should be empty, so it may suprise you guys to see that its not. Steinberg have a long list of (according to you guys) “solid as a rock, bug free, non-issues” to deal with.

If you just scratch the surface of Cubase and you can do what you need to bug free, then thumbs up for you, but for the rest of us who really go deep and use features that you guys don’t even know exist, let us post about bugs that we find. Its kind of stupid replying to someone’s post about a bug saying “Uhhhh, I don’t know, but Cubase is solid as a rock to me”. LOL!.. Obviously everyone uses Cubase in a different way so the bugs I find you guys may never encounter and vice versa.

A Steinberg UR22 on the road and the Steinberg mr816 csx when Im home.