Anyone else experience crashes on Cubase (x64)?

[nousch]

We still haven't been able to reproduce the problem with large projects, I' m afraid. But we did find some inefficiencies in the Redline Reverb code that potentially could cause problems. Because we can't reproduce your problem here, and as a consequence can't tell if the changes we made indeed have solved it, we kindly ask you guys to try the new beta and report back:

www.112db.com/beta

Thanks in advance,

--nousch

[niles]

Nousch, thanks for getting back at us.
I've tested the 1.7 beta with a demo license, and the behavior is the same. When opening the GUI in a larger project (+/- 4.5GB), Cubase crashes.
I also tested Studio One 2.5 x64, and that one too crashed with a 3GB project, exact same behavior as Cubase.

Despite the fact I don't have any trouble with other x64's plugs in big projects, I'm afraid it system related then. Especially given the fact you are not able to reproduce the issue on a PC with a Cubase x64 project >4GB.

[neilwilkes]

I am not at all certain this is a 112dB bug.
Why? Simply because not only can I not repro this, but also because I have heard of it in other plugin manufacturers/coders as well, and again - cannot repro.

Dare I ask if you have any Native Instruments plugins running when these crashes occur?

[niles]

Dare I ask if you have any Native Instruments plugins running when these crashes occur?

Yes, I have several Native Instruments plugins running. Could those be troublemakers?

Edit: I just tried to reproduce the problem with a Cubase project and only one instance of Halion 4 loaded with a bunch of high memory patches, and the problem remains. So I'm afraid it's not related to Native Instruments plugs.

[nousch]

Sorry to hear it still not working. I really hoped those changes would have made a difference...

I have heard of it in other plugin manufacturers/coders as well, and again - cannot repro.
 

Could you perhaps send me a link if you have one? I can try to do some detective work, maybe those other problems can reveal the underlying cause.

--nousch

[niles]

Sorry to hear it still not working. I really hoped those changes would have made a difference...

Yep, me too  

For the record, when a project is small it works perfectly, I can easily run 340+ instances of the reverb without any trouble.
Another remarkable thing. When I switch the plugin's GUI to "Generic editor" in Cubase, while spiking, the spiking stops immediately.

Neil and Nousch, do you care to share your system specifications?

[nousch]

I don't really understand what you mean, we got a lot of different systems here to test with. When someone has a problem we try the one that comes the most close. Is that the one you're interested in?

--nousch

[niles]

I don't really understand what you mean, we got a lot of different systems here to test with. When someone has a problem we try the one that comes the most close. Is that the one you're interested in?

Yes, that's the one. Because maybe an obvious thing like the graphic card/driver or type of CPU could be the cause of the issue.
I'm almost sure it's related to something graphical, because when I open the plugin GUI when it's NOT activated in Cubase, it also starts stressing my 12th CPU core. The fact it always and every time stresses the same CPU core in every high memory project, is remarkable itself.

Obviously when I run multiple instances of the plugin in an empty project, every separate instances of the plugin is pointed to 1 of the 12 cores, exactly like it should be in a multi processing environment.