I’m not sure I know what you mean.
The external input, on the Syntakt, is not a “track”, and so does not require triggering.
It is managed in the mixer section, by holding down FUNC and pressing the LFO button repeatedly, until you see the mixer page for external input adjustments.
It shouldn’t require triggering but I’ve encountered the same issue where the external input will be muted until you tweak the mix level on the external input page. I’ve also found that sometimes the signal will be panned hard right until I have to tweak the pan control and then it will instantly be centred
1 Like
Thanks for the reply.
Check my followup post.
Original problem stopped happening, when I opened a new project.
NOTE: I discovered that the original problem of muted ext input, only happens if SETTINGS > GLOBAL FX/MIX > EXTERNAL MIXER is switched on.
But a new problem appeared…
now turning up the external input echo, and reverb, have no effect, until I punch one of the trig buttons, then the external input starts to get reverb and echo.
Only happens when opening a project.
I don’t understand why this is not considered a bug?
Can someone explain for me, why this would be desirable?
That’s what I meant by comparing the OT thru track trigging above, I was just mistaken about what was not sounding, but that’s what I was alluding to (not quite correctly)
However, it is not considered a bug, just so you are aware
1 Like
I reported this as a bug. I can only record delay and reverb via main outs, the specific fx channels are always silent. Not tried with 1.10
1 Like
I have a doubt concerning screen auto off. What is normal time ? My ST was stopped and it didn‘t turn off after more than one hour…
NOTE: I discovered that the muted external input problem, only happens if SETTINGS > GLOBAL FX/MIX > EXTERNAL MIXER is switched on.
Wondering if similar bug, happens with other GLOBAL FX/MIX settings switched on?
1 Like
In the manual, there is a FX track LFO destination called filter type, but for the life of me, i cannot find it when I look for it in the syntakt.
theres this random blank pattern i came across in my syntakt, that has that destination i speak of already selected, but when i go and try looking for it, its not anywhere to be found.
Wow, discovered a new very annoying bug today, that I don’t think was present in 1.0.1 before the last update:
In my project, when switch from pattern 2 to pattern 5 (only in this order!), the track 5 which is a TONE machine, just lose it’s sound on pattern 2. No way to get it back unless I stop the track completely and start it again. This only occurs on pattern 5, and any other pattern switch works. Very strange!
Will try to do a video and send it to Elektron support
1 Like
Syntakt responded, and is looking into this.
I have confidence they will work out the bugs, in the next update.
Was that Tone machine sent into the FX track perchance?
In pattern 2 no, in pattern 5 yes!
It might be FX track issue then?
I’ve had this issue before 1.10, it’s not new I just couldn’t reproduce it before. When I would switch to a pattern that had a track going into the FX track, that track would play in a weird distorted barely audible way. If you stop playback and change pattern, the issue goes away.
For me it happened randomly, but I could notice it a lot, since the pattern would sound very different each time.
I thought it has something to do with the analog parts not being triggered, or the FX envelope getting stuck or something like this, but idk what actually causes the bug to happen, it just does sometimes.
I can reproduce it everytime, and it’s definitely related to FX track, as muting/u muting the FX track fixes the issue. What’s strange is that track 5 is not the only track going to FX track, but it’s the only one affected.
Ive been able to successfully recreate a bug.
Theres a cy ride machine sound i made that creates a permanent static hiss that doesnt go away until you reload the project. saving the project, with the static sound preset will cause the static hiss to be present when you reload the project…
to recreate, go to cy ride machine and set LFO to pre/post fx and set mult to bpm 1k. if you set the the other LFO to say something like, overdrive and also put it to 1k, the static could sound different, in my experience.
2 Likes
Confirmed I can also recreate this by doing only this (plus moving the depth value to non-zero). I can get the static buzz to go away if I simply change the LFO destination to something else or setting the depth back to 0.00. Interesting find!
EDIT: This seems to affect any analog machine
2 Likes
It’s not clear it is a bug (as opposed to an oversight or a quirk of what you are doing within the sound)
It’s an audio rate switching of a track’s output between two positions in an all analog chain … the issue doesn’t affect the digital tracks which may indicate that it’s a quirk of the configuration of the analog voices rather than a bug in code
The modulation itself is rather interesting, but there’s no need to restart the project or adjust LFO - playing a soundlock or that same voice on another pattern or adding a parameter lock of depth zero somewhere in that pattern will kill the ‘still running’ LFO, as will trigging the LFO and then giving it a fade
This noise will manifest even if the machine type is DISABLED, suggesting it is an analogue noise thing … i do wonder if there is something that can be done, it’s not too pleasant and could catch folk out quite easily
Interestingly, clearing the LFO and unclearing it will not reset it, if you have a trigged LFO and a fade it will simulate the fade as though a trig occurred even on a non running pattern
So there are workarounds, but i agree it’s an undesirable artefact and maybe something they can adjust out, but it may be a quirk of the analogue nature of the circuits and the solution may be to manage it (especially as it’s an edge case usage, although interesting) … hopefully the destination will remain, i’d hate to see that go, let us know what they say can be done about this, if anything, good catch though !
1 Like
I’m just relieved its not a hardware issue, as the hiss made was much more pronounced when I first heard it because I was using a lot of compression from digitakt, and it really freaked me out for a second. Double pushing stop makes the hiss change pitch for a short time too… thanks for the feedback
1 Like
Not sure if this is a bug or removed parameter. I noticed today that one of the analog cymbal machines (CY METALLIC) has a missing ‘Color’ parameter. It is visible as an LFO destination in Overbridge but missing as a parameter on the SYN page and as a destination on the device itself.
1 Like
FW 1.10, while in song mode, I experience two issues. Anyone able to recreate these?
1: Inconsistent pattern mutes (the purple ones)
The pattern itself (outside of song mode) has no pattern mutes set. In song mode I have the same pattern on several consecutive rows with various mute states.
While playing through the song and activating “looping mode” (Func+Left) to fool around with a pattern for some time, I often want to mute a track that is unmuted on this particular song row (or vice versa). What often happens is that the purple light changes as it should, but the actual mute state does not. If I press the trig again, it then works but now the light is reversed (dim purple light with sound from that track, or bright purple light with no sound from that track).
2: Func+No sometimes do not reset all parameters
I am looping a row in song mode and messing around with parameters (Ctrl-All and stuff). I then deactivate looping (Func+Left) to proceed to next song row (next row has same pattern but different mute states).
When song switches to next row, I press Func+No to reset the parameters I’ve messed with. What often happens is that some but not all parameters are reset, and I have to press Func+No once more for the reset to take full effect.