Midi fighter twisters with Digitakt

Hi, I have succesfully set up my digitakt with my two midi fighter twisters and have programmed all of my favourite parameters to work with the knobs. I am using a raspberry pi that has been set up as a headless usb host and it works great. The digitakt is set up so that any changes I make on the digitakt are seen on the midi fighter and vice versa.

Everything is great, unless I change patterns. If I change patterns the new midi information for all the parameters in the new pattern are not updated to the midi fighter. I can’t see the settings just by looking at the twisters and there is a audible ‘jump’ in the parameter when I change them if there is a significant difference between the two devices.

Does anyone know how I could set up the digitakt to send all the new midi parameters when I change pattern etc?

Many thanks,

2 Likes

You cannot.

2 Likes

The only Elektron box that can send all parameters to a midi controller is the Octatrack. :slight_smile:

3 Likes

Thanks for the confirmation. It’s a shame.

I’m really surprised by this. This seems like baseline functionality for boxes that deal with multiple patterns.

I’m no longer surprised by what features Elektron leaves out of their boxes.

Could you try enabling global FX/MIX for the project? At least you would have a bunch of useful controls to break out to the twister that would be consistent across patterns. Disclaimer that I didn’t try this myself.

Downsides being limited to just effects and mix settings and no unique settings for any given pattern, also likely a mismatch after changing projects.

I would actually prefer support for relative midi on the digi boxes, but that is another story.

Just ask for midi dump CC in the topic below and pray :wink:

Hi, good idea. It should be relatively straightforward to make it work.

After a few days of trying to get the midi fighter twister to work with the Digitakt I thought I’d write up all that I’ve learned so that anyone searching on this topic in the future has the info.

I would not recommend buying a twister to work with the digitakt. With the current limitations of the Digitakt and twister the experience is frustrating and unpleasant.

It is possible to map digitakt parameters to the twister. The two devices speak to each other so changes (to track parameters) made on one device are reflected on the other. However for some reason the digitakt does not send midi feedback for the global parameters (compressor, reverb, delay and mixer). This means for tracks you need to go through all the menus and tweak the knobs on the digitakt everytime you turn on the device or change pattern/project; there is no midi parameter dump from the digitakt to update the twister (the octatrack has this function on cc 61). For global parameters there is only one way communication so you have to tweak the knobs on the twister for every parameter when you turn on the digitakt, and if you change parameters on the digitakt they are not reflected on the twister.

Finally, it’s not possible to make the switches on the twister work in a satisfying way with the digitakt. The twister has animation and brightness CCs baked into some of the midi channels that cannot be turned off. As the digitakt uses all 16 channels for its 8 audio and 8 midi tracks whatever you do there is cross talk between the two devices causing strange led changes when you hit switches.

My wish list of updates would be for Elektron to include a midi parameter dump similar to the octatrack and enable midi feedback for the global parameters, and for DJTT to update the twister firmware so you can turn off the animation and brightness CCs. If this happened then using the twister(s) with the digitaky would be delightful. For now I’ll plug them back into ableton.

I now plan to focus on what the digitakt can do and not what it can’t. Thanks to everyone on the various forums who helped me try and make this work.

10 Likes

Thanks for the write-up! I also have two twisters, which I’m looking to use to control octatrack parameters. I got a raspberry pi to act as a USB midi host.

The big buzz kill for me has been the inability to remap knobs on the fly, like faderfox controllers can.

There’s a project called Muffin to write an alternate twister firmware. You may want to submit a feature request there. I already filled one for on-device knob assignment editing (~bxzn/Muffin#12: On-device knob assignment editor — sourcehut todo).

1 Like

This project is great ! I sold my twister because of the absence of firmware updates (program change, editing start/end values …).
It could be make me buy another one :yum:

The Muffin project seems to be abandoned. Too bad !

1 Like

Thanks for this update.

I have a Twister (for use with software), and was wondering if it could be used to control the DT.

Would a Faderfox be better suited to this sort of thing?

such as this one: Faderfox PC4

Sorry for the super late reply. Yes you can use the twister o. The DT. You need a midi host between the twister and the DT though.

This thread saved me hours, thanks! I can’t believe the XL is a better controller than the twister in this regard. As a mixer and FX controller I am getting what I need from it, I even copied octatrack’s Freeze delay behaviour on the bottom 8 buttons mapping time parameters to each one. I even have light feedback on mutes from and to the digitakt, that works very well.

Knowing that the octatrack has dump made me want to dust the thing and try the twisters with it.

DJTT will never update this, nor give any kind of customer service.

I used to have a Twister, but upgraded to a Faderfox EC4. If you have any chance of doing this, do so. What an improvement! In this case it also directly links thanks to the midi out/in.

Would you say the EC4 was an upgrade to the Twister in terms of using it with hardware gear (midi outputs) or in general?

What do you prefer about it over the twister (display aside)?

I‘m debating between these two, but mostly for DAW use, hence questions.

Thank you!

the only downside I have is that lack of visual feedback on the knobs itself. Other than that I personally experience the following benefits:

  • Knobs feel better (but that’s personal)
  • All buttons on the unit itself instead of on the side
  • Labelling the knobs is just so much better than color coding them
  • better mapping application
  • Midi in/out
  • Way more technical options when it comes to defining your knobs and buttons, to accommodate all requirements a synth or software might have
  • 16 groups of 16 knobs directly available, in 16 setups.

It’s 1 setup per application (that’s how I use it at least). So I have 3 setups currently: Traktor, Ableton and Digitakt. And within those setups I have 16 groups of 16 knobs. So take ableton as an example. I use it to map the send fx. I dedicate 1 group per effect. These are directly available despite a few on seperate return channels and a few direct on the master.

Considering the difference in price point (about 100 euro’s more over here) it’s really a no brainer for me.

1 Like

If you have any specific questions, just let me know, more than happy to go into detail (and I’m not even getting paid by faderfox :joy:) I’m just so enthusiastic about this thing.

1 Like