Hi,
All happens in the Editor.
Open editor
Go to sequencer.
Open a sequence, or make one in the editor.
Make sure that (Pattern) sequencer and Latch is ON.
In sequencer Go to step 1 or 2 or whatever, (Is depending on how many steps you make) and move the mouse in pitch 1 Just one tone DOWN…OK?
The pitch goos up…!?!
Small bug…°!°??
Warm regards Luloop
Was already mentioned here: http://forum.moogmusic.com/viewtopic.php?p=152069#p152069
There I wrote, that it happens only once, if you edit the step the second time, it’s ok. But now, I tried and saw, that it also happens twice (unpredictable), if you edit the same step a third time it is ok …
cheers,
Bernard
Hi,
It happens also after the third time. I should say…It happens unfortunately all the time.
And I am talking about all the steps no matter what step you change.
Warm regards Luloop
Here are my notes:
Affects Pitch 2 also. Velocity and Mod are unaffected.
Happens every time, every note, active or not (i.e. bright or dimmed).
“Pull” the value down slightly, and it bumps up a half-step before returning to the starting note, and finally decreases as you drag farther. It’s easy to do with three-fingers on the trackpad: just place them, and roll them down slightly. See the “#” every time! (well, except for B0 → C1 and the like, but you know what I mean).
I don’t need Latch On or Sequence On to see the problem. I’m running standalone, with no connection to the hardware, testing with the sequence from the preset ‘Across the Sky’. On the ancient 0.9.40 (sorry).
I can confirm there’s some intermittent weirdness.
I believe this only happens when Globals>Seq Options>Ref Note = FIRST, and not when Ref Note = MID C.
The bug is due to a logical problem with ref note = FIRST mode… playback of the sequence is always transposed according to the note you play to trigger the sequence. In Ref Note FIRST mode, playback is transposed so that the first note of the sequence plays at the pitch of the note used to trigger the sequence. Not just the first note but all notes are transposed of course,relative to the first note.
So if playback is latched or otherwise ongoing, and you edit the pitch of the first note of the sequence, this should logically change the transposition of the whole sequence, according to the rule above.
Except, when you’re editing a single note you don’t want to change transposition for the whole sequence.
So there’s some code trying to handle these different scenarios correctly, but it seems it can still get confused on repeated edits.
I will look at this…
IME it doesn’t matter which step your editing and it happens always, regardless of the performance mode.
Hi Luloop, I understand now. I was referring to a behavior on the hardware, in response to editing pitch of sequence steps (especially the first note).
You are talking about a behavior of the Pitch 1 / Pitch 2 value boxes in the editor when being adjusted by the mouse, entirely independent of any response from the hardware. Sorry I missed this distinction earlier. Alles klar 
Ha Ha ! Can’t stop laughing!
How did you know?
He’s a dutch man, living in Belgium (in the part where they talk french), but because he’s an open minded guy, he is talking german too!
Tot ziens!
Bernard
hyvää päivää.
Me to..haha haaa… Did not know that Amos can speak our language.
terveiset Luloop.
BTW
In 0.9.42 / 1.1.22 I think the problem is gone.
Still testing
Finnish? Now I’m really confused.
My German vocabulary extends as far as “Ein Pils bitte” and “Genau!” That’s about it really.
Yes it’s gone now, thanks to your efforts in getting the idea through my thick head. 
Firmware 1.1.23, Editor 0.9.43:
Seems to work now.
Thanks for verifying.