Rytm - Note Parameter & Lock Trigs [Bug]

Elektron Gear Analog Rytm
1

One of the many things I like about the AR, is that if you don’t lock the note parameter, you can use the note parameter to quickly transpose an entire track up or down while improvising. Now for as long as I had my rytm (3 years+) I have run into the issue where this on occasion suddenly stopped working in the middle of a session. Since this always happened in the heat of the moment, I always regarded it to be user error (and clearing the track always fixed the problem). Yesterday though, I realized that that is not the case, since this time it happened around the end of my session and I now have a project saved in the bugged state to study:

The problem:

  • DVCO on track 3&4, no samples.
  • only the tune parameter on the src page has p-locks
  • the note page and al the other pages have zero p-locks
  • track 3 is not responding to the note parameter changes
  • track 4 is responding to note parameter changes
  • no scenes or perfs set/active

What fixes the problem:

  • Clearing track 3 (or track 4 if it happens on that one)
  • Removing one or more trigs and putting one trig back. Just removing one trig is not enough.

What doesn’t fix the problem:

  • changing the p-locks to src-tune
  • clearing the p-locks to scr-tune
  • changing the mute state of the unaffected track (in this case track 4)

This has only happened to me on either track 3 or 4 while both tracks use the DVCO machine, so maybe it’s related to the choke group, but the fact that I only noticed it in that context doesn’t mean anything since I have no clue how to recreate it, so I can’t test that hypothesis. Same goes for the DVCO, it might happen with the other machines as well.

Made a short video documenting the issue:

Any thoughts? Somebody else ran into the same problem?

2 Likes
2

I’ve noticed something like this, brb gonna test

Edit: because this was proving unreliable I started mapping the src tune to a perf knob and using that instead - which is more useful for getting to the exact pitch you want. Just a lil side note

3

Thx for confirming that it’s not just me :pray:t2: Any idea/hunch/lead on how it arises/happens? Did it ever happen to you outside of the chokegroups/DVCO? :thinking:

Will definitely send it in to elektron as a bug report one of these days, but being a software developer myself, I generally find that the chances of a bug being fixed greatly increase when they are reproducible :joy:

I’m aware of your proposed workaround, and this does indeed get around the unreliability of the note parameter. Putting aside for a moment that this should be reliable and is clearly a long standing bug that should be fixed somewhere along the line, I’m curious:

“which is more useful for getting to the exact pitch you want”

Why would you say that? just because it is reliable? :thinking: Because beside being able to determine the range yourself instead of having to work with the 4 octaves that the note parameter gives you, I see only a bunch of disadvantages.

4

I mean cus you can’t define the limitation of the note parameter so you might miss the note you’re looking for, only relevant for switching to exact notes of course :slight_smile:

Had a wee go at reproducing it on other choke groups but didn’t have the same problem, but Gonna try more machines

5

Oh :hushed: nice, I figured out what’s happening here, it’s much simpler than I thought. It has nothing to do with choke groups and it happens on every track.

If you place a lock trig (yellow) and then make it into a note trig (red) by pressing it in grid record mode, it is no longer affected by the track note parameter but will use the last played note value instead. Trig previewing such a trig does work as expected however copying the trig (also to another track), copies the trig in the bugged state.

1 Like
6

For anyone wondering about this, elektron confirmed it as a bug :slight_smile:

4 Likes
7

Hi there, just bought a second hand AR and discover I got that bug everywhere but pad 1 and 2, so annoying ….