Using knot with looper end of chain not working

Knot
1

Hi there. I am using knot and trying to use without having to use another midi merger. The set up that works is knot to Torso t-1 in. Torso thru and torso out to kenton midi merge. Kenton midi merge to digitakt 2 in. Digitakt 2 thru to digitone in. Digitone thru to rc505 mk2 looper. Works perfectly. But when I try Torso to knot in, knot out to digitakt 2 in. Digitakt 2 thru to Digitone in. Digitone thru to RC505 mk2 in, it mucks up the loopers sync and the recorded loop is out of kilter, even though everything else is fine up to the point the loop starts playing. The knot is set to blue mode to merge the torso t-1 and the grid controller. I’m not sure what the difference is between using the kenton merge and the knot merge function and why the knot has this effect? Thanks very much, Kev.

NB It seems to be to do with the clock signal going through the knot from the torso t-1 and it is making the tempo jitter 2 or 3 bpm, when it goes through the kenton midi merge it doesn’t do that. Any ideas anyone? Does the knot muck up the clock signal? Thank you, Kev.

2

Knot has some currently known bugs regarding clock jitter. That’s probably what’s causing the setup to behave differently. Until those bugs are fixed, you will have to use the additional MIDI merge device I think.

3

Ah, ok. Thanks very much for that. Appreciate it :slightly_smiling_face:

1 Like
4

Do you have any idea when it might be? I see on other discussions elsewhere now, it has been a known problem for quite a while. If it is going to be a while, I might prefer to return it as the point of getting it was to cut down kit for live stuff. Thanks very much - Kev.

5

The clock jitter issue should see general improvements in the next iteration, in a couple of weeks time the earliest.

6

Brilliant, thank you very much for that. Appreciate it.

Kev.

1 Like
7

Any updates on this outstanding issue? Have any of the general improvements been implemented yet or is there a new timeline? Thank you.

8

Our current priorities in regards to Knot are the following:

  • Fixing issues in regards to core features such as the MIDI through function;
  • Fixing compatibility issues with hosting controllers from other brands.

Based on the above, we’re planning on releasing the fix for clock jitter before the start of Spring. For everything else, we’ve delayed patches to at least Spring, because most of our efforts are/will be on VSN1 firmware development.

When I have concrete info about the jitter fix, I will make a follow-up post about it here and on Discord as well.

Thank you for your understanding.