[aquataur]

@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]

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

[aquataur]

Patrick,

my post is related to the initial version. I have not worked extensively with Mixcraft since the bugfix, so I cannot comment on wheter things have changed or not.

Nevertheless, I find it strange that a process can screw up another processes memory. From my past software writing endeavours I would think, if memory is not available, I cannot allocate it. If I cannot allocate it, I should not write anywhere. If that were the case I would call it bad coding, but I cannot image that.

Officially, there was 600MB available when this happened BTW.

-helmut

[aquataur]

Scott,

yes I read it. But if the folks are in the verge of fixing things they might need to know that there persists a problem that they are not aware of yet.
I have not seen them things Mixcraft adressed yet.
-helmut

[aquataur]

Maybe you folks at toontrack should know about this too…

Using Mixcraft 6 as a host, sometimes when I use EZD2 in a project, other plug-ins (that had worked flawlessly up to this point) produce strange out-of-memory errors.
* I also frequently cannot load any other fx into the plugin slots,
* the EZD2 GUI won´t open,
* some host dialogs refuse to open
* EZD2 won´t play despite the fact that “follow host” is enabled. (It does start if I open the gui most of the time, but sometimes it refuses to play in sync at all.)
* and EZD2 crashes frequently when I change kits despite some 1GB free memory.
* EZD2 crashes when opening its own menu (such as saving a preset)

all above requires a host restart.
Mixcraft 6 is out if its cradle and stable. This is beyond discussion.

Otherwise, its a great plug-in and I am sure you´ll get those errors fixed.

-helmut

[aquataur]

Hi,

I just temporarily resolved a similar crash issue.

It appeared that EZD2 crashes on some (busy) Mixcraft projects, but not on others. It *always* crashes if two instances are opened.
Note that the plugin created crash dump report files, but those were empty.

The support wrote me the following: “Using multiple instances of EZD 2 in your 32 bit DAW can cause the DAW to crash, as it will not allow you to use more than around 4GB of memory.”.

Besides the fact that I believe that a behaved plugin should report to, but NEVER crash the DAW, memory shortage *was* the reason for the current series of crashes.
I opened the OS´s resource monitor and threw out all lingering memory thieves. It appeared that the problematic project had only 1GB memory available before loading EZD2, which, dependent on the kit it was going to load, was too little.

So, probably most important, I used the stand alone version to set a default kit (MENU>PROJECT>SET AS DEFAULT PROJECT ) the cocktail kit, with used few samples.
The plugin now loads fine. However, loading a different (bigger) kit may crash it again dependent on the available memory.

Folks, in earnest, you should fix this. This is not exactly a free plugin.

-helmut

[Author]

Replies