Forum to discuss all matters relating to the MPC1000 and MPC2500 operating systems created by 'JJ' (all versions).
User avatar
By Jungleman Tue Oct 11, 2011 5:49 am
Bug fixes & Addition:MPC2500 OS-XL Ver3.04 11-OCT-2011
--------------------------------------------------------------------------------
1. [GRID MIDI]

An event is not erased even if the ERASE button is pressed after OVER DUB+PLAY START.

2. [AUDIO TRACK]

Cursor is strange when cursor is moved to the LEVEL field from the LOOP field.
Moreover, adjustment of LEVEL, PAN, and OUT cannot be performed.

3. [SEQ EDIT]

[DURATION]
TO NEXT NOTE
There is no duration in the last note.
The last note extended duration to the last of a sequence.

4. Duration of the last note is not recorded with the right value.

Duration of the last note does not stop record in the position which canceled REC/OVER DUB.
It will be recorded to the position where the STOP button is pressed.

5. [PATTERN]

1. PC is not outputted even if it play back the pattern with which PC event is contained.

2. A mute event is not registered.

3. It may freezes, if it converts when the number of the bars of END of LOOP is odd.

<<Change>>
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.

2. The screen of PATTERN BANK was changed.

The pad (note) used for the pattern is displayed.

<<Addition>>
1. It is F4 (AllTrks) button addition to the mode of pad mute.

Usually, although it works only on an active track, if F4 (AllTrks) button is pressed, it will work on all the tracks.

2. It is F2 (PadChng) button addition to the window of "Pad event move to other track".


If F2 (PadChng) button is pressed, the window of "Pad (Note) Number Change" will open.


An event is moved to other pads (note).

3. [PROGRAM]

The value of a parameter will be copied if the [UNDO] + or cursor key is pressed in the window of "LAYER".

If the [UNDO] + cursor key is pressed in the state of the above figure, the value of TUNE will be copied to a layer 2.
User avatar
By le rat Tue Oct 11, 2011 7:13 am
2. It is F2 (PadChng) button addition to the window of "Pad event move to other track".


If F2 (PadChng) button is pressed, the window of "Pad (Note) Number Change" will open.


An event is moved to other pads (note).


I am curious to see how that one works. Waiting for the 1k version to be uploaded.
User avatar
By distortedtekno Tue Oct 11, 2011 7:14 am
le rat wrote:
2. It is F2 (PadChng) button addition to the window of "Pad event move to other track".


If F2 (PadChng) button is pressed, the window of "Pad (Note) Number Change" will open.


An event is moved to other pads (note).


I am curious to see how that one works. Waiting for the 1k version to be uploaded.

It's already uploaded. :)
User avatar
By Jungleman Tue Oct 11, 2011 9:44 am
Nice additions, I think this might be just the right time to make the switch... I've been busy working on a project, so didn't have the time to check out v3 yet.

A minor dislike:
"The Device field was lost."
I actually found it quite useful, as I'm working with lots of midi hardware and have different setups for live and studio.

And I don't get this:
"A system memorizes a setup of Pad to MIDI CC out and Pad to MIDI PC out.
Ver2.xx = A program memorizes.
Ver3.xx = A system memorizes."

So, in v2, you save Pad to MIDI CC/PC out settings by saving the current program, right?
How to do it in v3? Save SYSTEM SETUPS? ENTIRE MEMORY? ALL_SEQS&SONGS?
User avatar
By distortedtekno Tue Oct 11, 2011 10:49 am
And I don't get this:
"A system memorizes a setup of Pad to MIDI CC out and Pad to MIDI PC out.
Ver2.xx = A program memorizes.
Ver3.xx = A system memorizes."

So, in v2, you save Pad to MIDI CC/PC out settings by saving the current program, right?
How to do it in v3? Save SYSTEM SETUPS? ENTIRE MEMORY? ALL_SEQS&SONGS?

If I'm correct, I believe it gets saved as "SYSTEM SETUPS".
User avatar
By le rat Tue Oct 11, 2011 11:31 am
distortedtekno wrote:
And I don't get this:
"A system memorizes a setup of Pad to MIDI CC out and Pad to MIDI PC out.
Ver2.xx = A program memorizes.
Ver3.xx = A system memorizes."

So, in v2, you save Pad to MIDI CC/PC out settings by saving the current program, right?
How to do it in v3? Save SYSTEM SETUPS? ENTIRE MEMORY? ALL_SEQS&SONGS?

If I'm correct, I believe it gets saved as "SYSTEM SETUPS".


I ve just asked and I was told that it was saved in the internal memory.
User avatar
By mikolo Tue Oct 11, 2011 3:06 pm
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.
User avatar
By consuming Tue Oct 11, 2011 3:25 pm
Jungleman wrote:So that would mean there is only one global set of Pad to MIDI CC/PC out settings, instead of per program?


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


This is an awkward setting. Hopefully, it's not mandatory for the feature and we'll see a per-program-basis setting as well. It's strange to have patterns/cc settings on pads pop up from a previous project, especially before completely learning the new structure.

JJ is so fast with the bug fixes.