Hello, i‘m quite new here, sorry for any obvious lack of knowledge 
Talking about ‚waiting with the upgrade‘ and making a backup: the ‚new way’ of making a backup sounds awesome with Transfer 1.4. but i need the latest OS for that.
So what would be a proper (and SAFE!) way to backup my whole DT how it is right now without Transfer 1.4?
Thx guys.
Typically these EQ cutting/boosting tools are made by adding or subtracting a bandpass signal onto the original signal.
It could very well be a headroom issue in the bandpass itself, that translates onto the combined signal – “could”, who knows, there are many things going on in digital IIR filters, the distortion could be coming from a lot of places.
Before Digitakt OS 1.21A there wasn’t an easy way to do a backup. You can try ELK Herd, which is a third party tool.
You can also upgrade your digitakt to 1.21A first and use the new transfer 1.4 to backup your digitakt projects before going to 1.30. (Tip: save your projects in each revision of the os, and also make a backup of the projects in each revision of the os).
I think the ‘E’ is the bootstrap (bootloader) version.
Do you see the same results when you record the Digitakt using the digital USB output? (Just to rule out any external factors)
Can anybody please tell me if it’s a feature that LFO still gets sent from MIDI track if it’s muted? Or is it a bug… 
Hmm… or it had to do with global mute mode and pattern mute mode… do they operate in parallel?
Audio from iPad over USB clicks – it’s also in the recording.
I wouldn’t trust the waveform display on the Digitakt to make that conclusion.
EDIT: (I assume it takes the sample data and squeezes it into the available pixel space)
Thanks a lot, didnt know that 1.4 works with OS 1.21A! Can you explain in short what you mean with the revision-tip!? Is is some sort of option while doin the backup? 
Haha yeah I suppose you’re correct… I loaded in a sine wave from hardcore and it looks exactly the same on the digitakt screen.
So you keep backups of your projects for each revision (version) of the os.
Ah ok, now i gotcha! Thanks!!
I guess i will wait with 1.30 though… and see whats discussed here!
On a sine wave I am hearing the clipping go away with full negative gain once the sample level gets turned down to about 49 on EQ1 but it is quite low at that point given you are also taking away volume with the EQ.
After updating my DT to 1.30 I’ve noticed that the there is something wrong with the LFO and the trig conditions.
I put a trigless trig at the end of the 2nd bar of a 4 bar pattern, and used it to create a filter sweep using the ramp LFO wave.
No matter what trig condition I select (1:2, 3:5 etc) the LFO triggering the filter seems to not follow the trig condition. So for example the filter sweep will be activated under the 2:2 condition even when the condition is plocked at 3:5.
Anyome had similar behaviour?
Damnit, I can’t keep myself away from things like this!
Ok so, few findings:
anasine through the octaves – clean, then with eq1 (100 freq, -64 gain)
Just to see if I can reproduce it as well: what tool / software are you using to create pictures like this of the output of the digitakt?
anasine is the wrong sample, the pure one is called sine.
It’s still a sine, almost, but it might have some distortion by default.
This isn’t low level distortion with sine only. It distorts with many samples containing low freqs. This is another example.
also noticed it with the compressor… but that might just amplify the (or another?) problem
