One thing that’s really frustrating to me about the DT is the sensitivity of the encoders. If I’m trying to shoot a particular value - say, 7.5 - I feel like I go above and below it a thousand times before I can actually get it to land. This is getting old, and it seems like something that could be avoided with something with knobs. Is anyone using the Beatstep Pro with the DT? If so, are you able to map the knobs to the encoder functions or is that off the table? Seems like they would be a good pair, just wanted to see if anyone else had encountered this before I dive off into the rabbit hole.
i have the same with my second DN, on one page it is too sensitive, and on another page that same encoder does nothing when turned slowly, bit harder and it jumps for example from 78 to 80, bit annoying to work with but think we have to live with that, don’t think you can just change that with an os update as not all units have this behaviour, my first DN did not have this, but the encoders were more loose, almost wobbly. Hope that it will change when using it a lot.
Yes you can map functions to encorders of the beatstep but you don’t need to buy a beatstep for just turning a few knobs! Maybe some other gear laying around can do the job also.
The beatstep and beatstep pro can be used in conjunction with the dt. You would set the beatstep midi channel to the dt auto channel and the map the beatstep knobs to parameters you want to control. The problem you will run into is that the beatstep has only 16 knobs which only takes care of two pages of parameters on the dt. I do not remember off the top of my head if the beatstep has knob banks.
Additionally if you map the beatstep pads to send midi note numbers 0-7 you can trigger the tracks 1-8 on the dt with the midi pads.
The mpd is also good for this.
I would go regular beatstep or mpd. Used should be less than 100$ for each
Ah, I see what you mean…from looking at the MIDI spec, there’s no way to tell the DT “always map this knob/CC to whatever encoder A/B/C/etc is at the moment”, you have to map each individual function per page, per knob. That’s a LOT of mapping.
I do find many values don’t need the accuracy that’s available ( delay time of 23.56 instead of 24 ? ) … and yes I know the options available with digitakt button combos to snap to certain values.
The worst offender on my machine seems to be midi notes , one of them will jitter between notes ( I think it’s note 2 ) very frustrating to get it settled on a note , worse to get it on the note I want it on. It seems to be worse recently but I don’t know if it’s firmware or hardware … it’s hard to believe the firmware / code that controls encoder control / acceleration would be prone to bugs or become broken at this point. .
I’ve tried using external controller setups , midi designer pro on iOS is good for this , but day to day , when actually mangling music its much more tactile to use digitakt.
If can sometimes become so frustrating that I just turn the gear off. Or avoid using chords .
Maybe it needs bigger encoder caps ( the lump of rubber on the metal shaft )
