Digitakt MIDI CC Not Working - Parameter Locks Not Sending CCs to External Synth

Hi everyone,

I’m having trouble getting my Digitakt to send MIDI CC messages to my Delta CEP A 2 synth. Notes work perfectly, but no CCs are being transmitted at all. I’m running firmware version 1.52A.

Setup:

  • Digitakt → Quadra Thru → Delta CEP A 2 via MIDI cables (MIDI OUT to MIDI IN) (also tested direct midi connection)
  • Both devices on MIDI channel 2
  • CEP A in Manual mode (required for CC reception per manual)
  • No USB connected to Digitakt
  • Nothing connected to CEP A MIDI OUT

What I’ve tried:

  • FLTR page: Set CC1 Select = 7 (volume), parameter locked CC1 Value to different steps
  • Tested with CEP A’s documented CCs (CC3 for filter cutoff, CC9 for resonance)
  • SRC page: PB (pitch bend) works, but MW (mod wheel) doesn’t
  • Verified MIDI channels match
  • Checked all MIDI CONFIG settings in Digitakt

MIDI CONFIG settings:

  • PARAM OUTPUT: CC (also tried NRPN)
  • OUTPUT TO: MIDI+USB
  • RECEIVE CC/NRPN: Disabled
  • USB CONFIG: Overbridge disabled, USB MIDI enabled

The problem:

  • MIDI notes trigger CEP A perfectly ✓
  • Pitch bend works from SRC page ✓
  • NO MIDI CCs work at all (not even CC7 volume) ✗
  • Parameter locked CC values don’t send when steps trigger ✗
  • Notes + parameter locked CCs on same steps still don’t work ✗

I’ve read about CCs only sending on trigger events, which makes sense, but even with notes + parameter locked CCs on the same steps, nothing happens.

Question: Is there a master CC send enable I’m missing? Or could this be a firmware bug? I’m stumped because the setup should work according to the manual.

Any help appreciated!

Hi.

First try and change output to from Midi+USB to just MIDI and see if it makes any difference.

If you hook the digitakt up to a midi monitor program you can confirm if the CC’s are being sent. If the CC’s are being sent, then the problem is with the other device, or it is user error (no offense).

If the CC’s are being sent and they are correct to what you’ve programmed but they are not being received by the other device, however, note and pitch-based events are, then I would search online and make sure that the CC’s provided by the other company are correct.

In the event that the digitakt is not generating the CC data as expected, I would set up a new project as a test and confirm the behavior there as well. It will give you a chance to go through it again and ensure that there was not a step missed (doesn’t sound like it from your account of things which helps out in trying to help you) however it’s always possible that something small is amiss or that it’s an issue with the specific project.

The fact that the devices are connected and you can send pitch data from the sequencer as note events and pitch bend suggests that they are communicating properly, so what is most likely is that either the CC events are not being sent, or that the CC numbers being used are incorrect.

Let me know if you make any progress.

Good luck

Another thing to confirm is that you enabled the channel parameter on the midi SRC page for your midi track. I assume that you’re saying you’ve sent note events from the sequencer, and not that you’ve just sent notes from the chromatic keyboard using the DT as a midi controller.

If you’re saying that the synth responds to using the trigs as a keyboard, but that you can’t sequence notes or CC events, then you probably didn’t set up the chan parameter on the SRC page which requires you to hold func, push down encoder A, and then release func and release the encoder and use it to set the midi channel for the midi track.

Setting the tracks in the midi config section of the midi setup menu has a different use, so you also need to enable a midi track before it will send data on that channel.

Only mentioning this because you did not explicitly state that you’ve done it.

Thanks for the response! I see that the CC events are being sent from the Digitakt via the MIDI Monitor app.

Also to answer your question, I have a sequence running in MIDI B and its being sent to the CEP A and I hear the notes from the synth so that is working fine. Using Chromatic keyboard also works.

Well, from what data you’ve been able to gather, then I suspect that the CC parameter list of the synth is either incorrect or that you’ll need to circle back and check on what you said was called “manual mode” with the synth which allows CC to be received and see if there’s an additional step or if perhaps the info has been reversed.

You can send a bunch of random CC one at a time until something responds and see if that corresponds to your midi implementation chart for the synth, but it will be a bit time consuming.

If you have another device which can generate CC via midi, I’d start by confirming that the CC as given do not work when sent to the synth from a second device either. One would imagine that this is the case, but it would help to confirm whether or not the synth responds to any of those parameter CC’s.

I’d check out their website and look for any forums that mention the device specifically, and if worst comes to worst you can email the company.

If digitakt is confirmed to be sending CC events, then I believe you’ve set everything up correctly on that side of the equation. The fact that you can successfully send note events suggests that the midi connection is viable and responsive.

The last link in the chain are the specific CC numbers which the quadra thru doesn’t have any ability to filter out so if one were very determined, you could use a usb midi hub to send DIN midi out of the quadra into the computer and through the midi monitor app, but I suspect it’s not necessary.

I’d focus on confirming the CC parameter list for the synth and you could also reference a general midi CC list and try various parameters from that.

At this point I just don’t think the digitakt is the problem. I know that doesn’t resolve your issue but I just mean that I don’t think you have to troubleshoot with the digitakt in mind anymore.

Confirming that the Digitakt is most likely not the problem is very helpful, thank you.

I referenced the Delta Cep A 2 manual here: https://www.radikaltechnologies.com/wp-content/uploads/2023/09/DELTA_CEP_A2_US_UK-1.pdf

On page 55, CC 7 is Volume control so I set SEL1 in CC SELECT to MAIN VOL (CC1 SELECT = 1). Confirmed via MIDI Monitor that those midi events are showing in the logs:

s21:15:29.469 From Elektron Digitakt Clock
21:15:29.471 From Elektron Digitakt Note On 2 E1 127
21:15:29.471 From Elektron Digitakt Control 2 Channel Volume (coarse) 55
21:15:29.471 From Elektron Digitakt Control 2 Channel Volume (coarse) 61
21:15:29.471 From Elektron Digitakt Control 2 Channel Volume (coarse) 24
21:15:29.471 From Elektron Digitakt Control 2 Channel Volume (coarse) 0
21:15:29.482 From Elektron Digitakt Note Off 2 E1 0
21:15:29.486 From Elektron Digitakt Clock
21:15:29.502 From Elektron Digitakt Clock
21:15:29.519 From Elektron Digitakt Clock
21:15:29.536 From Elektron Digitakt Clock
21:15:29.553 From Elektron Digitakt Clock

Still hear no volume automation from the synth

It looks like you need firmware version 2.0 or later on the radikal device for cc control via midi to work. If you’ve already confirmed the FW version I’d suggest trying a CC other than volume. It looks as though 3 is listed as the filter cutoff and that should be audible so I’d try assigning it to a knob and see if it works in real time.

Also I’m assuming you already know this but it looks like you need to exit patch mode by pressing the patch button in order to allow it to respond to incoming CC.

Aside from that you’ll probably need to contact the company for additional troubleshooting. There is nothing that stands out as wrong in what you’re doing.

Good point, I bought it new last November but this one might not have the latest firmware. I’m trying an upgrade now and will report back.

Hope that’s all that it is then.

yes that worked! needed to upgrade the firmware :slight_smile: thanks again for your help!

1 Like

Awesome, no problem.

1 Like

All’s well that ends well :grinning:

This issue comes up now and again so it might be worth just listing some midi monitors.

MIDI-OX - free and does a whole lot more than midi monitoring can send sysex etc etc.

Expert sleepers FH2 - not strictly a midi monitor but capable of displaying midi information. Also has a setting to filter out midi tempo messages which do tend to get in the way.