Sustain pedal in keyb lru object

#1

hi there,

is it intentional that midi sustain pedal (cc64) is not implemented in the keyb lru object?

what would be the cleanest way of adding it in? (in the patcher or the object itself)

cheers.

#2

and i solved it already...

cc64 in to an inv object and then straight to rbrt/gate i object. connect the other input to the gate of your keyb object and the output to your adsr.

nice and easy.

#3

have you gotten this working with a polyphonic patch? I've been able to get my sustain pedal working with mono, but poly is causing all sorts of weird behavior.

#4

i never tried with a poly patch. but how is the lru object supposed to work in a poly patch? it kind of is only useful for mono patches, no?

#5

Right, maybe this should've been a new thread. I was just thinking about sustain in general.

I found an inefficient workaround -- the cpwitz/midi/arpeggiator "hold" function does exactly what I wanted. Keys that are being played stay frozen when hold is engaged, and my envelopes take over when hold is disengaged.

My patch has 8 voice polyphony, and it seems to be handling it with no problems.

Do you know of a way to do this without the arpeggiator? I've experimented with some "note hold" objects to no avail. Currently at 95% DSP -- it would be nice to slim it down.

#6

i always thought the "normal" midi in keyb does already respond to sustain. have you tried that?

#7

sustain (CC64) is done in the generated voice allocation code , not in individual (e.g. keyb) objects.
(basically the sub patch will not get the note-off until the sustain is released)

#8

Duh, yes, it's working fine.

The problem was that my sustain is being generated from a toggle switch I wired to my keyboard's sustain jack (I find those pedals incredibly annoying to use live). I wired it incorrectly initially -- didn't realize the jack was a switching jack. I'd tested continuity by using a 1/4" cable that was plugged into the jack -- all was working fine on the bench. When I tried to use it (without the cable plugged in) the switch was open and it was no longer shorting correctly. I assumed it was a software problem, but it was a hardware problem. At some point, I realized that and fixed it, but I'd already written the patch and started software troubleshooting.

Thanks for your comments -- helped me figure out that this was a case of user error.

#9

Sorry for resurrecting this thread, but I just run into a problem with a patch of mine and this seems to be the reason.
Is there a way to disable the CC64 sustain behavior in a (sub)patch completely? I have 2 axo's with 2 midi controllers running in series and use CC64 for another parameter.

#10

well the short answer is don't use CC64 for anything else, it is in the MIDI spec that CC64 is used for sustain, every midi synth should understand it, and i think every hardware synth i have uses it and you cannot disable it.

the answer from @thetechnobear tells you that this is a firmware "issue" rather then a thing in an object, so chances are very slim to have this changed easily.

#11

Yeah, I suspected as much. It's not a big deal to change the MIDI mappings and now I know about an additional feature of subpatches! I guess CC1/mod wheel is also automatically included in the subpatch code? Do you know any others I should look out for?

#12

All Notes Off, MIDI CC 123

i don't think CC1 is mapped by default.