Frankly speaking, it is a shame that Elektron did not manage to fix the “wrong octave LED” bug with 1.35.
A bit of history: This used to work perfectly (on MkI machines) up until 1.24c. The “wrong octave LED” bug was introduced with the 1.30 for MkII machines (I forgot when this was released), alongside with ugly sibling: the “wrong note LED” bug, which meant the A4 MkII’s mini keyboard was completely useless, as it showed wrong note and octave LEDs for p-locked notes.
Elektron fixed the “wrong note LED” bug with 1.30b in late December 2017, but they did not fixed the “wrong octave LED” bug. I simply do not understand how Elektron managed to fix the “mini keyboard LEDs display wrong note values”, while at the same time not fixing the “mini keyboard LEDs display wrong octave values”, because you simply can’t verify that the first bug (wrong note LEDs) has been fixed, without noticing that the second bugs (wrong octave LEDs) still exists.
I filed a support ticket for this in March 2017 and had high hopes that the 1.35 would fix this. There has been a time when this was working, at least with A4 MkI’s…but alas it looks like neither the engineer implementing this nor the QA person testing this seem to think that this central point of the A4 MkII’s visualization of music is worth fixing.
I so wish Elektron would have never started the Overbridge project, as it seems to draw all their attention into the wrong direction…away from solidly working, reliable hardware music making boxes.