Hi @avantronica. Thanks for you’re reply. The second behaviour with Max MSP I can somehow understand because it’s not nice but logical. But why the manuals says you can track 2 octaves within analog tracks and it stops key tracking at C7? C5 is middle and C6 is 1 octave. So it should go above C7 at least until B7 to have 2 full octaves, or am I wrong?
It goes as high as the VCO can … I would have guessed C4 was centre of ‘normal’ range, but what is C4 anyway, it’s completely arbitrary.
It’s centred around Midi note 36 iirc but I have written this a few places here already. Whether it’s adjusted from Rytm range I cannot recall
There is also an octave offset parameter in sound settings
Either way, there’s no issue with the device, it just takes stumbling into these limits to appreciate that there are limits. It’s a balancing act, but all the tools are there to exploit its potential. The digital oscillators are more compliant
Few bugs I’ve encountered lately that were fixed with a reboot but probably worth bringing up anyway.
-
I had patterns changing on their own the other day with no incoming MIDI and no song mode enabled. Problem went away after rebooting and I can’t replicate it. It was a brand new project and I hadn’t made any changes to synth engines or settings.
-
Track 6 engine was triggering on a note off function. Basically pressing down on the key would trigger the sound but releasing the key would also trigger the sound. It also went away after a reboot.
1 Like
I get #2 pretty frequently, occasionally with great results!!
1 Like
I have this same issue and found out how to reproduce it. Hold down note on a midi keyboard on auto channel and while holding the note select a new channel. The first channel will get stuck double triggering, and for some reason the pitch is different between note on and note off.
1 Like
I forcibly disabled Master clock receive and master clock sand in syntakt and in DAW settings . Only Overbridge distributes clock. And so far everything is fine . No device freezes.
There is another similar issue: hold down a trig then change the note using the knob while the sound is playing. After that ST will trigger on release as well.
1 Like
I think I found the first: This LFO destination is very interesting 
(Is your Syntakt still working?!)
The other one I don’t see yet…
yes, sorry that I was not precise.
To reproduce the issue:
- push and hold a note on a midi controller
- change trig note by rotating the knob on ST
now ST triggers on press and on release.
1 Like
LFO 2 doesn’t have LFO 2 as destination, nor LFO 1 DEST.
How to reproduce :
Set LFO 2 DEST to LFO 1 DEPTH
Power cycle > it displays LFO 2 DEST
(it is set to None actually, so apparently, this buggy displayed value just describe what parameter LFO 2 DEST is).
Yes. Apparently some lasting bugs…
1 Like
Ah ok I thought it was ST standalone.
[edit: Not a bug, see @Humanprogram’s reply to this]
I’m pretty new to Syntakt, so I’m not 100% sure that what happened to me was a bug, or if I just missed some detail.
At one point, I found tracks 9 and 10 to behave very weirdly. Having loaded either Dual VCO or SY Raw on them would only play “legato” notes (or sustained notes?): If I pressed the track button, or played a single note in keyboard mode, the note would keep playing, even if I let go of the button. Sound could only be killed by double tapping stop.
I checked reverb, note length and other settings. This behavior persisted over patterns, even in the default pattern, even over a factory reset. The same happened, when the note was played on an external MIDI keyboard.
What is more, both tracks would not play any sound, when I programmed trigs for them in the sequencer.
I have tried many things, including factory resetting the device, and that did not solve the problem. What did seem to do the trick was one of my stress responses: Either hacking on the trig buttons a bit faster, or quickly copying the VCO sound from track 11, where it worked, and undoing the copy for a few times.
Can anybody tell me if this has happened before, is possibly intended behavior that I’m too shortsighted to understand, or whether it sounds like an actual bug that should be reported?
I would not like this to happen again, since I’m not really sure how I made it go away.
Cheers
Good news, It’s the AHD envelope: tracks 9 and 10 have it set to this by default for kicks and snares. Hit the Amp page twice to change to an ADSR envelope for synth sounds.
It’s a common trip-up point, and I wish there were a way the machine would either switch when changing machines or come with a default decay setting to avoid notes sounding out like this.
1 Like
Ahhh! Thanks for the quick response! Now I feel stupid, but a bit more educated after all.
Great how my superstitious pigeon brain thought that I solved it by hacking on the trig buttons. So copying the track sound from track 11 also changed the envelope type and resolved this issue?
1 Like
We’ve all been there! With lots of features and settings the troubleshooting learning curve can be steep. On the plus side, I’m still regularly discovering new things this machine can do, a full year into owning it…
1 Like
I believe this is a bug of Reverb & Delay when applied on an audio-in signal.
As long as you trigger only MIDI tracks, those two effects won’t do anything on the audio-in channel, letting the signal unmodified. Reverb and Delay won’t work until you trigger a note on a non-MIDI track, and only then those effects start applying to the audio-in. (Note that the Balance button in the same mixer panel works all right even when reverb and delay are still non-functioning).
this is by design, you can trig the FX track - they do this to reduce noise floor, so you must trig
1 Like
This is an issue with all the digi shaped boxes. The effects need a trig on an internal track to start, and are also stopped by double pressing stop, which is useful for stopping runaway feedback loops. I think this is technically intended behavior, though it can be annoying.
1 Like