mpc1000_jv131.os2 Jul 13, 2010

--------------------------------------------
Bug Fix: OS2 Ver1.31 13-JUL-2010
--------------------------------------------
1. [GRID]

[16PAD loop edit mode]
An event may be unable to be erased.

*badum tish*

i reported this to JJ a couple days ago. quick fix!

BUT, there was one other problem i reported to him at the same time that he didn't fix. i'm going to mail him again and see what's up.

Yesterday, July 13, 2010, I noticed on the website of jj, which gave birth to the update of os2 for mpc 1000, ver. 1.31.
and I noted that today July 14, 2010, jj has left everything to change the date.
happened to change the date?
a question I get,
also modifications in the version, or what happened? are these the same? have changed anything?
We are vigilant in apricot (jj) ...

you should make the call OS3, and start from 0, because as you know, we have fundamental and elementary errors.
for example to improve and complete.

CC from outside to inside the mpc. also to control the possible duration of the note (from the external device) Imagine, our mpc, would become a real analog sequencer, or very similar.

and a long list of upgrades ..
this is my suggestion for jj, in reply to version 1.31.

jandpoint - i have no idea what you're talking about there. i know you are not a native english speaker but that post is really hard to understand.

good news - i got a message back & JJ is still working on the other issue i mentioned, it's just taking a bit of time so he released this update to at least get this fix out there.

just for the record, here are the bugs i reported:

this first one was just fixed:

1. open a new sequence (DRUM track type) and go to GRID EDIT

2. press NUMERIC to enter LOOP EDIT mode

3. put the cursor on the PAD 6 row

4. press some pads to enter events

5. press those same pads again to erase the events

BUG: the events do not erase.

this only occurs on PAD row 6 (in all banks A,B,C,D)

...and this one has NOT been fixed yet but JJ is working on it:

example: a user has recorded some events, and wishes to go into GRID EDIT and delete those events and put a different event (a different pad) in the exact same space as the deleted one so the timing is the same.

1. open a new sequence and record some events.

2. go to GRID EDIT (DRUM track type) and put the cursor on the row you wish to edit.

3. use the STEP button (SHIFT + BAR keys) to move from event to event, until you reach the one you wish to delete.

4. press DELETE (f4)

PROBLEM: the cursor moves forward a small amount when DELETE is pressed.
it may become impossible to move the cursor back to the original location because the cursor only moves in 4 'tick' increments (even with QUANTIZE off).
example: from time location 001.01.00 to 001.01.04

request 1: that cursor does NOT move when DELETE is pressed.
request 2. that cursor move in 1 tick increments when QUANTIZE is off. (from 001.01.00 to 001.01.01)