EZdrummer METALHEADS ERROR when trying to load

[leftlanetheory]

I Just downloaded the metal heads expansion and I’m having a bit of a problem. After downloading and installing it, I go load the metalheads kit for the first time and I get an “error” message from my Reaper saying it needs to close. I haven’t been able to authorize the metalheads kit yet because it hasn’t been able to load. I’m able to load the original ezdrummer as well as the DFH expansion with no problems. From the drop menu, Metalheads and ezdrummer are both available as well, so it must recognize it.

I’m using reaper. Any ideas?

Topic

[Scott]

Can you please give us some system specs? Are you using 64-bit Reaper?

Scott Sibley - Toontrack
Technical Advisor

[leftlanetheory]

I’m assuming its 64bit, thats what it says on the reaper site, but I’m not sure, is there a way to tell. I’m using a compaq R4000 512MB of ram, 60GB. It says reaper has encountered a problem and needs to close when trying to load the metalheads kit for the first time. The other kits load fine. I installed and registered the product with the included key. But haven’t been able to authorize it.

[Scott]

What OS (operating system)? Windows 7 64-bit? Any other VSTis running at the same time you load EZD?

I’m assuming its 64bit, thats what it says on the reaper site, but I’m not sure, is there a way to tell.

I don’t know. I use 32-bit Reaper. I’m not use if the 64-bit version is designated in the Help->About screen or not.

Scott Sibley - Toontrack
Technical Advisor

[Brad]

Could it be that MH is hitting some memory limitation? 512MB is not a lot of RAM….

Mac Studio M1 Max, RAM 64 GB, 1TB Drive, OSX 12.x/13.x and Windows 10 (VM)
DAW: Studio One Pro (always up to date)
DTX Express III (Extreme triggers), Nektar LX88
OWC Thunderbay Mini (4 X 1TB Sata SSD), Express 4M2 (4 X 2TB M.2 SSD), Envoy Express (1TB M.2 SSD)
Presonus Quantum, Faderport & Faderport 8
Black Lion Sparrow Mk2 A/D, FMR-RNP-RNC, MIDI Xpress 128, BM5A, KRK VXT4, Equator D5
2020 Macbook Pro 16GB RAM, 512GB SSD Audio(mobile rig)

[leftlanetheory]

Im using windows XP. I figured it might be the ram..but I have no problem running DFH or the pop/rock kit. Im just getting a message from reaper saying there was a problem and needs to close. On the toontrack site, it says there shouldn’t be a problem running with 512MB.

[Scott]

Well, you can’t use Reaper 64-bit in 32-bit XP (unless you are using 64-bit XP?). You need to use 32-bit Reaper.

At what point does Reaper crash; the first moment you load Metalheads or when the sounds start to load?

What version number is displayed in EZdrummer?

Have you tried using Toontrack Solo as host and see if the results are the same?

Scott Sibley - Toontrack
Technical Advisor

[leftlanetheory]

I’m not sure if im using the 64bit version, But I must not be if I’m able to load the poprock kit and the DFH expansion without problems right? I pretty sure

I haven’t used toontrack solo, but I’ll download it and give it a shot.

Reaper crashes, the second I try and load the Metalheads kit. The kit doesn’t even start loading, no sounds. Slight delay, then crash. As I mentioned before, I have no problem loading the other other 2 kits. From the pull down menu in EZdrummer, I select the metalheads kit and then I get the reaper encountered a problem and needs to close. It’s only with that particular kit.

[Scott]

What version number is displayed in EZdrummer?

Scott Sibley - Toontrack
Technical Advisor

[leftlanetheory]

EZdrummer 1.2.1 Is what Im running. 

[Scott]

Well, the default Metalheads kit takes a bit over 350MB of RAM to load. The Pop/Rock kit loads in at 268MB and DFH loads in 245MB.

Could it be the problem since you’re only running 512 of RAM? Maybe.

If you get the same results using Solo, I would guess that a lack of RAM is the issue.

Scott Sibley - Toontrack
Technical Advisor

[leftlanetheory]

Yeah, could be.. I’ll get back to you after I try a few things! Thanks for the help thus far.

[leftlanetheory]

Well, I got it to load! I forgot to reinstall the updated for EZdrummer. So that was the culprit. I was under the assumption that I already updated it. So Its up and running now.. Thanks scott.

[Author]

Replies