Bug fixes & Addition:MPC2500 OS-XL Ver3.04 11-OCT-2011

mikolo wrote:looking forward to this.. nice one on the undo key in the pad layers window.

Jungleman wrote:So that would mean there is only one global set of Pad to MIDI CC/PC out settings, instead of per program?

thats true.. same for the pattern settings too unfortunatley. Id of prefered it on a per program basis too.

cosign. it should be saved per program.

consuming wrote:JJ is so fast with the bug fixes.

economic slave's in a workshop?

1. [GRID]

Behavior of the STEP button was changed.
When the type of a track is DRUM, a vertical marker is moved to the next event or back event on a horizontal marker, by a SHIFT+ <BAR> button.

Not sure I understand this entirely. Is this just an addition, or did something actually change?

^ i requested that one. it's tricky to explain but extremely useful.

the best way to explain is to go into MIDI grid, record a performance, then go back to the start.
then, hit shift+bar >
note that the cursor moves to the next note
continue to hit shift+bar>
note that the cursor moves to the next note again (and so on).
the best part about this is for editing specific notes timings then quickly moving to the next instead of whirlin the data wheel.

now, in DRUM edit, the old behavior was to move the cursor horizontally, but not vertically.
so if you recorded pad A01 and pad A16 and tried to "move to next note"
vertically, you'd still be on A01 but horizontally you'd be at the time of A16.

this is good for editing NV data
but it's also especially powerful for various macros.

Nym wrote:^ i requested that one. it's tricky to explain but extremely useful.

the best way to explain is to go into MIDI grid, record a performance, then go back to the start.
then, hit shift+bar >
note that the cursor moves to the next note
continue to hit shift+bar>
note that the cursor moves to the next note again (and so on).
the best part about this is for editing specific notes timings then quickly moving to the next instead of whirlin the data wheel.

now, in DRUM edit, the old behavior was to move the cursor horizontally, but not vertically.
so if you recorded pad A01 and pad A16 and tried to "move to next note"
vertically, you'd still be on A01 but horizontally you'd be at the time of A16.

this is good for editing NV data
but it's also especially powerful for various macros.

I like this feature and was excited about it the first I read about it (nice request by the way) easier to edit now. Question how are you using it with macros?TYPO

I get it... Very nice. Thanks for explaining Nym.

I like this feature and was excited about it the first I read about it (nice request by the way) easier to edit now. Question how are you using it with macros?TYPO

i haven't written the macros yet, but the idea is to create a series of macros for "edit next/prev note X" where X = note variation data...

i am using your idea of a keyboard to do this for now, eventually considering a whole DIY surface but a keyboard really is just too convenient of a midi controller when all you're doing is triggering actions.

so like...the key combination A+rightarrow = jump to next note NV ATTACK
S+rightarrow = jump to next note NV sample start
etc.

i've been critically underutilizing NV stuff ever since os2, i guess
i used it a lot more in the akai os, but these days i just am more quick to reach for the multisample. however, especially the sample start bit is really, really useful and i'd like to use it more.

for me, it's all aobut eliminating the hassle between the function and the user. the easier it is to GET there, the more i'll use it, and the better i'll be at it....i'm sure you can dig that

Nym wrote:

I like this feature and was excited about it the first I read about it (nice request by the way) easier to edit now. Question how are you using it with macros?TYPO

i haven't written the macros yet, but the idea is to create a series of macros for "edit next/prev note X" where X = note variation data...

i am using your idea of a keyboard to do this for now, eventually considering a whole DIY surface but a keyboard really is just too convenient of a midi controller when all you're doing is triggering actions.

so like...the key combination A+rightarrow = jump to next note NV ATTACK
S+rightarrow = jump to next note NV sample start
etc.

i've been critically underutilizing NV stuff ever since os2, i guess
i used it a lot more in the akai os, but these days i just am more quick to reach for the multisample. however, especially the sample start bit is really, really useful and i'd like to use it more.

for me, it's all aobut eliminating the hassle between the function and the user. the easier it is to GET there, the more i'll use it, and the better i'll be at it....i'm sure you can dig that

I am going to work on this feature as well.I do feel that it can become lightning fast with a proper macros.Nice work as always.PEACE TYPO

Nym wrote:^ i requested that one. it's tricky to explain but extremely useful.

the best way to explain is to go into MIDI grid, record a performance, then go back to the start.
then, hit shift+bar >
note that the cursor moves to the next note
continue to hit shift+bar>
note that the cursor moves to the next note again (and so on).
the best part about this is for editing specific notes timings then quickly moving to the next instead of whirlin the data wheel.

now, in DRUM edit, the old behavior was to move the cursor horizontally, but not vertically.
so if you recorded pad A01 and pad A16 and tried to "move to next note"
vertically, you'd still be on A01 but horizontally you'd be at the time of A16.

this is good for editing NV data
but it's also especially powerful for various macros.

Tried this out and it now runs the way it should... Vey nice. I never used the shift for this but deffinately will now!

About the GRID button change...

It's listed on the MPC 2500 bug fixes page, but it doesn't seem to do anything on the 2500.

Since the 2500 already has [STEP] buttons that move through the events, is it a 1000-only feature? Or can you explain in a simpler way how to verify it works on the 2500?

if the vertical pad selection moves when you step from note to note, then it works.
if the vertical pad selection stays selecting the "last pad triggered" then it has not been implemented yet.

If I'm getting this right, say you have a sample triggered only in the first beat of each measure in the first track and sixteenth notes triggered in the second track. In the older version, even though your editing the first track it will send you to the next note of the sequence which would be the next 16th note, even though that event is in another track. This way it will bring you to the next event in that track only... skipping all of the 16th notes in a track you arent editing. Hope that I explained that right. Hope i'm even understanding this right.

Oh I think I understand, the only thing that changed was how it moves to the next event.

It used to be, that in GRID EDIT for a DRUM track, if you jumped to the next event, it'd move forward to it in time (x-axis), but the pad (y-axis) didn't move, so you'd have to move it to the pad with the event for it to intersect.

Now what happens, is it will only move to the next event for the currently selected pad. So if your pad line is set on A01, and the next event in time is on pad A02, before it'd jump in time to A02, but now it does not.

This is different than the MIDI mode when OVER DUB is on. In there, it jumps forward to the next event in time, but it also moves the note line automatically for you, and underlines that note, jumping around in both x/y.

The reason why I was confused, is because it says, "SHIFT+ <BAR>". On the 2500 there is both a [STEP] and a [BAR]. So I kept trying to hold [SHIFT] while pressing the [BAR] arrow keys. This does nothing different!

My guess is, the MPC 1000 does not have a separate [STEP] and [BAR], so for 1000 the "SHIFT+ <BAR>" is how to emulate a [STEP] < >. The bug fix entry for the 2500 then is wrong, and it should just say [STEP].

In 3.04, with DRUM, if you want to jump to the next event, and it's on another pad, you have to hit that pad first. With MIDI it goes to the next event regardless of note. I can see why someone would want it to work that way.

But maybe it'd be nice to go to the next event regardless of pad in DRUM mode? That's what I thought was going to happen, if I held [SHIFT] while pressing the [STEP] keys. The pad (x-axis) line still is stuck where it was.

Nym wrote:

I like this feature and was excited about it the first I read about it (nice request by the way) easier to edit now. Question how are you using it with macros?TYPO

i haven't written the macros yet, but the idea is to create a series of macros for "edit next/prev note X" where X = note variation data...

i am using your idea of a keyboard to do this for now, eventually considering a whole DIY surface but a keyboard really is just too convenient of a midi controller when all you're doing is triggering actions.

so like...the key combination A+rightarrow = jump to next note NV ATTACK
S+rightarrow = jump to next note NV sample start
etc.

i've been critically underutilizing NV stuff ever since os2, i guess
i used it a lot more in the akai os, but these days i just am more quick to reach for the multisample. however, especially the sample start bit is really, really useful and i'd like to use it more.

for me, it's all aobut eliminating the hassle between the function and the user. the easier it is to GET there, the more i'll use it, and the better i'll be at it....i'm sure you can dig that

Thanks for explaining the new feature Nym. This is definitely very useful to have and speeds up the editing process.