Replies created

 

Viewing 9 replies - 1 through 9 (of 9 total)
  • StealthMode
    Participant

    Make friends with a human drummer and bribe him to program tracks for you. You will need him later for live work anyway. 🙂
    Jokes aside, it is well worth watching someone program tracks who has been doing it for a while. There is a definite process. I have seen amazing drummers STRUGGLE to program midi and I have seen guitarists breeze through programming great drums for a song, from start to finish within a few hours, with amazing result.

    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/

    StealthMode
    Participant

    Sounds great! What settings did you use on MGG?

    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.

    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.

    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.

    StealthMode
    Participant

    Yes, it seems to be a feedback loop. But I have not been able to find a way to fix it. Do I need to buy an Audio Interface to get past this? I have always just muted the right channel and recorded mono into the left, but it is not working in this instance.

    StealthMode
    Participant

    But actually even the Stand Alone version of EZMix2 just feeds back and screams and doesn’t give any kind of sound I can work with, regardless of the Audio Setup I choose. I have tried every configuration. So it might be that the fact that I am going into a mixer and directly into the Mac has something to do with it. But I mean surely the Stand Alone version should work. I have guitar direct in to mixer output via Tape Output to Mac. Then the Mac Audio Out goes back into stereo Line In on the mixer.

    StealthMode
    Participant

    No, I am just applying the plugin directly on the channel as I would any other plugin effect. – Thanks

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

No products in the cart.

×