Digitakt 1.04 : Bug reports


#611

I just did this and the first time through the bar I get Kick on 1,3,4 - the next time I get Kick on 1,2,3.

This seems right to me. The ‘neighbor’ track (the N of NEI) is track minus 1. So I’m guessing track 1 has no neighbor track since track 0 doesn’t exist, and the neighbor is just itself. It’s behaving as expected in that way.

If for some reason you’re talking about the SD on track 1 and BD on track 2… I get kicks on 1,3,4 for every bar. This would seem to mean that because the neighbor track (1, SD) has no trig conditions, the default comparison results in ‘false’ for beat 2 (NEI) thus no trigger, and then false again for beat 4 (/NEI) thus a trigger. Again, this seems correct.


#612

I guess I shouldn’t have tried it on tracks 1 & 2. I’ll try it again in the center.

I can’t comprehend how 1, 3, 4 could be correct if it’s NEIing itself.

Will redo the experiment and see if I can figure it out.

Thanks for your response


#613

Oh shoot! I just tried it on the middle tracks and it works as expected! That is COOL! I just discovered the thrill of poly rhythms and this conditional is going to be put to use! Thanks again for your help!


#614

Wait- no, this is weird. It plays the same pattern and then i change some trigs around- it plays the same pattern, I press stop and play and it changes?


#615

If it’s NEI of itself, then it’s always looking at its own previous conditional trigger evaluation. The first time it hits one (beat 2) there is no previous conditional trigger so it’s false and on an NEI trig, so there’s no trigger. The next time it hits one (beat 4) it’s looking at the previous trigger from beat 2, which was false - but it’s an /NEI so it’s a trigger. Then the next bar those would be reversed because the next Beat 2 NEI would be looking at the previous bar’s beat 4 which was true, so it is also true. and so on…

The manual doesn’t say track 1’s neighbor is itself, but I’m just thinking it must be because of that behavior… if it was just looking at a ‘blank’ nonexistent neighbor track, then it would be 1,3,4 every time.


#616

Sorry that’s too vague for me to explain!


#617

Ahhhhh! I think I FINALLY understand it- I was hoping it would be a choke/slave relationship- but it’s actually much more intricate than that.

Thank you for bearing with me!


#618

Regarding neighbour track of track 1, the manual is not very clear. It states the neighbour track is the track before the active track. Going by that the list looks like this:

Track 1 is the neighbour of track 2
Track 2 is the neighbour of track 3
Track 3 is the neighbour of track 4
Track 4 is the neighbour of track 5
Track 5 is the neighbour of track 6
Track 6 is the neighbour of track 7
Track 7 is the neighbour of track 8
Track 8 is the neighbour of track 1

Maybe @eangman can tell us if that list is correct and make enlighten us a bit on the neighbour conditions.

(off topic but why is the English used in the manual American English? I would so much prefer neighbour instead of neighbor and colour instead of color :sunglasses:)


#619

If the nomenclature is consistent with A4MK2, the last item of this list is incorrect. The manual states on p. 68: “In this way track 1 can be sent to track 2, track 2 to track 3, track 3 to track 4”. There’s no mention of the output of track 4 being sent to track 1.


#620

I have no idea, the Digitakt manual is very limited on this and only gives 1 example; that track is 3 is the neighbour of track 4.

The neighbor track is the track before the active track. For example, track 3 is the neighbor track of track 4. NEI and N̅E̅I̅ conditional trigs on track 4 evaluate the conditional trigs placed on track 3. The NEI condition is false if no condi- tional trigs exist on the neighbor track.

That’s all it has. The word neighbour only exists twice in the whole manual :sweat_smile:


#621

Hi!

Quick question. Is it possible that the latest firmware may have a bug on samples names?

It happened to me that some of my samples’ name have changed or dissappeared and when I try to correct them I get an ERROR message.

Thank you!


#622

Hi!

Quick question. Is it possible that the latest firmware may have a bug on samples names?

It happened to me that some of my samples’ name have changed or dissappeared and when I try to correct them I get an ERROR message.

Thank you!


#623

A post was merged into an existing topic: Digitakt 1.04 : Bug reports


#624

Not sure it covers your issues but when I made a duplicate name by mistake it dissapeared.


#625

After some investigation into the code of the Digitakt concerning the neighbor track functionality, this is how it works:

Audio track 1 is the neighbor of track 2 and it is also the neighbor of itself (making the NEI conditions work like the PRE conditions on track 1).
Audio track 2 is the neighbor of Audio track 3.
Audio track 3 is the neighbor of Audio track 4.
Audio track 4 is the neighbor of Audio track 5.
Audio track 5 is the neighbor of Audio track 6.
Audio track 6 is the neighbor of Audio track 7.
Audio track 7 is the neighbor of Audio track 8.
Audio track 8 is the neighbor of MIDI track 1.
MIDI track 1 is the neighbor of MIDI track 2.
MIDI track 2 is the neighbor of MIDI track 3.
MIDI track 3 is the neighbor of MIDI track 4.
MIDI track 4 is the neighbor of MIDI track 5.
MIDI track 5 is the neighbor of MIDI track 6.
MIDI track 6 is the neighbor of MIDI track 7.
MIDI track 7 is the neighbor of MIDI track 8.
MIDI track 8 is the neighbor of no track.


Trig Con NEI on Track 1
#626

gah! this one has caught me out many times with sudden jumps in tempo - usually to the global default of 120.


#627

Was hoping for an update for the weekend


#628


#629

1.05 is out :metal::star_struck::metal:


#630

Check now :smiley: