EZ Drummer 3 crashing

[allanM]

When I try to delete empty ez drummer 3,  multi-channels, ...

When I try to delete empty ez drummer 3,  multi-channels,  in Cakewalk it crashes.

EZdrummer version: 3.0.0
Operating system: Windows 10

When I try to delete empty ez drummer 3,  multi-channels,  in Cakewalk it crashes.

EZdrummer version: 3.0.0
Operating system: Windows 10

Topic

[Olof Hermansson]

daronpowers wrote:

Not sure who is Steven Thomason nor if the above email reply relates to me. Please advise.

Well, both of you should preferably have started your own threads since your crashes are unrelated to the one in the original post (and to each other).

Anyway, can you still reproduce a crash when you drag from Grooves to Song Creator, without having done any alt-resizing of a song track block before? What are the exact steps? You just open the project, open Song Creator, switch to Grooves and drag a groove to the “Drag MIDI here” zone in Song Creator? Does it happen in a new project as well and in the standalone?

Olof Hermansson - Toontrack
Coder

[Olof Hermansson]

Steven Thomason wrote:

EZ Drummer 3 Crashes when i attempt to extract audio in the form of stems, steps as follows,

1 export song as audio files

2 choose stems

3 sound quality high 24 bit

4 export & select folder

5 CRASH

 

EZdrummer 3 standalone version 3.0.6 (build 35660) [64-bit]

SOUND LIBRARIES
EZdrummer 3 Bright Room version 1.0.1
EZdrummer 3 Main Room version 1.0.1
EZdrummer 3 Percussion version 1.3.0
EZdrummer 3 Tight Room version 1.0.1

MIDI LIBRARIES
Acoustic Songwriter Grooves version 1.0.0
EZdrummer 3 Percussion version 1.0.1
EZdrummer 3 version 1.0.1

EZdrummer version: 3.0.6
Operating system: Windows 10

Could you attach a project where this can be reproduced, please? It may depend on for example which library/preset is being used and what MIDI is on the track.

Olof Hermansson - Toontrack
Coder

[daronpowers]

In another email thread Toontrack asked me to submit a crash report and determined that EZ3 has a serious bug. According to the email thread I am currently stuck with a continuously crashing problem until Toontrack decides to fix the problem and update the software. Frustrated and disappointed. Daron Powers

[daronpowers]

When is the next update of EZ3?

[daronpowers]

When are you going to update ez3 to fix the coding (as you discovered) as my ez3 continues to crash daily!

[daronpowers]

EZ3 is crashing daily many times per day. When are you going to fix it?

[Olof Hermansson]

We can’t say when the next update will be released. But when it comes, it would be a shame if it did not fix your crashes. We have fixed a crash that is related to alt-resizing a song track block before dragging from Grooves, and we said how to avoid it, but it seems you are getting other kinds of crashes? We can’t fix anything more if we don’t get more info, which is why I asked:

Can you still reproduce a crash when you drag from Grooves to Song Creator, without having done any alt-resizing of a song track block before? What are the exact steps? You just open the project, open Song Creator, switch to Grooves and drag a groove directly to the “Drag MIDI here” zone in Song Creator? Does it happen in a new project as well and can you reproduce it in the standalone? More crash logs may be useful too.

Olof Hermansson - Toontrack
Coder

[daronpowers]

When composing in my DAW (Digital Performer 10) with EZ3 open (any size window) I drag the groove down to the song creator. When the file hits the measure markers it crashes. Only when dragging across the measure markers does it reliably crash. Occasionally I can drag it fast across the measure marker and remain working. Seems to be no way to predict the crash (when dragging from grooves down to the song creator) but it’s consistently screwing up my workflow, clients are upset, and wasting a lot of time.

EZ2 had a bug that the tech said Toontracks would not fix and I was told by your techs to spend money and update. I like EZ3 but I don’t like working on pins and needles.

In a previous support ticket (don’t know how to find it for reference) your tech said it is a software BUG and would be fixed in the next update. I, however, am using EZ3 daily in my work and need a fix now.

[Olof Hermansson]

Hm, by “song creator”, do you mean “song track”? Because there are no measure markers between the grooves list and the song creator, but there are measure markers at the top of the song track (below the song creator if the song creator has been opened with the Song Creator button).

daronpowers wrote:

In a previous support ticket (don’t know how to find it for reference) your tech said it is a software BUG and would be fixed in the next update.

Do you mean what Christoffer wrote on the first page of this forum thread? (Click the “1” in the page navigator or click this link.)

Olof Hermansson - Toontrack
Coder

[daronpowers]

EZ3 Continues to crash daily. Totally screwing up my workflow, slowing down everything, starts, restart, it’s a nightmare. When will you fix this acknowledged bug in EZ3 software?

See visual. Please acknowledge.

[Olof Hermansson]

This crash can only happen if you have earlier pressed the left mouse button on the right edge of a song track MIDI block while holding down the alt/option key.

To avoid this crash, you can do the the following before starting to drag a groove down to the track: Click once with the mouse button (without holding down any key on the keyboard) in the middle of a song track MIDI block (inside the MIDI block but not near any of its edges).

Olof Hermansson - Toontrack
Coder

[daronpowers]

The crash happens by simply dragging the groove down to the song creator. I DO NOT press (as you suggest) the left mouse button on the right edge of a song track MIDI block while holding down the alt/option key. I do not touch the keyboard. All I do is select the groove with the mouse. Drag it down and when it hits the measures it crashes. One of your other techs said this is A KNOWN BUG. It is supposed to be fixed in an update. Please check with them about the update. These EZ crashes are killing me.

[Olof Hermansson]

For now, please try what I said on how to avoid the crash (clicking in the middle of a song track MIDI block each time before dragging down a groove).

The only crash bug that has been fixed is the one that caused the crash that you sent the crash log for (on page 1 of this forum thread) and it only happens if the last mouse-down on a song track MIDI block was on a right edge of one, while the alt/option key was held down (or the key was stuck so that the computer thought it was pressed). Note that this may have been done much earlier than when you drag down a groove to the song track (without pressing any key). If it really is impossible that the alt key has been pressed at any time when you have clicked in EZdrummer 3 after opening the project and it still crashes when you drag down a groove, then we need more crash logs (and maybe a project where it can be easily reproduced) because it must be another bug then, which has not been fixed.

Olof Hermansson - Toontrack
Coder

[daronpowers]

How about we get EZ3 working correctly.

“If it really is impossible that the alt key has been pressed at any time when you have clicked in EZdrummer 3 after opening the project and it still crashes when you drag down a groove, then we need more crash logs (and maybe a project where it can be easily reproduced) because it must be another bug then, which has not been fixed.”

Tell me what you want to get your software working correctly. Send over specific instructions. This bug is creating serious havoc.

[Olof Hermansson]

First, could you give straight answers to these questions, please:

1. Are you saying that when it crashes, you have never since the Digital Performer project was opened touched the keyboard at the same time as you have clicked in the EZdrummer 3 window?
2. Can you get it to crash if you do what I suggested to avoid the crashes (that is, if you click in the middle of a song track MIDI block each time before dragging down a groove)?

Olof Hermansson - Toontrack
Coder

[Author]

Replies