Same here, after restarting the issue went away and I couldn’t reproduce it.
1 Like
I had a similar issue to this. Did the message read “oops somethings wrong reboot”
I had some issue where the my bass drum track was triggering with different pitch every so often… Initially I was using the BD FM machine and for the life of me I couldn’t figure out where the ‘higher pitched note’ was happening during sequencer playback. I eventually disconnected all the midi cables, initialized the track sound, made sure both LFO were off but it was still happening. I could even press the trig button repeatedly and it would occasionally still trigger a note with different params. I tried as well the bd classic machine and found when manually triggering it would occasionally play a different sound - not sure which parameter was being affected but the drum hit would be a short one. Jeanne suggested a power cycle which did the trick but she mentioned she had a similar issue…
Profile - Jeanne - Elektronauts
I actually had this two times many months ago. It was a bit different, the pitch envelope seemed to be free running instead of triggering, or something like that.
Not something I’d like to experience when playing live.
But it has not happened since …
Worth a bug report I think.
Not the end of the world as it was just a simple power cycle to resolve the issue but still worth noting.
1 Like
Not sure if anyone else has encountered this, but since the 1.3 update the names of some of the destinations for the FX track LFOs are different in a confusing way.
You can see what used to be named “REV: Reverb FX Routing” is now just called “REV:REV” and the same goes for the delay FX block routing. Another one (not pictured) is the destination which used to show as “REV:FB Shelving Freq” now shows as “REV:FREQ”.
Minor issue, but it has thrown me for a loop a couple of times before I figured out what they were 
Also, would love it if anyone else could confirm this isn’t just my device showing different names…
1 Like
Hello ,there is a bug introduced in the new OS 2.13.4 version regarding the lfo . HOLD MODE does not hold the value anymore .
I have a sound for one of my composition that changed because of this .
The value is not hold anymore and move .On a Sy Raw machine , i accociated 1 LFO 1 to the syn OSC 2 detune . The mode LFO shape is random and the mode is HOLD . On the previous OS the sound was stable between note with a unique detune value . now the detuned value move between notes and make pitches unstable . then i don’t have the expected behavior that i have. Could you please confirm me that it is bug . If it is not then is there a way to have the same behavior than before ? or i will have to go back to OS before as this behavior is important for my compositon .
Looking forward for your answer. if you need more information , contact me . best regards .
PS : i just began to work with the new engine but i will wait for experimenting futher with new engine and will go back to the “old” OS waiting more info. thanks+.
Edit : The fade in/out does not influe ont he behaviour to . something is broken . i will not try to “understand” the bug or try to find a workaround further . i will just go back to 2.8.4 and wait for your information .
Sounds like you need to adjust LFO phase (now slew for S/H shape) to zero, then it will behave basically as it did before
1 Like
Oh ! Thank you so mutch ! now it behave like it should be !!
i missed this " Added slew functionality to the RND waveform for the LFOs. When RND is selected for the WAV parameter, the SPH parameter now sets the amount of slew." great new feature finally ! 
1 Like
SWARM synth parameters don’t reload with FUNC+NO. The values jump back into place but the sound doesn’t change. Lightly touching any encoder audibly makes the value “jump”.
Today i found that the REVERB is very off-center, audibly more loud in the right channel which is especially apparenty in lower frequencies and long reverb times.
Anyone’s Syntakt become noticeably buggier after 1.30? Love the new machines but I’m running into so many weird issues
- sometimes I get hanging notes but in a super weird way - when you trig a track, it quickly latches on some note and then stops the sound. messes up any sound, have to restart
- song mode buggery (tracks not playing despite being set to unmuted), have to restart
- a track on one pattern keeps randomly disengaging from fx track (?!?), keeps happening every now and then but is difficult to replicate
- ghost trigs in sequences
It is by no means Polyend levels of unusable but mine definitely now feels less reliable for live stuff
2 Likes
I think the FX track has some bugs for me with envelopes not triggering sometimes that I’ve set in there. If I reload the song or change patterns sometimes it fixes itself. Hard to reproduce reliably for me.
1 Like
There’s some funky stuff going on with OB + OS1.30. I have got weird randomly hanging and/or pitch shifted notes but only on the analog tracks. There’s no other midi going into the ST. Will check if loading a different project solves anything, but this makes the ST unusable with Live atm.
update: Loading a different project doesn’t solve it. 
update 2: It’s not an Overbridge issue. My Syntakt just decided to suddenly act funny… Might be time for a support ticket.
update 3: A good ol’ power cycle and waiting a bit seems to have solved the issue… It’s a Christmas miracle! 
When I switch patterns, the FX block settings visually change, but they don’t start to actually apply until a note is played on the syntakt. This means that if all the syntakt’s channels are muted and it is filtering external audio, when the pattern changes I still hear the old settings.
I think it’s working as intended. A lock/yellow trig at the beginning of the pattern can apply the new pattern’s settings, or the Global FX/Mix menu can keep all FX / FC track settings the same across patterns.
1 Like
I don’t think it’s working as intended? I don’t see anything in the manual around the behavior of the FX block when switching patterns, but since I have all the FX/mixer settings in “non-global” mode, I’d expect that when the pattern switches, the FX block’s settings change to that pattern.
I tried just using a lock trig on an unused track and that didn’t work, nor did putting a lock trig on the FX track… did you mean that I would need to p-lock all the settings I care about? That does work, but is really annoying…
It is though! It’s not a bug, it’s annoying, but not a bug
2 Likes
With the latest released Syntakt OS 1.30B, all bugs that are known and we have been able to reproduce should be fixed. There might still be issues of course, so keep on reporting if you find something.
One issue that we have reports on but so far not been able to reproduce ourselves is this one (also kindly reported by @Jeanne and others).
In effect, it will cause mistriggering pitch and or amp envelope on the analog tracks.
If it happens (which appears to be very rare), it seems to be active from power-on and will not happen mid session. A power recycle solves it. We hope to nail that down too of course.
13 Likes
Since I also seem to have enountered confusing things with the fx track, could someone ELI5 for me the logic in which the fx track does work? Perhaps I’m missing something important…
Like, sometimes I power up the ST and the fx track is mute… Or, I load another project, press play and the fx track is mute… if I then switch to the fx track and manually trig it, it starts working again…
thanks
There’s a bug that is still here for me. While pressing FUNC sometimes it opens the Sound list as if I touched the LEVEL/DATA knob.
That sounds more like an encoder issue. If it is opening the sound browser it likely mean it is seeing input on the LEVEL/DATA encoder. Can you enter test mode (hold FUNC while powering on the device) and see if it is registering movement?
Yes, I’ve done that before. The way it behaves also shows that is a software bug rather than a hardware issue