Interesting. Too many variables........is there ever going to be a day when shit just works for everyone?

I'm someone that...

Used Reason for 9 years before I switched to Cubase and later REAPER in 2010 to get back to Reason in 2011.

I may not be the best example for pushing your "will" to change? Because to me, this is the crucial part here. Not what we can tell you what we experienced or major differences. They actually should be obvious. Why would you switch in the first place? Now with Reason 6.5 around the corner, I wouldn't want to switch at all. Especially if you can get a free upgrade and just lean back and wait for what's coming up in the RE store, once it's up and running. Since plug-ins are plug-ins and hosts are hosts.

sure, when everyone's understanding is equal, some magical day in wonderland.

As I said, the same VSTS do not make other hosts crash. In fact, not even once. The primary VST in question here, although certainly not the only one, and, as others have pointed out, Steinberg's own plugs were as much to blame, is Reaktor. So, is it cubase, or is it reaktor? Frankly, I don't care, Reaktor + Cubase = Frequent Crashes, Reaktor + Other hosts = No Crashes; that's my experience and that's enough to assert "cubase crashes, other hosts do not."

My machines are NEVER marginal, NEVER, did I say NEVER, I meant to say NEVER. So, that was never an issue for me. Also, I'm not exactly naive with respect to computers, the point being, that I'm not reporting a simple crash. I'm talking about repeated problems across multiple machines, multiple versions of host OS, and multiple attempts to isolate the problem. (XP, Vista 64, win7 32, win7 64).

My experience mirrors the experience of others and the following post suggests a far more likely technical reason than your dismissive reply.

http://www.cubase.net/phpbb2/viewtopic.php?t=123082

It seems that 32 bit cubase had memory issues across all versions from SX4 through 6.01. It appears that it is hyper sensitive to plugin memory leaks. This, in fact, may be a bug in cubase, or not, but it makes no difference and you cannot categorically assert that cubase ISN'T to blame. If you've ever done any C/C++ programming you know that memory leaks are common. That doesn't make it good programming, but, if you are selling a host, you should expect that it will happen and do your best to contain the impact. The point is that it doesn't matter whether you want to call it a bug in cubase or not, the fact remains that cubase (32 bit) is MORE sensitive to memory leaks in other plugins than other hosts. In fact, that same thread points out that GA1 had a bad memory leak in 5.01. So using cubase with Steinberg's own plugs leads to crashes and does not give us the confidence that Steinberg's team has any greater understanding of how to build stable software than the plugin devs that you're suggesting are the culprit.

There were/are also numerous annoying bugs in cubase that impacted my day to day usage of the product. Of all the hosts that I've tried, it was the least stable, had the highest number of annoying quirks and bugs, and seems the most stuck in CS ideas from ten years ago.

Other hosts are more robust, let's call this a feature, a competitive advantage, the mark of a superior product, a demonstration of better programming talent, or whatever you like. The point is, with respect to this thread, that instability is something you should get used to with cubase whether you use the unstable plugins of others, or, prematurely shipped and unstable plugins from Steinberg.

If thats the case the why do some have no issues :



Seems that something other than Cubase is problematic here. When people start talking about Steinberg not knowing what they are doing, C++, memory leaks etc, I start to think theyve tweaked the hell out of Windows or used utils etc causing damage that they dont see.

The answer is very simple, it's use case.


You can't draw that conclusion. All you can say is that if you haven't experienced a defect, then you haven't triggered the use case that uncovers that defect.

So, every case of reported instability is valid to the extent that, under their use case, with their equipment, that the instability exists. It is reasonable to consider whether it's equipment, or other software.

But, again, if it's other software, that's again not relevant, Reaktor+Cubase=Crash, Reaktor+Other Hosts = No crash. Doesn't matter where the bug is, that's something that you should expect with Cubase+Reaktor, end of story.

Further, we know that GA1, from Steinberg, with cubase, also triggers crashes, at this point, we're done; we absolutely can blame Steinberg for releasing unstable software. Moreover, it's not that much of a stretch to place a greater likelihood on cubase being buggy than other VSTS.



Well, simply put, you're wrong, moreover, pulling guesses out of your ass simply speaks to your ignorance. You're projecting a profile onto me based on your limited exposure to technical topics. Understanding memory leaks is a product of education, it's not simply some hacker-speak exchanged by teenagers.

It's pretty obvious that things do not always works the same for everyone. That is a fact in the software world. And no, it's not always user error.

I mean, people are able to use some hosts on machines that are obviously less powerful than mine where I cannot. Some though, have issues with what I use on equal machines. It's not perfect science. Can we draw logical conclusions most of the time? Sure. But it's not exact.

Add the fact that some want to hate on a DAW/plug/company and will say anything to make it bad and you have even more chaos.

Not to mention the fanbois who stick up for everything their host is

Again, you might do better in this conversation if you stop pulling nonsense out of your ass. What I'm doing is expressing my experience, which is irrefutable, and drawing reasonable conclusions based on both my experience, and my education.

If you want to refute my conclusions related to my experience of severe instability with cubase, you will have to work a bit harder to construct arguments that actually make sense.

You have a history of doing this. I dont have to prove anything to anyone. I use Cubase to make music. I could give a rats ass about memory leaks etc. If you pay me I might help you solve your issues, clearly you cant solve them

You mean that I have a history of being critical of substandard products, yes, that's the only correct thing that you've stated so far.



Why would I pay you for anything, you've demonstrated no ability to think rationally and you don't understand computers?

Personally, I don't have any "issues." I had a problem using an unstable DAW. I fixed that problem easily by switching to a stable DAW. Along the way, I gave up very little and gained quite a lot. To me, cubase is outdated. It's surviving on inertia.

With other DAWS, there simply hasn't been any stability issues to speak of. That was all that was necessary to fix cubase, ditch it.

That's absurdly reductive. As if there are no other factors preseent but the two. This is indicative of very poor reasoning. As far as use case, that means the other user without eg. the Reaktor+Cubase=Crash scenario are avoiding something you have in your system, which you seem ready to dismiss entirely in your argument. It is a bad argument. Your pretense at making better arguments than the next guy doesn't help that argument.

For me it's Reaper + Kontakt = crash. It happened with Reaper 3 and Kontakt 3 in the past and happens now with Reaper 4 and Kontakt 4. Does it mean that Reaper is a substandard bla, bla, bla...

No if I'm the only one that experiences this.

I think you have a problem managing that DAW. If I didn't have the issue, it means I did something different, quite simply. The combination of factors in your experience produce a result you lay solely at the host's door. It's not good reasoning, sorry to say.

Your choice of what to do to get rid of it, good for you, but you are using a public forum to put out information that isn't necessarily good, so expect some disagreement.