Midi track within a pattern starting late in a sequence

Elektron Gear Digitakt
1

Hi everyone.

I must be doing something wrong.

I have a Minitaur with my Digitakt.

Sometimes when I change patterns in a sequence, the Minitaur track within a certain pattern starts late, but when I play that pattern containing the Minitaur track in isolation, it starts correctly.

Any ideas?

2

any os for the digitakt aside 1.01 - 1.04 will not play the first trig of a sequence. not sure why they cant fix it… it will play the trig but not the first trig in the pattern until it goes round once… then it will play. i still use 1.04 … not sure how others use the digitakt as it doesnt seem to be a problem that many people shout about but its very annoying. if you want os 1.04 let me know and i will dropbox it to you. it works fine with that os sequencing external midi instruments.

3

Thank you for this.
I thought I was going crazy!

But it’s odd, as some Minitaur tracks work fine.
There doesn’t seem to be a logic why some are fine, some aren’t.

4

The bug the previous user is describing happen when the digitakt is slaved to another device. Sometimes it will skip triggering the sound on the first step of the digitakt. But this shouldn’t put your patterns out of sync.

Just to make sure the issue is the described bug,
do you have the digitakt slaved to the Minotaur?
Are you sequencing the Minotaur from the digitakt?

Also not a good idea to go to 1.04 if this is a midi problem. Midi on the digitakt was quite messy back then.

1 Like
5

Thanks for this.

I’m sequencing the Minitaur from the Digitakt.
Using my Blofeld in the same way, working fine with the Digitakt.

Just wondering if anything can be fixed through the Minitaur editor?

Minitaur
Minitaur.GIF894Ă—658 213 KB

6

Apologies for double posting, but any ideas on how to solve the late pattern triggering issues with the Digitakt and Minitaur? (My Digitakt is controlling the Minitaur)

Are there any CC messages that can be sent to the Minitaur to get it triggering on time?

I’m posting this additional post, as it appears my Blofeld has no issues with this, so I assume it’s a Minitaur problem.

Thanks!

:slight_smile:

7

Few things to check:

check to make sure the sequence is on the steps you are expecting it to be on when it grid record mode.

check track length for the midi track you are using to control the minitaur.

Check to make sure the midi channel the Minitaur is on us not being used by another track on the digitakt.

2 Likes
8

Thank you for this!

Minitaur is currently set to “track 16” on the PC Minitaur editor (but using it on Digitak’s channel MIDI H) , does that mean I have to “stop” Blofeld operating on that channel, and if so, how do I do this?

Could this be the issue?

Thanks again,

D

9

I think maybe a little more info on your set up maybe be helpful. It’s difficult to troubleshoot not really knowing how you have things routed.

But if you have the Minitaur and the blofeld set to receive midi on the same channel they will be playing the same midi sequence. I don’t think this would cause the mini to start playing late but it would have potentially undesired effects.

Have you checked to make sure the Minitaur sequence actually starts where you are expecting it to in grid record?
I ask because If you live record it can be easy to microtime a note on the first step but before the start of the pattern which will not play on the first play of the pattern.

2 Likes
10

Thanks for this.

I’m using Digitakt, Blofeld, Minitaur, Kenton thru, Kenton Usb host and a Minilab MK 2 (operating on its channel 1 attached to the midi out of the Digitakt through the kenton usb host)

Before using the Blofeld in multi mode, I was still having these late pattern issues with the Minitaur in the Blofeld’s single mode. The midi light of the Minitaur was exactly on the beat when the Minitaur sound should start, but the sound was starting late, but with the Blofeld it was fine. Weird :slight_smile: