I came up against an odd one I hadn’t noticed before at the weekend.
With the sequencer stopped and any sample track selected, when I went into chromatic mode, the record button became inactive. I couldn’t start real time (or step recording although that makes some sense) from that state and had to come out of it, start realtime recording and then switch to chromatic mode. Maybe this is by design but it just felt awkward to me.
In my case, the support initially thought the auto-save function was defective and that it was due to a capacitor. When I explained my problem in more detail (see above) they said it was “unheard of” and offered me to send in the digitakt or try to recreate the problem myself. Unfortunately, none of this is an option at the moment, so I make a backup every two days 
I have some Digitone LFOs assigned to a track on the Digitakt. When I just recorded some external audio (not from DN) into the DT and previewed it before saving, the Digitone LFOs were low pass filtering the preview? Is this a known thing? The filter sweeps didn’t end up in the recording after saving. When I turned off the Digitone, the preview filtering stopped happening.
Unsure if this is to do with the OS update, but first power-on after updating, trig buttons 4-8 weren’t working for me at all, completely dead. Power cycled and disconnected USB, they’re all now fine. 
EDIT: Had this occur to me again on two different power cycles yesterday. Went into Debug mode and all the buttons worked fine, power cycled again and the buttons were all OK again. Feels like it’s less of a hardware problem and something weird’s happening in the software.
I miss Elk Herd! can’t fetch projects anymore…
My Play button is not lighting up 
it is still working though 
Not sure if it’s a bug, so correct me in case I’m wrong:
Usually, red [TRIG] on sequencer + [YES] fires up sample and all its setting on that specific step.
However, in conjunction with activated RETRIG option, [TRIG] + [YES] gives silence.
I don’t remember the exact implementation of that logic on previous OS versions, but it seems pretty obvious that you want to be able to prelisten retrig settings simultaniously on isolated steps rather then loop the full sequence to listen if the settings match your expectations.
retrigs have never been auditionable with trig+yes unfortunately
Not sure where to post this since I don’t see a bug thread for 1.51. After upgrading I now hear a pop/click when sampling. It happens through Analogue ins and usb audio. The click is always in the same spot, about half a second into the recording. The source has no clicks, there is no clipping, etc.
Is there a place where I can get 1.50A firmware so I can downgrade?
I noticed the same thing yesterday and was wondering why I couldn’t get rid of it.
Just copying this 1.51 bug here FTR, steps to reproduce are linked below in source topic
I have reported this now … I’m fairly confident this is a bug - there are other users discussing clicks and i tried my steps on a new project
It’s not every time, but the majority and always in the same location afaict
somewhere just under 176 ms … it is not extra samples, it is nulled samples in two positions
EDIT: In case this is a surprise to Elektron, for clarification, i am running the lights off {cog+9} mode in 1.51 and there was no transport - literally minimal steps from a new project
only mentioning the LED setting (as little else changed in 1.51) as it may interfere with the ux in some way resulting in issues elsewhere as i suspect that there has been no changes to the sampling … but it’s definitely clicking and it’s not user error, may relate to rlen ?!
When I play audio through the usb of my digitakt feeding into sp404mkii it sounds like its phasing or something. Levels dropping and getting louder almost like there is a compressor on it. Especially recognisable when listening to speech. Direct out of digi is fine but when I switch it to play something off YouTube its weird. Using unbalanced cables for the ins of sp404 balanced going to my speakers. Persists even with balanced cables. Anyone else experienced this I’m sure its a usb issue.
bingo ! - bizarrely, literally a minute after i posted this, it was confirmed as such in the response to my support ticket, it has also already been fixed for the next release, no idea when that will drop though !
I’m seeing a weird behaviour when using sound locks that contain a different machine than the relevant track is using.
Not sure if it’s a bug per se, but I’m pretty sure Syntakt doesn’t do this. Basically, when holding a trig that contains a sound lock, it’s LFO parameters can’t be p-locked further because the LFO targets are scrambled, it shows the default targets for that tracks default settings.
For example, track contains a one shot machine but you sound lock a sound that uses a slice machine. At this point it’s fine, but if you try to adjust the LFO settings on that trig, you see targets for a one shot machine rather than a slice machine.
Yes, I p-lock too much 
My clock doesnt stay steady when digi is used as “slave”. If I cloxck the digi off of anything else (Computer, Trigon 6 etc) the clock doesnt stay put. Say my song is at 165bpm, the clock will jump from m164 to 165 over and over the whole time the song is playing., It only deviated 1 bpm but its enough to throw it off
Its func+yes
thats normal… the clock source is the reason and also the display doesn’t reflect the true time variation.
I’m seeing here in display when clocking from E-RM Multiclock a variation of 163.9 - 164.2.
Maybe check in your daw if you see an actual fluctuation of a short testsample.
My general advice would be, unless it’s really strong and you can clearly hear a difference master vs clocked, ignore that. It’s a rabitt hole. Midiclock is just not perfect.
if it’s really strong avoid midi-merger or cheap midi-thrus and compare different clock-sources. The before mentioned multiclock is a great midiclock-source.
Ok great… good to hear., I figured I was stressing,.
What is?
Would love to hear how this bug came to be with the sampling tbh!