Ah, I don’t use a Digitakt, so I haven’t noticed that.
I also haven’t really been reading threads on the issue tho I vaguely remember a few. In my experience when something like that happens it’s from either too much data being shoved down that pipe or the receiving device needs slightly more time to change Presets and trigger a sound.
Also in my experience it’s a “your mileage may vary” as not every system is affected.
I don’t know how the Digitakt works, but if you’re changing patterns that also includes changing audio samples, that might slow things down enough to lose that first beat. It’s also why I avoid sending PgmCh to synths in the middle of a song/performance while that Track is playing. As for ‘too much data’, I ran into that with an old multi-fx processor back in the day…mid 90s I think. It would get confused if I was sending too much data on other channels.
I’d suggest use MTPro to filter all data except anything specific to the Digitakt as destination. That is, don’t define routes in MTPro but define them in the Presets only. This way, only the data that satisfies the conditions of the presets gets sent to the Digitakt (ie only data destined to control it, nothing on other channels)
If that doesn’t resolve it, I’d imagine it’s that too much stuff is trying to be done on the first beat and the Digitakt OS can’t switch patterns and play the first beat at the same time. 