Topic: Cubase Studio 5 Crashing after Metal Machine and EZDrummer Updates

Viewing 5 replies - 1 through 5 (of 5 total)

Replied May 21, 2013 at 19:37 #1965270

StealthMode
Participant

Further to this issue, I tried to downgrade the Metal Machine plugin using a backup from TimeMachine and for some reason the folders are now empty and any Cubase that I used MetalMachine on is now corrupt and crashes upon opening. WTF!!!
Where do I go for support? Things are just going from bad to worse.

Replied May 22, 2013 at 18:17 #1965280

StealthMode
Participant

Anyone got an idea how I can downgrade to my original EZDrummer Install? The EZDrummer 132 update seems to be what is causing my larger projects to crash, which is annoying as these are the one I have invested the most time creating.

Replied May 22, 2013 at 18:25 #1965281

Scott
Moderator

You can contact support directly via the Support Portal:

http://www.toontrack.com/helpdesk/issue_view_portal.asp?ID=81

Scott Sibley - Toontrack
Technical Advisor

Replied May 25, 2013 at 20:21 #1965317

StealthMode
Participant

Thnaks Scott. Good advice. If anyone is interested, it turns out multiple versions of EZDrummer were loaded causing memory overload and therefore Cubase was crashing. Still not sure how I can rescue my projects, but at least I know what was causing the crashes.

Replied June 9, 2013 at 12:06 #1965506

StealthMode
Participant

In case this post is of use to anyone else:

I managed to fix this by doing the following:
I created a new project in Cubase 5. Then I opened one of the projects which had been crashing, but I did not activate the project. From the non-active view I could see that there were several instances of EZDrummer being used on different tracks. Further confirmation of this was that the blue usage indicator bottom right in the EZD interface showed well over 1200MB usage. One instance of EZD uses approx. 364MB. So that was the problem. I then unnasigned or deleted the extra EZD tracks which brought the memory usage down considerably. I was then able to activate the project concerned and save without further crashes.

Thanks to support for leading me to the solution. The way I understand it is, the previous version of EZD had some kind of built in limit which would not allow more than a certain amount of memory to be used. This limit was removed in the 1.3.2 update and is the reason my projects started crashing because I had a few copies of EZD assigned to different tracks. There is no documentation that I have found which teaches you to use EZD or shows good practice recommendations. It is a simple enough and intuitive interface so in most cases you don’t need any. But it would have been good to know that you shouldn’t assign more than a certain number of instances of the plugin.

Relieved to have found a solution!! m/
Author

Replies

Viewing 5 replies - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.

Please log in to read and reply to this topic.

Cubase Studio 5 Crashing after Metal Machine and EZDrummer Updates

Studio Corner

Viewing 5 replies - 1 through 5 (of 5 total)