Crash inside live ezd2

[chris harbin]

If you select a different output than 1 in ezd2...

If you select a different output than 1 in ezd2 then ezd2 crashes. Happens 100% of the time.

I’ll ask again, is there not an ezdrummer support area currently?

If you select a different output than 1 in ezd2 then ezd2 crashes. Happens 100% of the time.

I’ll ask again, is there not an ezdrummer support area currently?

Topic

[Tom~Metro]

@Olle said:

>Will this fix also include the random mis-numbering of the Multi-Out option?

I am not aware of any such problems. Where and when does
what happen?

I mentioned this in my first post, and in two bug reports I have sent you.

When Multichannel is selected in the mixer… Drum tracks are not sequentially numbered. They appear very random.

thanks again

tom

[Erik Phersson]

> Output 3 Is missing when clicking for Multi-Out.

Was that the bug regarding random mis-numbering of the Multi-Out option?

Was that the output assignments in the EZdrummer Mixer missing Output 3 or do you mean that there is a route from the EZdrummer mixer to output 3 but there’s no sound in your host on that channel?

Erik Phersson - Toontrack
Head Of Development

[Tom~Metro]

Click on the Mulichannel button. Depending on the kit selected the numbering is not 1-12 as it should be. The channels are numbered out of order and some numbers are missing completely. This is on the EZ Drummer mix window.

tom

[Olof Westman]

That’s not a bug. The multi-out routing template is no more than a
suggestion but it is a suggestion that always follows a certain way
of sending the same signals to the same outputs. Kick goes to
output 1, snare top goes to output 2, snare bottom to output 3,
hihat to output 4 and so on. If the preset has no Snare Bottom
channel then there is nothing routed to output 3.

Olof Westman - Toontrack
Coder

[Tom~Metro]

@Olle said:

That’s not a bug. The multi-out routing template is no more than a
suggestion but it is a suggestion that always follows a certain way
of sending the same signals to the same outputs. Kick goes to
output 1, snare top goes to output 2, snare bottom to output 3,
hihat to output 4 and so on. If the preset has no Snare Bottom
channel then there is nothing routed to output 3.

I guess this makes sense if I adjust my thinking a bit.
Thanks for the explanation.

tom

[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

[Roy Parker]

Several questions to help me decide to wait on this product or move on to another product or suite. The multi-out functionality is big for me. I understand no time estimates can be given, but I do wish companies would at least gives us a range that still allows some flexibility. So, with that in mind….

#1: Is there any range of time that you can give us regarding the issue/update release for this issue? less than three months, three to six months, 6 months to a year or over a year?

#2: This may negate my need for an answer to the previous question. From within Pro Tools 11 running 48K sessions, is there a way to set and use the multiple output channels without the crashes?

#3: Related to #2, are the multiple output channel assignments global in nature? Can they be set in stand-alone mode or within Reaper and then opened and used in Pro Tools, or are they project attributes that need to be done for every instance or project?

#4: Will there be a demo made available so that one could install and try out for themselves to answer questions like 2 & 3 without having to beg on your pre-sales forum?

Thanks in advance for any answers. hopefully I can join the club.

[Tom~Metro]

HI Olle,

Is there any word on the bug fixes yet. The one involving “Muli-Out Crashes” at 48k is a showstopper here. PLease advise.

Thanks

Tom

[Scott]

We are currently working on an update. It will be released when it has gone through the proper beta testing process. In other words, ASAP!

Scott Sibley - Toontrack
Technical Advisor

[chris harbin]

It’s tough waiting.

[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

[chris harbin]

@Scott said:

We are currently working on an update. It will be released when it has gone through the proper beta testing process. In other words, ASAP!

[Tom~Metro]

@chris said:

@Scott said:

We are currently working on an update. It will be released when it has gone through the proper beta testing process. In other words, ASAP!

^^^ That’s me way in the back, 3rd torch from the left. ^^^

[chris harbin]

Yay it’s here!

Now I can move everything back to 48k/128.

[chris harbin]

So far……….this seems to work!

[Author]

Replies