Can anyone give me info?
Like i mentioned in this tread OS 1.30 gave a lot of issues. I opened a support ticket yesterday to ask for OS 1.21A , but no reply yet. I found a link in a tread with the previous OS Old projects sounding different after 1.30 update and how to solve it - #12 by maerteijn
I downgraded the OS , and had no sound, reloaded project and it’s ok.
But now when i boot the digitakt it shows a E in the left corner in the boot screen.
I don’t recall seeing this ever, my intuition says E of error? What does this mean? The Digitakt functions normal.
I don’t know about your main issue but don’t worry about the E - it doesn’t mean Error at all.
2 Likes
More like a few observations;
- Trig Note still does not go higher than +24, meaning that if you use a single cycle waveform, for example, and pitch that down to the extended range you will not be able to extend the octaves in chromatic mode. Seems like a major oversight.
- EQ filter clips (sort of, sounds like something is wrong) almost immediately when gaining or attenuating, doesn’t seem that usable to me. Feels like a bug, but might just be that the EQ needs more headroom.
- Dual switch icon breaks the layout on the Master External Mixer page, I would love to see a vertical one instead.
19 Likes
Well that’s weird. It’s pretty much unuseable as an EQ. Fine as a narrow range clipper effect though, but is that the point?
Hehe ok, I’ll submit a support ticket. Haven’t done that since 2015. 
19 Likes
I had extreme weird sounds at first with EQ but it disappeared on reboot and I have not been able to reproduce them. I thought it was because of beta ^^
Can you reproduce this after reboot on a brand new projet as well?
2 Likes
I reported a bug related to sync between devices. This was their response.
4 Likes
Hi,
The EQ filters distort very badly. Especially audible on non distorted kicks and sine-like sounds. Even when you apply band reject the signal distorts. For me they are currently unusable.
Submitted a ticket.
4 Likes
Also weird.
Yeah, sure can.
2 Likes
does anyone else also has sync issues with latest OB and DT versions on ableton live 10 ?
I have a digitone running in parallel and no sync issues with that one.
I raised a ticket but i don’t know about their reactivity on weekends
Look into this tread , i have the same issue.
Anyone having any luck using the second lfo to modulate the speed of lfo1, I cant rule out lack of understanding but when I played with it there seemed to be no change to the sound.
You’ll have better results modulating the depth. I had fun with this tonight ^^
My Digitakt just became less LoFi hip-hop and more Æ nonsense suddenly ^^
4 Likes
I did some listening and you are absolutely right about the clipping. I noticed it mainly with the EQ1 and 2, the others sounded cleaner, but I am no expert. If I were at home I might hook it up to the oscilloscope to see what is going on. Definitely weird.
EDIT, maybe the others are just more subtle in their clipping. I actually kind of like the frequency based clipping, but I have been trying to make harsher sounding tunes lately.
1 Like
Same issues on Live 11 and my friend is experiencing this as well. It looks like the OB plugin is no longer reporting latency to the DAW so Ableton can’t compensate for it.
This really sucks for my workflow and I hope Elektron fixes it soon. I’d downgrade my OS if doing so were supported.
Edit: It seems like PDC comes back if I right click it and click Group. That said, saving the resulting Instrument Rack and adding it to a project from the Browser doesn’t work. This is definitely busted. 
I’m also hearing a lot of digital clipping with the EQ filters.
I just had a very strange and very frustrating bug where MIDI data from one single pattern is now sending out on every pattern despite those patterns’ MIDI tracks being turned off and cleared of all settings and sequencer data.
I recently setup my Digitone and Digitakt in a bi-MIDI relationship where
- MIDI tracks 13-16 on DT control Audio Tracks 1-4 on DN
and - MIDI tracks 1-4 on DN control Digitakt audio tracks 5-8.
In a nutshell, I have DN MIDI track 1 and 2 sending sequencer/LFO data to DT Audio tracks 5 and 6 on Pattern 9. This works exactly as it should (basically opening up the high hats via Amp release and increasing the Bit crusher on the other track). But now, despite all MIDI tracks on both machines “purpled” out (I.e. pattern muted) and cleared of all MIDI settings (no channel assignment, no CCs, etc…) for every single pattern other than the one I want to actually work, the exact same sequencer and LFO data is present on every pattern.
It truly is mind boggling. I know it’s external MIDI data as the knob graphics on the screen are moving which of course doesn’t happen when it’s internal sequencer data as well as I removed the DN MIDI out to DT MIDI in cable and it stops the issue.
This is not a case of MIDI loop as there are zero issues other then this one strange thing happening and I carefully selected MIDI channels so that there is no overlap.
Tried power cycling and the issue persists. Will try a new project I guess but that will be extremely frustrating to lose a whole project because of this.
Not sure if this might be new DT OS related as I just set this up right after updating DT.
2 Likes
Yep, just tested the new EQ filters and they distort something crazy, even with negative values 
I‘ve had that happening somewhat regularly with a Digitakt having a MIDI LFO going to another Digitakt. The LFO would just keep going when switching patterns, even though the corresponding MIDI track was empty in the new pattern. A trigless trig on the – now empty vanilla (?) – MIDI track would stop the LFO, but maybe still overwrite the previously controlled parameter value, wherever the LFO just happened to stop.
I don‘t know if this is the same case you‘re having, but maybe it helps.
It’s not a big deal but updating seems to clear some of the midi settings. My Digi has started sending pattern change again.