Akai OS2xl v1.14 up!

**** akai!! I got to say why did they do this to a machine that had hidden potential??????

eq32 wrote:

THE ADVERSARY wrote:Just turn the TC to OFF and the GRID works fine.

Yesir!! It does seem to work with T.C. off flawlessly.

So true, why didnt i think of that before wasting my time like that...

Well it should still be documented/fixed. At least there is a clear work around.

Lots of things that aren't JJ's strong point one being documentation, but still you have to look at it from a sensible point of view.
A GRID by definition makes nudging with a defined TC setting somewhat of a contradiction.
Being set to a GRID and then moving something off GRID when note positioning is being determined by the GRID is a definite point of possible breakdown.
This is the reason DAW's and Editors typically have the snap to grid function to allow you to choose between forcing notes to the grid or free movement/placement of the notes.
In OSxl you have to use the OFF setting to assure you have the fredom to move the notes with proper interpetation, which would be the equivalent to turning off the snap to grid in a DAW.
Maybe he will re-program it to work differently but remember every key stroke from JJ has a ramification.

^ very well noted.

i'll still like it when nudging can be performed with tc on or off.
i'll test this when i get a chance to install the new update, thanks for the steps, rinseout.

Confirmed for me so far: Grid Edit nudging works perfectly with TC off.
Good stuff
Would be nice to also have it work with TC on, but I'm very happy with this.

Nym wrote:^ very well noted.

i'll still like it when nudging can be performed with tc on or off.
i'll test this when i get a chance to install the new update, thanks for the steps, rinseout.

Nym, you will probably find that it works with TC on, but what happens is when you start doing chaotic jumping around the nudge field starts to lose it point of reference.
After every nudge the field should move to the new location and the nudge factor goes to "0" to signify the completion of the movement.
So basically if you nudge 3> it becomes 0 so if you then nudge <3 it will but you back where you started.
Well with the TC set for 1/16 it would occasionally become incremental and give you a nudge 3> but still keep 3 in the field, so if you then nudge again it would actually nudge you 6>.
Took me a couple of attempts to get it to start acting up and even then it was no true consistency to it.

I see no advantage to nudging with the TC, that would be beneficial it you were doing some type of auto nudge but as far as moving notes it wouldn't benefit you.
The GRID lines are still there and you have the numerical count to help with your positioning.
The only real drawback I see is that you have to remember to turn the TC back on if you want to tap in the Main sequencer screen.

JJ could make the GRID screen use TC off without relationship to the TC setting for the sequence to solve this or give them seperate setting.
Roland has that aspect of the Piano Roll or GRID Edit settings not being tied to the main screen settings to allow for more functional editing.

shift timing in the quantize screen has always worked like this: snap to quantize value, then shift forwards/backwards the chosen number of ticks. so maybe thats why it does it in the grid edit too. as it happens id much prefer that shift timiing in t.c. didnt work like that either- that way youd have the choice- quantize first and then shift, or just shift to keep the subtle timing differences of your performance

That's is true but it's not the problem per say.
The combination of the MPC quantize characterisics and things like the Strength funtion have trouble agreeing with each other in GRID mode.
One function is Static the other is Dynamic so in theory it should be either or.
If you are nudging in GRID and the note is for lack of better term being dropped between points the reference can become corrupt thus causing the desribed poblems.
This is why OFF alleviates the problem, it allows access to all and any points the MPC is capable of.

mikolo wrote:shift timing in the quantize screen has always worked like this: snap to quantize value, then shift forwards/backwards the chosen number of ticks. so maybe thats why it does it in the grid edit too. as it happens id much prefer that shift timiing in t.c. didnt work like that either- that way youd have the choice- quantize first and then shift, or just shift to keep the subtle timing differences of your performance