I am hoping someone can point me to an internal setting here, but I am having a problem with my Syntakt…
I have an external keyboard (a Critter/Guitari Pocket Piano) routed into the Syntakt. I want it run through the FX chain. I have this working…but…
I have the Syntakt receiving clock, program change, start and stop from my Digitakt. What I am finding is that if I start sync’d playback from the Digitakt, perform a song, and then stop and perhaps try again, the Delay is no longer active on the Syntakt input. It APPEARS to be - display shows as active - but it no longer is routing the signal through the delay part of the FX path. Oddly, overdrive and filtering are still active.
I have to power cycle the Syntakt to get the delay back.
My Syntakt is on OS 1.21…Has anyone else run into this?
Sounds buggy, but what happens when you ignore the digitakt and hit start and stop from the syntakt transport only? What happens when you disconnect the pocket piano from midi? What happens when you disconnect the digitakt and try with just the pocket piano? What happens if you set up a brand new project with the same 3 pieces of equipment, with no other information copied over, and try a basic test of the same routing to see if it happens again or not?
Just a few things you could consider trying out to find out if one piece of gear in the mix seems to be causing the issue, if it’s specific to this project, or if it’s a bug. If you can figure out a condition under which it doesn’t occur, then when it does it will be easier to figure out why. If it’s only when outside transport is initiated, maybe try using a different piece of hardware (other than digitakt) as transport and clock to see if the results are the same.
And if it is a bug, post it in the syntakt bugs thread as well.
Yeah I wasn’t really thinking about which generation pocket piano you had, I just assumed when you said “I have an external keyboard routed into the syntakt” you were saying that you were also using it as a controller.
In that case another thing you can try if you need a workaround is to send transport from syntakt to the digitakt and see if there’s any issue. If it’s a bug and it’s been reported, it will be in that thread I linked previously. Maybe an expert will check in, we’ll just have to wait and see.
@Tchu you posted that link while i was replying, i was actually replying to your previous message but that thread is almost certainly what is going on.
And confirmed - this is exactly what is happening.
To recap for future readers -
If you hit “stop” twice on a Digitakt or Syntakt (or Digitone, I think too) that’s playing, it acts as a sort of “MIDI panic” button, and stops all notes, AS WELL AS any FX that are ringing out still.
The FX then maintain that muted state on the Delay / Reverb UNTIL you trigger an internal note. This will put the box in a state where the display is telling you the delay (for instance) is still active, but you will not hear it, as it has been muted.
Tapping any key that triggers a sound will re-enable the muted part of the FX chain.
The behavior is there to prevent a situation where you might have feedback set high on an effect and the system could overmodulate immediately when you press play again. But, if you’re unaware of this, it’s very confusing as your FX are just not playing back as you expected.