Logic + OB + Syntakt, trig velocity keeps being set to 1

Elektron Software
1

I’ve had a Syntakt for a few weeks and have just got around to recording some of my jams into Logic. I’m using a Mac Mini M1, Logic Pro 10.7.6, and Overbridge 2.1.5.4.

I’ve been having a weird problem where randomly the Syntakt tracks in Logic would go really quiet, like barely audible, and I couldn’t work out how to get them back to normal, although some notes would still play at normal volumes. This even continued when using the Syntakt stand-alone. It usually took turning the Syntakt off/on, or reloading projects/patterns to get things working properly again.

I think that I’ve finally tracked down the problem however. I eventually noticed that the default track trigger velocity was getting set to 1 across all the tracks. I assume that the random notes that were sounding properly had a p-locked velocity. Setting the velocity back to a sensible level fixes the problem. I’ve found that double clicking the stop button in Logic causes this to happen, although I have a feeling that might not be the only thing. Has anyone else experienced this?

2

In case anyone else has this issue, here’s the response I got from Elektron support on this:

I have not seen other reports of this problem, but I found that when “Control 2 (Breath Control) to zero” is checked in Logic Pro Preferences > MIDI > Reset Messages , the velocity parameter of all tracks is set to 1 when double-clicking STOP. Spying on the output from Logic Pro, using a MIDI monitor, I can tell that Logic Pro sends out CC number 4 with a value of zero on all MIDI channels when double-clicking STOP (if “Control 2 (Breath Control) to zero” is checked). CC number 4 will change the Syntakt velocity parameter, which explains the problem. If you uncheck this setting in Logic Pro, it should not happen anymore.

5 Likes
3

Happened to me too. Once I realized that it was velocity that had been turned down I could search the web a bit more efficiently, and found this. Thanks and praises!

Humbly, Ylan

1 Like
4

Or I thought I’d solved it.

I unchecked “Control 2 (Breath Control) to zero” but it still happens. I will have to try creating a new template for Syntakt in Logic.

Humbly, Ylan

5

Thanks for posting this. I’ve been running into this issue on Digitakt II and it’s been a real head scratcher. At first I thought I was accidentally doing “Control All”.

I wonder though if there is a typo in the solution above? It says:
“… Logic Pro sends out CC number 4 with a value of zero on all MIDI channels when double-clicking STOP … CC number 4 will change the Syntakt velocity parameter, which explains the problem.”

But the solution above says: “Control 2 (Breath Control) to zero” is checked … If you uncheck this setting in Logic Pro, it should not happen anymore."

So first it says Control 4 is the problem but then advises to uncheck Control 2. Perhaps they meant to say uncheck “Control 4 (Foot Control) to zero”?

6

Yes I think CC#4 is velocity on the Elektron boxes. I had this happen with my AR and was mystified.
Interestingly, the AK doesn’t seem to respond to it

Kinda unrelated, but similar: I discovered the AK sends Pitch Wheel 1 -8192 when it’s started up, so any synth downstream will be out of tune if it’s turned on before the AK

7

I’ve got the same issue but on ipad when using Digitakt 2 to sync slave logic via audiobus

Anyone know where to find this breath control setting in logic for ipad?

8

So has this nonsense been fixed yet in ipads? Only workaround I can think is disabling all tracks channels on the elektron device but then logic won’t send recorded automation.