- Func + Clear clears sequence for me too. In live recording mode, Func + Clear immediately after displays “undo Pattern Clear” and does just that, however in play mode, it displays “undo Pattern Clear”, but doesn’t actually undo the pattern clear (well, occasionally it does).
- I have the same issue as jcd. always left with one trig. I’m actually always left with the trig that was active when i relesed the No and Trig key.
Yeah, it happens on Global Mute (the green mute in case I got them confused)
I ll check that today.
Oh that would make sense. I’ll try that out. Thank you.
Can you put in a support ticket number 1. They couldn’t replicate it so the more people report it the better.
Ya
i just fiddled around a bit and somehow I managed it not beeing able to mute a track. all buttons lighted full green ( func+ bank) but tapping any of teh green did not changed anything. dont ask me what I have changed. bug or is there something to keep aware of ? reloaded my project I could mute tracks again
Hi there!
New to this forum, but after updating to Digitakt 1.06 I noticed a weird bug that only happens to one sample (check video for reference: https://youtu.be/jvi4tsgLonY).
So page 3:4 should sound identical to page 1:4, but after the trigless locks from 2:4 the sound changes. This is because of a sample that’s being triggered from different starting points. So on page 3:4 it should go back to the starting point from 1:4, but instead it’s stuck on the starting point from 2:4…
I hope this makes any sense, and I hope there will maybe be a fix soon as I didn’t have this issue with 1.04.
Thanks!
1 Like
That come from the new behavior of triglocks since this os.
That make me sicker than before.
Basically now by making trigless trigs(yellow) u will hear as is all sounds parameters that have been locked on the previous red trig on the whole loop, till u relock on them on a wanted value on a next step. So if u do yellows that don’t change a parameter that have been locked on the previous red but other stuffs, relock them too directly on yellow one or soon after.
They haven’t fixed anything about triglock behavior, they just deported the issue
This works fine for me. Trying it with soft synths on my iPad each parameter lock sends a new cc level that is there until the next change. It doesn’t matter if I have no default value in the track or if I set a default value.
I think the secret is to remove the default value on the FLTR page, so it is an X, The it will only respond to the locked trigs.
Here a video of what i complain about triglocks behavior. They succeeded to fix the issue about note vel and lenght changes, but me and others told them that the issue affect every sounds parameters.
3 Likes
Not sure if this has already been posted…
When I do Reverse Loop or Forward Loop with a sample the envelope doesn’t really respond as it did in 1.04. The loop points in my previous projects are all of a sudden very clicky when it cycles either manually or via LFO.
Am I just imagining that it was smooth before or is this a 1.06 bug?
This may be the same issue as Ymsey posted above…?
There’s some weird stuff going on when using the yellow trigless trigs in my patterns. These trigs have no param locks on them - they’re new, clean trigs – but they screw things up if they follow an existing note trig that contains param-locks. It seems that the trigless trigs keep the settings of the preceding param-locked note trig, rather than ‘letting go’ of the temporary changes. It’s much easier to show in a video… (please excuse the unsync’d audio/video and my garbled terminology!)
(send to support)
2 Likes
hello guys, I’m new here, and my only experience with de DT is 1.6,
I found a lot of bugs, this automation problemb Garf just talk about, the CC strange behaviour if you do not put off the CC pots on filter page after automation; sometimes my unquantized trigs live recording are not rec…
anyway, tell me if it was so buggy in 1.4 ? I mean, I know about midi crach etc, but for 1.6, one year old start production machine, i found it very buggy, and it’s annoying, because i like it sound…
the yellow triggers, are for the automations, have you not automated something?
nothing automated. new “clean” trigs, as mentioned.
I haven’t found 1.06 to be any buggier than 1.04, and I do prefer the encoder sensitivity adjustments and other improvements.
Though I’ll admit I am very gentle with the DT - I don’t ask much of it other than as a sampler, drum machine, and basic MIDI sequencer. Occasional parameter locks and conditional trigs. Rarely do I use trigless trigs as I don’t really use long samples.
Any heavy lifting MIDI wise I use a proper event-based sequencer.
I had this same issue,
Worked on a track, resampled some hi-hats and kicks trough a pedal. -> named them, assigned them to a track, saved everything correct.
Came back an hour later to see that the samples were not only missing from the pattern, + the project list(now there was just a ----- where the sample used to be (named correctly). But also in my +drive in the section where you find the “recorded” samples they wore gone.
Strange thing is that not all samples were gone, 3 of 4 were missing.
I can manage to re-resample those drums, but i don’t think this is normal behaviour so thought i’d share it here.
It’s so cold in the uk , the coldest country on the planet , the bestest cold in the history of the universe.
An early March firmware update would melt our hearts , and the snow.
Come on elektron !!! , it’s spring time.
Boing.
Ok, new bug here. It’s about unquantized live recording mode
Sometimes a double trig on a kick is not record
so aonnying
I Could write it in step mode (first kick on the grid, and the next one in -1/32, but it should works with the live recorde mode…
Do you guys have this one ?