Grid edit: nudge notes - JJOS2XL v 1.12 - mpc2500

Hi.
1) Load up a hi-hat sample and assign to pad A01 of a drum program
2) Leave TC at default (1/16, strength 100%, swing 50%)
3) set sequence bars to 1
4) turn loop on
5) hit rec+play
6) hit note repeat and pad a01
7) hit mode +pad15
8) hit overdub and move to the fourth hi-hat which is at 001.01.72
9) hit shift and ^ and nudge the hat three places right to 001.01.75
10) hit cursor down arrow and afterwards hit overdub to turn overdub off
11) hit overdub and move to the fourth hi-hat which is at 001.01.75
12) hit shift and ^ and nudge the hat three places left to 001.01.72
13) Notice that the drum hit will not move.
14) Try nudging the hat (at 001.01.75) 4 places to the left and it moves left 1 place to 001.01.74.
15) Try nudging the hat (at 001.01.75) 1 place to the left and it moves right 2 places to 001.01.77!!
16) Try nudging the hat (at 001.01.75) 2 places to the left and it moves right 1 place to 001.01.76.

Is this how it's meant to work cos it's very confusing?

Cheers

Just me then?
I've submitted this to JJ, but surely it can't just be me. I thought loads of people must nudge their hits in grid edit.
Nym?
Anyone?

i'll try this today and get back

hey sorry, i missed this post but not the bug.
i reported similar stuff happening with TC off in drum grid edit (notes aren't moved at all!)
and i've also noticed funky nudging stuff in tc values in drum grid too.
and midi grid, nudge is completely wacked! all these bugs have been reported and checked by murai so we will hopefully expect a fix soon.

thanks jimmie

this technique doesnt seem to work for me

sorry - do you mean you can't reproduce this?

i tried to nudge a note and it didnt nudge.

Cheers for gettin back to me on this.
Trying to work out the "nudge logic" in OS2XL has sent me loopy a few times and I kinda keep letting it stop me in my creative tracks, so I'm waitin for this to be fixed now, which I'm sure won't be long.

is there an easy way to nudge that i am missing?? when you have overdub on, it then seems a pain to hit shift and ^ to get to the top bar. surely a shortcut would be better, so that all you do is get the crosshairs on the note you want to move and then you could use any L/R/up/down arrow key to bump them

shift ^? all i do is hit f4 EDIT and navigate to the TIME section.
i would like if the cursor darted to the TIME section as soon as f4 edit is hit instead of to the nv section.

I sent what I wrote in my first post to JJ. I received an email from JJ on Wednesday. I only just found it^^
Anywayz, JJ replied with:

"
Please refer to the following on-line manual.
http://www7a.biglobe.ne.jp/~mpc1000/os2 ... _drum3.htm
"

In the manual it says that the nudge value is "the difference from TC position", but it's messed up with whatever TC values I use.

Ok.
I have a pre-recorded drum hit at 002.01.89 that I want to move to 002.1.95 in grid edit.
How do I do it and it make sense?
I found that nudging it 5 to the right does it.
Now if I try to nudge it 5 to the left it goes to 002.1.91!!
wtf? It's like trying to hit a moving target!

I replied to JJ's mail asking him to please re-read what I wrote.
He replied with:
"
The bug of the report was understood and checked.
It corrects by the following version.
"

Big cheesy smiley-face from me
rarrrrrrrrrrrrrr! At last

is that a pirate rarrrrr or a tiger rarrrrr? I guess pirates sound more like arrrrr... but I've never met one in real life.

i reported these, i believe they're related:

DRUM GRID EDIT DISPLAY:

1- load project, set bars to 8
2- create a drum track
3- record a pad performance
4- enter DRUM GRID EDIT
5- hold SHIFT and hit CURSOR RIGHT
6- BUG: grid display breaks.
7- NOTE: this does not occur in MIDI GRID EDIT.
8- NOTE: it appears that this bug creates a bug for NUDGE NOTE

v
--1: create 8 bar sequence
--2: record a performance. record a performance near 8.4.00
--3: hold SHIFT and hit CURSOR RIGHT to A, move to the note, and B, to
recreate the above bug
--4: EDIT note and attempt to nudge it
--5: BUG: a note is not nudged logically.


the first one checked, the second was irreproducable but i think it has to do with your bug, jimson