What could one expect when switching Reason to Cubase?

[braj]

[hibidy]

I didn't get that at all but the others ones that pop up after are quite disturbing.

[AstralExistence]

its a bad idea man. stick with what you know and never stray once you know it. if only somebody could have given me this advice early on. the biggest issue you face when switching host is project compatibility.

[braj]

I didn't get that at all but the others ones that pop up after are quite disturbing.

Well, it involved a crash sorry about whatever popped up afterwards.

[ghettosynth]

...

[hibidy]

I didn't get that at all but the others ones that pop up after are quite disturbing.

Well, it involved a crash sorry about whatever popped up afterwards.

I should have gotten it.............good call!

[braj]

I didn't get that at all but the others ones that pop up after are quite disturbing.

Well, it involved a crash sorry about whatever popped up afterwards.

I should have gotten it.............good call!

Just sometimes reading stuff on KVR, in my head I hear 'Jesus Christ!' which is good that I am at least thinking of Jesus I guess

[LeVzi]

In my experience, you will also have to get used to a lot of crashing. Cubase crashes are the reason I tried reason in the first place.

Not a single crash since Cubase 4 here.

Sorry for off-topic, but did you try Minimogue VA? It always crashes my Cubase, like any of the Stegner plugins, Arppe2600va too...

Bridge them. jbridge stopped that happening, even in a 32bit host.

[ghettosynth]

...

[jancivil]

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

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

...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.

That's absurdly reductive.

It's completely sufficient given all other information presented, which, you are ignoring.

As if there are no other factors preseent but the two.

I never said that. However, you can't just invent other factors as if they are going to be substantially meaningful. I've given you most of the parameters of interest, what else do you think will matter?

If you now want to suggest that there might be some other exogenous confound, then that's perfectly fine, but you must be prepared to suggest what it might be. In other words, you don't get the god argument just because we disagree.

The question asked was why other users don't have issues. I presented a reason, it's use case. That is completely valid, and you know it.

So granted. You are making a larger argument it seems to me.

Second, I stated that given TWO equal scenarios with the exception of host, that one is more stable than the other, also, equally valid, and here, irrefutable.

So, step up, what do you think that it is? Of course it could be anything, but we have to consider the prior probabilities and I'm fairly certain that anything that you come up with will be insignificant in my case.

I would of course need all sorts of information to help you sort why reaktor fails on your system. It happens to be the one plugin I nearly always plug directly into Cubase, as opposed to VE Pro, and it always works with No Issue. So. Logically it IS a sandbox difference. There is no way around that. I would have to do more work than I'm interested in to know if you mean comparing Reason to Cubase with Reaktor is equal. I hope not, as that would be absurd. Reason is in general more stable than any plugin host given enough sandbox conflicts, which may be very little. I don't need to invent anything and YOU know it. You are implying you have a rather flawless system somehow, even though later you can't manage to install Cubase without enormous problems. You do things very differently than do I, evidently.

However, the crux of my point, is that WHATEVER it is, it doesn't affect the other host, this is also irrefutable. So now instead of saying that cubase is more sensitive to memory leaks, we are saying ALSO that cubase is ALSO more sensitive to whatever other exogenous confound that you want to blame the instability on.

So, yeah, a host that does not use plugins does not have the crud in the sandbox situation a plug in host has. That is quite evident from nothing more than that fact.

If the person considering the change has no need for VSTs that Reason doesn't have an equivalance to, and to my knowledge there are some very attractive instruments, and one thinks those effects sound great - I do not - why bother with what is really a big change. I'm not advocating for someone to choose Cubase because I prefer it, but I find your arguments to be kind of dodgy.

[jancivil]

my exp. with Cubase is SX2 and C5, up to 5.5.3 which only rarely crashed and I was pushing it when it did. Hasn't in a long time.
SX2 crashed a lot but I barely met minimal recommended system specs at the time.

You seem to be blaming a host for unstable VSTs to me.

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?

I say it's your particular use of, owing to factors you aren't talking about. Demanding I come up with imaginary scenarios about your system, or the implication I'm inventing doesn't get rid of the clear logical problem. The simple conclusion you have is not good, really.

You have a bizarre installation of the application, following this other stuff. I don't think your system is a good baseline for anything frankly.

[yairhol]

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.

Probably not, and my first guess would be that it was in Kontakt. The same thoughts occurred to me with Reaktor and Cubase, that the problem was with NI. After all, these are also substantial programs with a long history and potentially large memory footprints.

In fact, that's why initially I just gave up on using reaktor as a VST because I had read that others thought that it was unstable as a VST. To be clear though, cubase was not stable for me even without using Reaktor, it's just that Reaktor was a standout.

Because of this frustration, I switched to Reason and got a lot of work done, but, I wanted to use Reaktor again (as a plugin), so I started looking at other hosts.

What I found was two things:

1) Other hosts, EVERY HOST THAT I TRIED, were stable.

But, wait, my system had changed, cubase had been updated, maybe cubase was stable too? Maybe I could bet back to all of that work that I started and gave up on?

2) Nope new installs of cubase on new systems were STILL unstable compared to other hosts.

I can load 5.5.3 right now, bring in Reaktor, and probably work in it for several hours without problem. Then again, it might crash within fifteen minutes. Almost without exception, cubase has crashed at least once in every session longer than an hour that I've used it. That's from version 5.0 through 5.53. Again, on multiple systems, all new components, across different OSes, with or without Reaktor, in fact, with or without any plugins other than the steinberg effects, etc.

Since the first attempt to give cubase a second chance, I have gone through two more system changes, and the same pattern holds.

Your experience here is very unique. If that was the case for a lot more users, Steinberg would be flooded with complaints. Since I can't find anyone else having so much problems with Cubase, I conclude that it's something unique that is happening on your systems. Why? I don't know. But saying a general thing as Cubase is unstable, is just not true.
I'm on Cubase Studio 4 and crashes are *almost* non-existent.

[LeVzi]

To the OP

In a word


Freedom

[ghettosynth]

...