Sustaining Randomly – No Control over Sustain Pedal

[csonc]

Hello,

I don’t know why EZ Keys is sustaining when I am not wanting it to.

This occurs both while using Ableton and while using it in Standalone mode. Even when I automate 0 for CC64 it still comes on. When I drag the MIDI from EZ Keys into a channel with Kontakt it plays with sustain.

But let’s just focus on stand alone mode because if that gets solved it will most likely be solved in my DAW.

I have no MIDI devices plugged into my computer (macOS 10.14.6)

I have no idea where it is getting this CC information.

When I use the browser and replace the MIDI the sustain is only held down when appropriate, but if I create my own segment then the sustain pedal gets held down despite me wanting it to.

So basically I have no control over the sustain pedal at all.

Occurred before and after update to 1.3

Any help would be greatly appreciated.

See video here:

https://drive.google.com/file/d/1Na_w9W-RBw93vgEeJJwXUfY-p69HAeTi/view?usp=sharing

EZkeys version: 1.3.0
Operating system: macOS Mojave (10.14)

Topic

[Jon Mitchell]

This has happened to me in both Reaper and Pro Tools (I thought I was going nuts). What I have found is that (especially if you are using one of EZ Keys’ grooves/midi files) the MIDI hold information is still on the file. Haven’t used Abelton but in Reaper’s MIDI window, you can go to CC 64 (Hold Pedal) and delete the values. Then it won’t sustain.

EZkeys version: 1.3.0
Operating system: Windows 10

1

Thanked by: csonc

[csonc]

Appreciate this, but it’s still not addressing the actual issue of this application randomly inputing a CC 64 when I am not telling it to and it brings to light a flaw in this application.

Within my DAW the only way I can address this is by dragging the MIDI outside of the MIDI track that has EZ keys on it into a new MIDI track not using EZ Keys and then input a CC64 message. That’s the only way to get it to not sustain.

In standalone mode there’s no way to address this issue, it just behaves how it wants, generating a CC64 by default with no way to tell it not to.

This issue only occurs when I create new segments. When I use the groove MIDI files it works as expected.

I do appreciate the input though Jon and you;re time in replying. So far you’ve done more then the actual company I gave a chunk of my money t, so I do appreciate you 🙂

Hopefully someone from Toontrack will actually respond as these forums seem like the only way to get support, if no response is available then this simply highlights another major flaw in this company (a more foundational one I’d argue) and I will consider the money I spent a sunk cost and just move on and wash my hands, my time, and my frustration clean of this company.

[Scott]

Can you attach a zip file of the EZkeys project file where this occurs so I can forward to the programmers? I have not experienced random sustain pedal issues personally.

Scott Sibley - Toontrack
Technical Advisor

1

Thanked by: csonc

[csonc]

Sure! Appreciate your efforts in this Scott. The zip file contains two simple projects (one for Mellotoon, one for Studio Grand), both projects contain one chord from a segment I created (so not using the groove/MIDI files).

EZkeys version: 1.3.0
Operating system: macOS Mojave (10.14)

[Scott]

csonc wrote:

Sure! Appreciate your efforts in this Scott. The zip file contains two simple projects (one for Mellotoon, one for Studio Grand), both projects contain one chord from a segment I created (so not using the groove/MIDI files).

EZkeys version: 1.3.0
Operating system: macOS Mojave (10.14)

Ok. I forwarded this post to Toontrack Tech Support. I’ll let you know when I get a reply or perhaps they will reply to this thread directly.

Scott Sibley - Toontrack
Technical Advisor

[csonc]

Thanks again Scott. I appreciate your efforts in this, no matter what comes of it. Have a good day 🙂

1

Thanked by: Scott

[Author]

Replies