Got this amusing bug on a pattern where a MIDI track gets func+no’d back to the original state (in this case SY SWARM). The bug disappears when you flip between pages (eg -> Filter & back to Synth).
Replication:
SY SWARM on track X -> Change track to MIDI -> Func+No to reload pattern
If I were better at memes, I’d try to make something about “one save to rule them all” vs. “one save to ruin them all.” As it stands, I’ve had similar things happen and it’s dangerous/precarious and a bummer. Good job thinking quick and selecting the proper answer to the yes/no question.
Came across this fella for the first time today.
Edit: Has me thinking if custom color-schemes would be possible? Like on the M8 f.e.
Experienced my first major bug today. 
I have a project that I started writing patterns in about a month ago.
A few days ago I spent hours filling the banks with new songs/ideas.
Came back today to keep working on those ideas just to find that all the patterns from my last session have somehow had their patches initialized.
The patches from my patterns that I worked on a month ago all seem to be intact, even the ones that share banks with the newer patterns.
This has happened across multiple banks.
Luckily, I always make a backup project, so I was clearly able to see which patterns specifically have had their sounds initialized.
Only problem is my backup project is from an older save state so it doesn’t have some of the newer patterns/songs that I wrote, and I have no way of knowing what sounds I was using on them.
Is there any way to reverse this?
Hello,
PTIM and PORT : they belongs to the sound, not the pattern.
There is no mention of this in the manual.
=> I received that info from the support.
Best
John
Hello John,
Thanks ! That makes sense now.
The manual should definitely clarify that the [TRIG] Parameter reload and randomize only affects the PTIM and PORT which are the only parameters on the TRIG page that are part of the sound.
Hi @inputmonitor,
This one is strange. After some testing, it seems related to the fact that at the end off the waveform, it has reach it’s “natural” max peak.
I could not reproduce it at first time because I made a new pattern without setting the LFO.T.
As soon as I set LFO.T to retrigger and set it back to not retrigger, I got the problem.
Going the the lfo page and change DEP, change the pitch.
Changing the WAVE or SPH does not do anything.
I don’t think it’s directly related to the waveform because I could reproduce the same behavior with the RAMP. (SPH to 0, SPD & MUL to 32) and the mode set to HALF.
Similarity : these two waveforms have reach their natural peak at the end of the mode.
By “natural” I mean that I can’t reproduce this with a sine or triangle and setting the top with sph.
Definitely a bug for me…
Did you make a ticket ?
Best
John
Hi John, yes I made a ticket.
Hi @Brockstar,
For os v1.21 : “TUNE” does not move on any machines when randomizing (digital & analog).
Seems like the desired behavior now.
Randomizing overdrive still don’t work for analog engine… two years now 
(re-up to the support)
Best John
Does anyone else experience trigs that don’t fire? It’s happened to me a few times of late where a sequenced track does not play. Nothing muted. Playing the track manually doesn’t ‘wake it up.’ Power cycle fixes it but dang.
Hi @JohnLost,
Just have this one right now.
My Syntakt was in sleep mode for a while.
I made a new pattern with just 4/4 bass and no sound.
Triggering manually works but not the sequencer.
I double check everything but nothing anormal.
After changing the lfo modulation on the TUNE, sound came back again from the sequencer.
Best
John
Hello,
Re-up for this one
After contacting support, it’s confirmed to be an error in the manual.
This is actually an error in the user manual, which I have asked our technical writer to correct. The feature described is simply not implemented on the Syntakt, or any other product in the Digi series. What happens when using this key combo is just that a trig is added, since the track is triggered. I hope that explains it.
Hello,
Trying to switch audio routing “midi in” to off does not work.
Settings > Audio routing > midi in post-fx
Settings > system > usb config > usb audio/midi check
Play some audio from pc throught Syntakt Audio Interface.
Now, just switch midi in to off : does not work.
Keep these settings, switch off, wait 30 sec, switch on Syntakt.
Try to play from pc, no sound.
Reported to support and confirmed to be a bug.
New user here. One month with the ST e25 and this is the greatest honeymoon phase I’ve had with any instrument since my first new guitar as a teenager 
The issue @7thSun mentioned has happened to me 2 or 3 times as well. I make it a habit to save projects before powering off, and reloading the current project has always fixed the issue for me, so it hasn’t taken any data yet, but this is a bug that was mentioned in this thread over a year ago for the first time.
I came by to report an interesting bug I encountered this morning. On the FX track, after turning retrigs on for certain steps, I applied conditional locks but they didn’t have any effect. Changing to 2:2 or 4% (for example) no longer affected the FX track trigs, and they would trigger for every loop regardless (including the retrigs). After restarting the ST, the conditional locks worked as expected.
I just tried to replicate the bug but I wasnt successful.
Today, when working on a song, I suddenly got no sound.
After quite a bit of troubleshooting, I found out that the external input level on the Syntakt had been reset to zero on about half of my patterns. This way, the sound from my Digitone could not be heard. These patterns had been working the minute before.
Is this a known bug?
This thread is about a bug I just experienced today and searched for, finding others that have had the same progress loss bug with the syntakt specifically
if you have a good sound and go to change machine but hit “no” (as if to change your mind) your sound goes bye bye, no and yes from machine menu mean the same thing lol
First of all, Elektron has a history of updating firmware of their line-up years after initial release. Also with long periods between firmware versions (talking about years).
Second of all, asking this question is a bit useless as Elektron never gives a lot of details on their roadmap, so nobody knows.
Sometimes mine doesn’t want to turn off, like she wants to keep making bangers til Dawn.
Perhaps it’s just a defective turn off switch, but I prefer the alternative narrative of a haunted banger making machines that decides by itself when to let me go.
Anyone else had a situation where a pattern seemingly gets corrupted? I was recording into Login on iPad, Logic crashed and the Syntakt started playing feedback over my headphones. After a reboot only ~5 trigs in the entire pattern play. Even when I copy individual trigs into a new pattern they won’t play. Additionally in that pattern and any other I copy these trigs into I cannot generate sound through hitting the trig key for that track. Have never experience a bug this severe and it has me questioning if my backup strategy is sufficient.
