I’ve got my Digitakt L+R out routed into the Syntakt L+R in, and I’m using Syntakt L+R out (or Syntakt headphones) as the main out. Every time I boot them up, no Digitakt audio reaches Syntakt out or headphones. Syntakt’s external mixer is set to global.
Every single time after bootup I have to go to the mixer (page 3), nudge the external in (encoder A), which brings Digitakt’s L back, then nudge the balance (encoder G) to bring Digitakt’s R back as well.
It took me some time to figure out this workaround (after checking audio routing and Digitakt multiple times), and I can consistently bring the external in back, but this seems like a bug.
Afaict it is normal to have to stimulate(typically trig) the FX track to activate it … there must be good reason as it’s a bit inconvenient set up this way
Thanks! Indeed, the external in is running through the FX block in this case. I’ll check if there is a quicker/easier way to get up and running by triggering the FX track.
Otherwise, if this is the expected behaviour, I will have to remember to nudge the level and balance each time.
I have a vague recollection it may be done for noise floor reasons. I.e. Shut off external ins unless you go out of your way to purposefully activate them
Any trigless trig on the FX track setting something in a vanilla state should do the trick
Experienced a bug yesterday where after powering up the Syntakt, the patterns had partially reverted to older states. I had saved the project manually just before powering down, thankfully, so I could just reload the project from the drive to fix this, but for a moment I felt really nervous about losing hours of work.
What happened was that some patterns were missing, and after pressing a few buttons in mute mode, even more patterns were missing. After some time, there was just the one pattern on A1, with an older name on it. It was as if it was pulling from an earlier version of the file or something because the name of the pattern was the name of pattern A2 that I later renamed before saving.
This makes me wonder, can you trust the autosave feature at all? I tend to rely on this all the time, it’s part of what I love about the Elektron *takt boxes, the immediacy of just powering them up and picking up from where you left off. Now I feel I’ll need to compulsory save every 5 mins just to be on the safe side.
Recorded a song into Reason 10 (MacBook Air 2021) via Overbridge and then when not using Syntakt itself I switched to an empty pattern to ensure it’s not playing on top of the recorded tracks when mixing.
I noticed that the Syntakt crashes a lot when just leaving it on in Overbridge mode like this. Nearly every time I went back to the Syntakt to record another section or redo something that I wasn’t happy with, the Syntakt had frozen completely. The trigs and buttons remain in the color they were before it froze, and no button press does anything. The oled screen remains on and no error message is shown.
A quick power off and power on restores it again, so it’s not necessarily a big deal in the end, but it definitely seems very unstable. It would be helpful with some kind of error message to understand what’s going wrong here.
I really don’t know. I don’t even know if it sends midi data, because I sure can’t record any into Reason 10 from Syntakt. It’s all audio from that direction at least. But why would it crash even if some midi data was sent to it? There’s no loopback issue from what I can tell.
Midi feedback loop or too much midi data receive is a common freeze reason.
I don’t know Overbridge, nor your setup. I’d eliminate things one by one to deceipher if there is a particular culprit…
Small bug I found on 1.2; initializing a sound (or even erasing a whole pattern via pattern menu) doesn’t reset the Note on the Trig page to the default C5, it will stay at whatever it was changed to on the erased pattern/track.
Hmm, okay but if you are resetting a whole pattern, should it not put everything in that pattern back to the way it was before anything was changed? I also just saw most of the other parameters on Trig don’t reset except the portamento ones. If there’s logic behind this I don’t get it (explanation would help), as to me erasing a pattern should mean everything is back to defaults. I can see the logic of it not resetting with a “sound” reset in case you are just wanting to restart making a sound with a couple base settings in place, but a “pattern” reset should IMO.
In the new Machines at the Analog Machine, the Random Function does only affect Tune and fine Tune and pitch on the Syn page. On all other Machines it works in a other direction. is this a bug ?
