I’m seriously looking at upgrading from EZD to EZDrummer 2.
Is anyone using EZD2 with Mixcraft? If so:
Were there any problems with the install?
Any problems with using EZD2 in Mixcraft?
Thanks,
I am a Mixcraft 6 Pro Studio user who uses EZD in just about every Mixcraft project I create.
I installed EZD2 without any problems. I haven’t started tweaking EZD2 within my Mixcraft projects yet, so I don’t have anyhing to share with you there I’m afraid. I have a few EZXs installed as well, and those didn’t cause any issues either.
Did you check the Mixcraft support forum? There are a lot of posts regarding EZD2 upgrade/installation issues and experiences in there.
http://acoustica.com/mixcraft/support.htm
It seems that EZD2 uses more resources (RAM) than the old version. And keep in mind that the current version of Mixcraft is a 32-bit application. Mixraft 7, scheduled for release later this year, will be 64-bit.
Thanks for the response,
I also use Mixcraft 6 Pro Studio and EZDrummer 1 and have not had any problems at all. It’s good to hear that you did not have any problems with the install. I have been following threads on the MC forum and see that some have reported problems. I plan to upgrade to the 64-bit MC7 when it is available. I may wait to upgrade EZD until that time so that I can just install the 64-bit version.
I use Mixcraft 6 and projects that use EZD2 (2.0.1) run out of memory on a 32 bit machine. You have to throw out EZD entirely, work on the project, freeze, and then reload EZD – not exactly the fine british way of doing things.
Dying means a total crash during play with dreadful sound, not a graceful signing out.
There is something unstable about the memory management of EZD2, sorry to say that.
I hope somebody in control monitors what is being written here and initiates some improvement.
The package is good per se if it works, but those crashes stretch my patience hard up to the point where I want do demand refund.
-helmut
Hi aquatar,
can you load 600-800 MB with other Virtual Instruments in your 32-bit Mixcraft 6 environment?
With that I do not mean sample players that stream from hard drives but are actually loading into RAM, which is what EZdrummer 2 does.
In 32-bit environments, particularly on Win OS, the loading of OS, host and VI hits the 2GB(-ish) limit fairly easy which usually results in crashes. Not so much host or VI dependent.
John Rammelt - Toontrack
Technical Advisor
@John said:
Hi aquatar,
can you load 600-800 MB with other Virtual Instruments in your 32-bit Mixcraft 6 environment?
With that I do not mean sample players that stream from hard drives but are actually loading into RAM, which is what EZdrummer 2 does.
In 32-bit environments, particularly on Win OS, the loading of OS, host and VI hits the 2GB(-ish) limit fairly easy which usually results in crashes. Not so much host or VI dependent.
Hi John…
I brought this up in a related thread here in the forum and was soundly trounced… Maybe you can shed some light. I suggested using J-Bridge to “bridge” the 64 bit version of EZD2 into Mixcraft. I was told NEVER use any bridging software. When I asked why since I have successfully used J-Bridge to bring in my 64 bit versions of East West Quantum Leap samples into Mixcraft. By the way, I have also used it in the other direction too and bridged some 32 bit VSTs into my 64 bit DAW. I politely asked if we could discuss the “whys” of not using J-Bridge and was totally blown off..
Maybe you can offer some insight here
Regards
Pierre
The reasoning of why not to use a bit bridge is that Toontrack doesn’t support it’s use with our software. Using a bit bridge is for using a 64-bit plugin in a 32-bit DAW or vice versa. There are both 32-bit and 64-bit versions of our plugins so there’s no need to bit bridge.
Scott Sibley - Toontrack
Technical Advisor
@John said:
can you load 600-800 MB with other Virtual Instruments in your 32-bit Mixcraft 6 environment?
John,
unfortunately I cannot tell. I do not work much with sampled instruments and the ones I used seemingly did not produce a problem (or did not use much RAM)
@John said:
In 32-bit environments, particularly on Win OS, the loading of OS, host and VI hits the 2GB(-ish) limit fairly easy which usually results in crashes. Not so much host or VI dependent.
What do you mean with the 2GB? I have 4GB installed and it uses 3.25 or thereabouts.
I am no expert in those things, but I find it hard to believe that *any* behaved program can crash anything.
EZD2 loads okay with a minimum default kit (aka low memory consumption), but when I load a different kit, or sometimes just browse grooves, it stalls the DAW totally.
-helmut
@aquataur said:
What do you mean with the 2GB? I have 4GB installed and it uses 3.25 or thereabouts.
http://www.viva64.com/en/k/0036/
I am no expert in those things, but I find it hard to believe that *any* behaved program can crash anything.
-helmut
Well, believe it or not, I had a lot of problems myself when I ran one of my studio setups as Pro Tools HD on PC under Win XP and when I loaded kits bigger than 7-800MB on that particular machine (with Superior 2), it totally crashed the machine, ’cause Pro Tools landed around 1GB when fully loaded with all plugins and a Session. Seen it happen in 32-bit Sonar as well.
Not the plugin but the app crashes due to the RAM access limit being hit. It doesn’t matter how much physical RAM is installed. You should be able to use th 3GB switch, though.
John Rammelt - Toontrack
Technical Advisor
No products in the cart.
Get all the latest on new releases,
updates and offers directly to your inbox.
Note: By clicking the 'I WANT IN' button, you will not be creating a Toontrack user account. You will only sign up to get our newsletters, offers and promotions to your inbox. You can unsubscribe at any time from a link at the bottom of each email. If you want to learn more about our privacy policy, please find detailed information here.