What could suddenly stop DP from recording CC 64?

[FMiguelez]

Hello.

I have 3 sustain pedals, and now none of them work.
I've checked both, the Input and View filters, and they are set correctly.

DP plays the sustains correctly if manually drawn, but won't record them live with the pedal.

Does anyone have a suggestion for me to try? I'm out of ideas

Thanks!

[stubbsonic]

Is it possible that in DP you have inadvertently set up your CC64 to perform some other Command/function? I don't know if you can search commands for a MIDI source. Might take a while to search manually.

Another thing to check is to see if the keyboard itself has some way of disabling the pedal.

You've already checked filters.

Are you using Keyboard Maestro? Any possibility something in there is messing things up?

[cuttime]

Have you used #64 lately? There is an old bug in DP9, (I put in a techlink on this for DP9.1) that sustain would be recorded, but not patched through, i.e not heard. Not sure if this is related, but but there are a number of threads about this that are a few years old. I remember this being fixed in a later iteration of DP, but I don't recall exactly what version. Are you sure the keyboard is generating #64? If not, https://www.snoize.com/MIDIMonitor/ to the rescue.

[HCMarkus]

I have had an occasional issue with CC64 still. Once in a while, my first CC64 ON message will get missed on layback if, after performing the part, I enable quantization on the track. Work around has been to put the CC64 ON message on a separate, unquantified track addressing the same MIDI Input.

[FMiguelez]

Thank you so much for your help, guys.
I think I found the problem, but I don't get it> it's the MIDI keyboard.

So all 3 pedals work fine with the Fatar, but I'm retiring it because some keys don't work anymore. But none of the pedals work on any of the 2 Novation keyboards. How can this be?
The CCs get sent properly, but the keyboards simply ignore them as if they didn't exist.

One of the pedals has the polarity reversed (which can be easily adjusted with the Fatar), but it doesn't work either.

I've RTFM, and there's nothing in there indicating anything about the sustain pedal.

What do you think it's going on?

[stubbsonic]

I'm sure you're aware of this, but I'll mention it for others who find this thread. Some keyboards will scan the switch-pedal inputs when powering on to determine switch polarity (normally open vs normally closed) so you can use either type of pedal.

I have a Zero SLMkii, and when I load the config software and start a new template, the sustain pedal is disabled by default. I have to go and assign CC64 manually. I like that behavior (where it doesn't automatically assign anything to any CC). I can't imagine that would be the case for using whatever "state" it loads, but it's worth running the config and confirming that both keyboards have their pedal ports configured correctly.

[FMiguelez]

I have a Zero SLMkii, and when I load the config software and start a new template, the sustain pedal is disabled by default. I have to go and assign CC64 manually. I like that behavior (where it doesn't automatically assign anything to any CC). I can't imagine that would be the case for using whatever "state" it loads, but it's worth running the config and confirming that both keyboards have their pedal ports configured correctly.

I think that's exactly my issue, Stubbs!
I have that exact controller like you and the SLMKii with 5 octaves.

If I may, how exactly do you assign it manually? Do you mean in Automap?

Also, it beats me why it would be disabled by default...

[stubbsonic]

The app on my Mac is called SLMkIIEditor.app.

The sustain port is shown on the front panel (not in a very intuitive spot-- relative to the rest of the layout).

I double-click on the port and it opens the assign pane for that control source.

The reason it was unassigned in my case was because I was starting a completely blank configuration. As to why it may be disabled on your unit might have to do with someone who was not using the unit for traditional MIDI stuff. Or you just chose a template that was "unlucky" in this regard.

Hopefully that's your fix.

As a side note, I've kept my eye on an SL Mkiii because I imagine what better, more accurate velocity measurement might be like. It's overkill with all the CV stuff and LEDs I'd never use, though.

[daniel.sneed]

[...]As a side note, I've kept my eye on an SL Mkiii because I imagine what better, more accurate velocity measurement might be like.[...]

It's under my magnifying glass too. But I've heard Novation dropped Fatar keybeds with SLMKIII. Not sure any other brand can compare in keybeds.

[stubbsonic]

[...]As a side note, I've kept my eye on an SL Mkiii because I imagine what better, more accurate velocity measurement might be like.[...]

It's under my magnifying glass too. But I've heard Novation dropped Fatar keybeds with SLMKIII. Not sure any other brand can compare in keybeds.

Thanks for that extra bit of info. I'll watch for reviews more carefully for action/feel.

[FMiguelez]

The app on my Mac is called SLMkIIEditor.app.

The sustain port is shown on the front panel (not in a very intuitive spot-- relative to the rest of the layout).

I double-click on the port and it opens the assign pane for that control source.

The reason it was unassigned in my case was because I was starting a completely blank configuration. As to why it may be disabled on your unit might have to do with someone who was not using the unit for traditional MIDI stuff. Or you just chose a template that was "unlucky" in this regard.

Hopefully that's your fix.

Thanks, Stubbs!
I still use Automap for the SLMKii's, so I'll check what that app you mentioned is all aboot and try it oot