sequencing and nudging steps - 0-100% seems confusing

[clay]

when programming drums using the move sequencer

- i select the first two 16th notes for a bass drum groove - first two steps are lit up
- i nudge the 2nd 16th note to the left so its a bit rushed
- the 2nd step light turns off
- I now seem to have two beats on the first step

how do i access each beat separately so i can change the nudge value of each or the pitch, note length etc?

I'm not sure but this seems to be a limitation of the sequencer and how it handles note nudging 0-100% rather than +50%-. If I nudge the 2nd step backwards it moves to the first step, rather than still staying as the 2nd step.

Hopefully I'm just missing a way to select between beats on the same step?

[[jur]]

Try momentarily switching the steps resolution to 1//32 when you're nudging.
This should prevent the step's led to turn off when you'll go back to 1/16.

[clay]

thanks. I will give that workaround a try

[Jayude]

This really does need a change in how it works. I agree with how you were expecting it to work - rushed notes should remain on their intial step up to a certain amount. -1 to like -49% is one way of looking at it but I guess it could be less than that, something like maybe -9% ? So then a swung step would be on its initial step up until 90%.

I started a thread early on about this. There's a few competing ways of thinking about it plus it gets complicated when you start needing to select parts of a bar or when switching clips for example but yeah, simply rushing something a little shouldn't put it on the step before.

[Jayude]

Well I didn't expect to fall into another trap with the shift function less than two hours after posting my last reply!

I recorded a beat 100% live by tapping in the pads. Groove was fairly good. Took a couple goes to capture n micro shifted things by a couple percent here and there. As can be the way with live grooves I don't think a single hit was on a strict 16th step, some slightly early n others swung a lot. The groove worked in any case.

I felt the last 16th of the bar was too swung so I kept on trying to shift it earlier but confusingly it was wasn't sounding any different. I had looked past the fact that when I selected the step it showed a box with two values i.e the range of multiple notes. So what I was adjusting was the 1st and last notes of the bar at the same time To push the 2nd note of that last step to the very start of the bar so I could then shift solely the last 16th would've altered the feel too much. Plus of course, when I start the clip it skips what is functionally the first note of the bar because the Move has recorded it as if it's a extremely late last 16th step.

This is a fundamental problem with how the Move handles shifted notes.

[JeffX]

+1000 on this one!

For me, this is certainly the biggest drawback with the Move's step sequencer

in music, a note that arrives just before the beat is just as common as a note that arrives just after the beat
and it's absurd to light on the 16th step of a bar (for example) with an offset of +90%, when “musically” it's obviously the 1st step of the following bar, which falls just a little before the beat...

To avoid this, MIDI sequencers generally adopt offsets over a range of -49%/+50%

Ableton, please correct this point


PS:
I also need to add another request..
(I'd probably have to make a dedicated feature request
but the 2 problems are so close..since they concern step offset)
when a step is held down, the current offset of this note should be displayed on the screen
for the moment, we have to shift with the arrows to find out this value, but if we just want to check the information, we shouldn't have to do so