Digitakt 1.30 : Bug reports

I’m noticing a bug with the PRE/-PRE trig conditions. I have a snare on steps 13 of all four pages. I have the same snare on step 14 of all four pages and it’s microtimed to start at 13, and also has the delay knob plocked. The snares on 13 are currently set for 100% hit, and the ones on 14 are set for -PRE, meaning they shouldn’t play at the moment because of step 13. Unfortunately, that is not what’s happening. The snares on 14 play anyway. No matter what I do, what trig conditions I change or remove on either of them, I can’t get it to work. I want to make it so the 13 steps are at 50% probability so that when they don’t hit, the 14s with the delay plock are triggered. It happens on all patterns in my project.

I created a new project and it works fine, so I’m thinking it’s a bug in reloading old projects perhaps.

There is currently a bug where if you change PRE/-PRE while the sequencer is running you can more or less cause them to act in opposite of how they should, hopefully it will be ironed out soon. I think this is possibly the same bug you are running into here.

2 Likes

Digitakt 1.30 Overbridge_2.0.58.8 + Ableton 11 sync problem

Since the latest Overbridge and OS upgrade of the Digitakt i have a strange problem.
When i drag Digitakt or Analog Heat from the Ableton browser into a miditrack both machines are out of sync .
But, when i drag the whole track to a random track of session view the machines sync.

edit:
So , drag > drop to a midi midi track = no sync
Drag whole track while running to the anywhere of session and release = sync.

Update: After some testing saving a project in ableton, opening the project everything starts out of sync again, clicking a couple of times on Live stop button resets the sync.
So my guess is overbridge does not get a proper reset command when loading the plugs into live.

Edit: Waiting for Support , asked for version 1.20A to go back,

there is a 2.0.59 out there

1 Like

Had an issue last night where I was copying parts about and some key combo faused the FUNC key to be metaphorically stuck down, needed to reload project to clear it or everytime I pressed play it would try to clear the pattern.

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. :kissing_heart:
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. :smiley:

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. :frowning:

I’m also hearing a lot of digital clipping with the EQ filters.