Topic: Installing 64-bit version after installed 32-bit version first wrongly

Viewing 15 replies - 1 through 15 (of 21 total)

Replied March 18, 2016 at 14:10 #1987063

Slam Executioner
Participant

I now realized that warning (“not enough memory”) pops up usually when I use and try to edit the drumkit from Progressive EZX. Maybe I didn’t installed that correctly?

In general, when I try to install the extracted 64-bit updater for EZDrummer2 it asks me to set the host. How is this made correctly? How do I set the 64-bit version as host during the installation process? Which folder is the right one to be sure there won’t be problems in the future and with further upgrades?

Please help.

Replied March 18, 2016 at 16:20 #1987064

Scott
Moderator

Can you please post pics of the pop up messages? I can’t really tell what is going on from your descriptions.

Scott Sibley - Toontrack
Technical Advisor

Replied March 19, 2016 at 17:53 #1987077

Slam Executioner
Participant

Sure, here is the warning that pops up. This shows up whenever I try to change some presets on the drumkit as seen on the pic. As I know, only if I use Progressive EZX.

Replied March 19, 2016 at 17:59 #1987078

Scott
Moderator

And the message that you get when you try to install the 64-bit version?

Scott Sibley - Toontrack
Technical Advisor

Replied March 19, 2016 at 18:03 #1987079

Scott
Moderator

@Slam Executioner said:

Sure, here is the warning that pops up. This shows up whenever I try to change some presets on the drumkit as seen on the pic. As I know, only if I use Progressive EZX.

The error pops up when you run out of RAM when running the 32-bit version in a 32-bit host. Are you running 32-bit Cubase? How much system RAM do you have? Is EZD2 the only thing loaded? Other instruments?

Scott Sibley - Toontrack
Technical Advisor

Replied March 19, 2016 at 18:15 #1987080

Slam Executioner
Participant

RAM: 8GB
Operating System: 64bit

Where can I check if I run Cubase in 32bit or in 64bit? Can’t remember what I installed back in the days…

EZD2 is the only loaded tool. No other Instruments are in use.

Replied March 19, 2016 at 18:37 #1987081

Slam Executioner
Participant

@Scott said:

And the message that you get when you try to install the 64-bit version?

I’ve installed the 32-bit update version and now I want to install the 64-bit update. So far so good. But then it asks me about the host thing. I have no clue about that to make it works corretly. Which folder do I have to choose there?

Replied March 19, 2016 at 18:50 #1987082

Scott
Moderator

@Slam Executioner said:

@Scott said:

And the message that you get when you try to install the 64-bit version?

I’ve installed the 32-bit update version and now I want to install the 64-bit update. So far so good. But then it asks me about the host thing. I have no clue about that to make it works corretly. Which folder do I have to choose there?

It’s asking where you have installed other 64-bit plugins on your system and to set the path if you do. I have no idea if you have or where that directory would be if you have.

Scott Sibley - Toontrack
Technical Advisor

Replied March 19, 2016 at 18:52 #1987083

Scott
Moderator

@Slam Executioner said:

RAM: 8GB
Operating System: 64bit

Where can I check if I run Cubase in 32bit or in 64bit? Can’t remember what I installed back in the days…

EZD2 is the only loaded tool. No other Instruments are in use.

I use Cubase Pro8 and it says on the startup screen when you start Cubase if you’re running the 32-bit or 64-bit version. Or it says in the Help-About Cubase window.

Scott Sibley - Toontrack
Technical Advisor

Replied March 19, 2016 at 20:06 #1987086

Slam Executioner
Participant

Next to that, I have a completely new problem now. The drum sounds cracks here and there. Haven’t that problem ever before. What is that?

Replied March 19, 2016 at 21:07 #1987088

Slam Executioner
Participant

@Slam Executioner said:

Next to that, I have a completely new problem now. The drum sounds cracks here and there. Haven’t that problem ever before. What is that?

Just raised the buffering from 256 to 512 and the cracking is nearly eliminated. But why not working with much higher buffering then? What would happen when i set it to max level? And why do i have problems with cracking since i installed new EZX’s and did several updates. I want to understand whats going on on my computer. And sorry for my newby questions.

Replied March 19, 2016 at 21:23 #1987089

Scott
Moderator

@Slam Executioner said:

@Slam Executioner said:

Next to that, I have a completely new problem now. The drum sounds cracks here and there. Haven’t that problem ever before. What is that?

Just raised the buffering from 256 to 512 and the cracking is nearly eliminated. But why not working with much higher buffering then? What would happen when i set it to max level? And why do i have problems with cracking since i installed new EZX’s and did several updates. I want to understand whats going on on my computer. And sorry for my newby questions.

A lower buffer allows for a closer ‘real time’ playing latency if you are using say, a MIDI keyboard and are inputting MIDI manually. If you are never doing that, and are only going to use the Toontrack MIDI or other 3rd party MIDI, then set the buffer as high as you want. I have mine at 64 buffer when inputting with my keyboard and then bump it up to 1024 when I mix.

You are probably experiencing this issue now as the Progressing EZX is more resource intensive than other EZXs. Do you have the same issue with the defualt kits or is it just the Progressive EZX? It uses more RAM than other kits, which is why you are getting the RAM limit message above.

Scott Sibley - Toontrack
Technical Advisor

Replied March 19, 2016 at 21:45 #1987092

Slam Executioner
Participant

Ok I understand the situation with the buffering/latency now. Much thanks for explaining me that. Does the latency thing has influence in MIDI only or in audio recording as well?

About the other problem. Yes it really seems that memory problems are only when I use Progressive EZX. Didn’t knew its more resource intensive than all others. Not sure if I have problems as well if I use another kit but run it with presets from Progressive EZX. Have to test that but probably same error. But anyways, how can i fix that memory problems?

Replied March 19, 2016 at 22:07 #1987093

Scott
Moderator

@Slam Executioner said:

Ok I understand the situation with the buffering/latency now. Much thanks for explaining me that. Does the latency thing has influence in MIDI only or in audio recording as well?

About the other problem. Yes it really seems that memory problems are only when I use Progressive EZX. Didn’t knew its more resource intensive than all others. Not sure if I have problems as well if I use another kit but run it with presets from Progressive EZX. Have to test that but probably same error. But anyways, how can i fix that memory problems?

Yes, buffer influences audio recording as well. Audio latency is the time it takes for the round trip from input to output. Recording the input and monitoring the output (headphones or speakers). Some audio software, Cubase is one, offer an ASIO Direct Monitoring that allows the audio to be monitored directly and bypasses the audio program for monitoring. However, you also bypass any effects that are on a particular track when recording. So, say you are recording a guitar part using an amp sim, if you use ASIO Direct Monitoring in Cubase, you will bypass the amp sim. So, there are advantages and disadvantages with all options. You can set a low buffer for tracking, and then a higher buffer for mixing.

The only way to fix the memory issue is to make sure you are using the 64-bit version of Cubase and the 64-bit version of EZD2.

If you use the 32-bit version of Cubase with the 32-bit version of EZD2, you will have a RAM limit of 4GB, regardless of how much RAM you have on your computer. Given that just booting Windows 7 and opening Cubase uses around 3GB of RAM, it doesn’t leave that much left for EZD2. And, like I said, the Progressive kits use more RAM and other libraries, you run into the memory error.

Using the 64-bit version of Cubase and EZD2, you have access to all of the system RAM. You will eliminate the memory error. Or, if you really have to use the 32-bit version for whatever reason, you can select ‘None’ on some of the kit pieces in the Progressive EZX so they won’t load into RAM. You may not need all of the cymbals, for example.

Scott Sibley - Toontrack
Technical Advisor

Replied March 19, 2016 at 22:50 #1987094

Slam Executioner
Participant

Much thanks for all your time and help Scott.

I still have to check if I run Cubase in 64-bit or not. But if so, where would I find a 64-bit version for EZ2 and would an update has a negative reaction on my actual projects?
And do what you think about if I use Progressive EZX samples in drummer superior? Would that lead to the same memory error?

note: still haven’t found out if I run Cubase in 64-bit or not. The problem is, when I start Cubase the startup screen is way to fast to read something. And can’t see any information about that in the help-about cubase window. Other options where I can see that?
Author

Replies

Viewing 15 replies - 1 through 15 (of 21 total)

Installing 64-bit version after installed 32-bit version first wrongly

EZdrummer Help

Viewing 15 replies - 1 through 15 (of 21 total)