I just did. I get the expected behavior, provided that the LFO.T is set, not just for the track on both patterns, but also making sure that it is set on the TRIG in GRID REC.
When I go into GRID REC on the second pattern, hold the TRIG in question and turn off LFO.T, then I get the behavior you describe further up.
3 Likes
I just checked the cursed pattern and lfo.t is set on both patterns triggers, I even locked them with a p-lock to try and force it but it still doesnāt work, I seems this project is just corrupted.
- I have an external MIDI feedback loop which sends MIDI output back to MIDI input.
- FX control channel is set to 9
When I change FX control channel to 10 then it crashes when I change MIDI channel of the MIDI track to 10. A quick workaround which is fine for me, is to set FX control channel to OFF.
latest firmware should fix this.
List of changes from OS 1.15 to 1.15A
- Sending Note On/Off messages to the FX control channel could, in some circumstances, freeze the device.
4 Likes
Yes, indeed. I missed the 1.15A and it really fixed the problem. Thanks
2 Likes
LFO bug: āhalfā stops being āhalfā when start phase is not zero. It becomes āstop at phase=64ā. āOneā is similarly bugged.
3 Likes
Thatās how itās described in the manual so I think itās intended behavior for better or worse ĀÆ_(ć)_/ĀÆ
Found a way to reproduce my bug encountered earlier with sample slots.
Saving a pattern to a project does NOT save sample slot assignment. The Kit on the saved pattern will save the track sample assignments but all slots will be empty unless you save the project as well.
Steps to reproduce:
- create new project
- Save project with a name
- Assign new samples into any empty slots. Bank b works as an easy visual indicator
- Program a new pattern with the bank b sample slots. A02 for example. Go to system-> pattern->save to project
- Load a different project
- Choose ādo not saveā
- Load the test project again
You will see that your pattern is intact as it has been saved to the project but your slots are all empty with no sample assignments.
This is problematic when working on new sets where you may have been improvising and working through your live set and do not wish to override the initial setting of the other patterns you have completed and only wish to save the new pattern youāre working on.
I donāt believe the dt1 has this issue as this is the way Iām used to working.
1 Like
I can see that kind of makes sense, since the slots themselves are part of the project not the pattern.
But really annoying though all the same.
I think that justifies calling it a bug 
EDIT: Symptoms Confirmed. While the reloaded pattern correctly points to the right slot, the slot itself is in fact empty.
2 Likes
Awesome thanks for verifying Iām not going crazy! I havenāt been able to get into my account and submit a proper bug report today has anyone else had luck getting signed into Elektron.se?
2 Likes
Probable wavetable bug:
I think Iāve found a weird bug in 1.15A, in that itās specific to Track 12 - it doesnāt seem to handle MIDI Machine properly and doesnāt accurately record what you play.
Iāve tried this with external midi keyboard, using the keyboard mode internally and with no midi device connected, ive tried it with different midi channels and Iāve tried it with a brand new project. Hereās what happens:
Go to track 12 and set it to MIDI machine.
Start Live-Rec mode (it doesnāt seem to matter if itās quantised or not) with Track 12 selected, play a three note chord sustained for a few beats.
Stop the recording and look at the sequence. A trig is recorded but it only has one of the played notes with none of the NOT2 NOT3 and NOT4 parameters set. The LEN parameter is also way too short 0.125 I think.
If you do the exact same thing on a different track it records what was played fine.
Also on Track 12 if you record just a single note it will record the not but the LEN parameter is still wrong, but most of the time itās just set really high - I think Iāve seen 80 something and 127.
Also, I think if you go into Rec Edit mode, hold down a trig and then play a chord on an attached midi keyboard, it does a similar thing or not capturing the 3 notes properly. If you hold down the trig and then progressively add more notes to the chord the first note is set to NOTE, the next 1 or 2 added notes overwrite the NOTE rather than setting NOT2, etc. it seems to depend on the notes played for example if I do C, then Eb, then G then I end up with just NOTE set to G and nothing set to NOT2 etc.; but if I do C then E then G I get NOTE set to E and NOT2 set to G. Again this behaviour is only observed on Track 12.
Itās so weird that itās not happening on Track 12, I hope itās just a weird bug and not a fault with my hardware.
EDIT: Possibly related, Iāve noticed that when playing (not recording) chords in through MIDI, with Track 12 selected, so that it plays those notes back out to the connected external MIDI synth, I frequently get stuck notes which I think is due to missing note off messages.
EDIT 2: I think Iāve managed to clear this issue now. I think the one thing I didnāt try when switching projects and changing all the midi settings, etc., was to turn it off and on again. I sat down and tried to eliminate the issue the next day and the first thing I tried the issue was gone and returning to the original project hasnāt made the issue come back. I guess I had some sort of midi loop of spending which got Track 12 in a funny state which persisted even after all the changes. I guess thatās sort of a bug, but much less significant.
~I now have more doubt about whether this is a firmware bug or a fault with my specific hardware. Would anyone be able to try this out to confirm if anyone can reproduce this issue with Track 12 please?~
See edit of the post above - Iāve managed to clear the issue.
1 Like
hello folks, when i go to FUNC+SAMPLE > project memory > right arrow > select unused the DIgitakt 2 freeze. anyone else has encountered this problem ? tried disconnecting overbridge nd rebooting but none helped 
Hi, Iāve just got a new DT2. Can anyone else recreate this bug? I would really like to know if this is a hardware issue or software.
- Change a sample machine to slice
- Press yes
- Go right and left and up and down using a combination of dial and arrows
- Device freezes
I created a video below: (only visible for 2 days)
Thanks everyone
i use the werp machine all the time, and this happened for the first time. after the set werp length of 4 bars, it continues to play another 2 bars in a kind of a slow motion. no, its not retriggering, as i mute it before, no i checked decay, release etc, its not chaning anything about the sound being produced after. it doesnt happen with other samples, is does happen on other tracks with the same parameters with the sample. I have the latest OS
Did you put in a ticket?
yes. but figured id maybe ask, if someone had the same issue. i found a reddit thread describing the same issue but the fixes did nothing for me unfortunately
Quick question with bpm settings per pattern they seem to have vanished after changing to bpm per project I thought switching back would revert bpm settings set in each pattern? or am I mistaken
Hi, Iāve encountered something on the Syntakt that I think is either a bug or an omission, and Iām wondering if any DTII owners could check if it is the same on the DTII.
When holding FUNC while editing parameters, it jumps to a predfined set of values (octaves, min-max etc depending on the type of parameter). On the Syntakt, this is disabled when editing locks, and if you for example want to jump to zero you have to dial it in manually.
Is it the same on the DTII?
1 Like