By le rat
Mon Sep 02, 2013 3:51 pm
Hello everybody,
I've decided to create this topic to explain what's behind this compatibility issue, share experience and try to find solutions.
That's a problem, people who switch from -AKAI OS, FREE OS, OS1 or OS2?- to -OS2XL, OS3 and 128XL- have to face and the online manual doesn't really help.
http://www7a.biglobe.ne.jp/~mpc1000/os2xl/important.htm
http://www7a.biglobe.ne.jp/~mpc1000/os2xl/pad_to_note3.htm
I've redrawn some schemes and will try to explain differently.
I) BACKGROUND
Basically what do we have in the MPC? DRUM tracks and MIDI tracks :
We are supposed to use DRUM tracks with the internal sampler and MIDI tracks with external devices but we won’t necessarily
One of the reason why is : the track type has an influence on others functions (SEQ EDIT or GRID EDIT for instance). Depending on our OS and our workflow we’ll prefer to use one type rather than the other.
What’s the relationship between PAD number and MIDI note number?
By default it follows a GM standard like this one : http://www.midi.org/techspecs/gm1sound.php#percussion
Range goes from note #35 (pad C14) to note #98 (pad D16). It is customizable into this range and data are stored in the program file.
The screenshot above is precisely taken from PROGRAM mode.
There is the same screen in MIDI/SYNC mode, it’s useful for MIDI tracks when there’s no programs assigned. Nevertheless, in this mode data are not stored by the system and are overridden if a program is finally assigned.
STEP EDIT screen when a DRUM track is used (data managed per pad):
STEP EDIT screen when a MIDI track is used (data managed per MIDI note event) :
II) Potential issues
All the problems start when we want to use MIDI keyboards, sound modules with DRUM tracks or programs with MIDI tracks. Traditionally MPC users are using blank programs with the right MIDI note assignment to prevent those issues and keep a coherent MIDI signal flow.
What’s explained in the online manual here http://www7a.biglobe.ne.jp/~mpc1000/os2xl/important.htm is a comparison between old default assignment and new default assignment (therefore regardless of users blank programs)
I’ve redrawn some schemes :
OLD DEFAULT ASSIGNMENT:
NEW DEFAULT ASSIGNMENT:
Please note that the old assignment is #35-#98 and the new assignment #36-#99
Compatibility issues between old and new assignments:
DRUM track perspective:
Example: in an old project made with an old OS, if you had pad A2 responding to incoming MIDI #36, A1 will be triggered instead in a newer OS version. On the contrary if you had pad A1 sending #37 it will now send #36.
MIDI track perspective :
example : If you had A01 triggered by #37, it is now triggered by #36
For experienced users who are already using blank programs, the only issue is : the new range is #36-#99 instead of #35-#98.
III) Current state (based on OS2XL)
To sum up the current state with few words : the new -pad number / MIDI note number conversion table- is fixed against MIDI IN. It can be considered as a new limitation for some people.
The NOTE tab in MIDI/SYNC mode (see above) has been removed.
The behavior against MIDI OUT is still customizable. See http://www7a.biglobe.ne.jp/~mpc1000/os2xl/midi_out3.htm and updated block diagram below :
It’s possible to trigger pads with #CC thanks to the BUTTON function http://www7a.biglobe.ne.jp/~mpc1000/os2xl/button.htm
What can we do when we have a compatibility problem?
Well the first thing to do is nothing
It’s better to try to remember which project was made on which OS and to stick with it.
Otherwise, there is no miracle solution. All have to be done manually. So it’s better to understand what’s going on and to change things at the program level or in STEP or SEQ edit…etc
Recently I’ve read a topic in which saving/reloading .mid files could be a solution. http://www.mpc-forums.com/viewtopic.php?f=25&t=124757
Personally I had a big compatibility issue when I had to reload projects made in OS1. I was triggering my s950 (#35-#98) and at the same time doing layering with DRUM programs inside the MPC. I had keygroups assigned to #35 in my s950. It was a mess when the new system was introduced.
*OS1 users beware of autochromatic assignment : http://www7a.biglobe.ne.jp/~mpc1000/acae.htm
*Something else to mention : Multitimbrality/Track 10/ NOTE24-35 http://www7a.biglobe.ne.jp/~mpc1000/os2xl/multi3.htm
IV) conclusion
My simple advice is : if you plan to update to a newer OS one day (OS2XL, OS3, 128XL..etc) you’d better use blank programs starting with #36
By the way if something I wrote is wrong don’t hesitate to tell me so I can correct my mistakes and update the first post.
I don’t use MIDI much on my setup. I don’t use a computer either with my MPC. If you had specific issues with MIDI or computers please share them. Any others thoughts, recommendations, solutions concerning this compatibility problem are welcome.
PEace
I've decided to create this topic to explain what's behind this compatibility issue, share experience and try to find solutions.
That's a problem, people who switch from -AKAI OS, FREE OS, OS1 or OS2?- to -OS2XL, OS3 and 128XL- have to face and the online manual doesn't really help.
http://www7a.biglobe.ne.jp/~mpc1000/os2xl/important.htm
http://www7a.biglobe.ne.jp/~mpc1000/os2xl/pad_to_note3.htm
I've redrawn some schemes and will try to explain differently.
I) BACKGROUND
Basically what do we have in the MPC? DRUM tracks and MIDI tracks :
We are supposed to use DRUM tracks with the internal sampler and MIDI tracks with external devices but we won’t necessarily
One of the reason why is : the track type has an influence on others functions (SEQ EDIT or GRID EDIT for instance). Depending on our OS and our workflow we’ll prefer to use one type rather than the other.
What’s the relationship between PAD number and MIDI note number?
By default it follows a GM standard like this one : http://www.midi.org/techspecs/gm1sound.php#percussion
Range goes from note #35 (pad C14) to note #98 (pad D16). It is customizable into this range and data are stored in the program file.
The screenshot above is precisely taken from PROGRAM mode.
There is the same screen in MIDI/SYNC mode, it’s useful for MIDI tracks when there’s no programs assigned. Nevertheless, in this mode data are not stored by the system and are overridden if a program is finally assigned.
STEP EDIT screen when a DRUM track is used (data managed per pad):
STEP EDIT screen when a MIDI track is used (data managed per MIDI note event) :
II) Potential issues
All the problems start when we want to use MIDI keyboards, sound modules with DRUM tracks or programs with MIDI tracks. Traditionally MPC users are using blank programs with the right MIDI note assignment to prevent those issues and keep a coherent MIDI signal flow.
What’s explained in the online manual here http://www7a.biglobe.ne.jp/~mpc1000/os2xl/important.htm is a comparison between old default assignment and new default assignment (therefore regardless of users blank programs)
I’ve redrawn some schemes :
OLD DEFAULT ASSIGNMENT:
NEW DEFAULT ASSIGNMENT:
Please note that the old assignment is #35-#98 and the new assignment #36-#99
Compatibility issues between old and new assignments:
DRUM track perspective:
Example: in an old project made with an old OS, if you had pad A2 responding to incoming MIDI #36, A1 will be triggered instead in a newer OS version. On the contrary if you had pad A1 sending #37 it will now send #36.
MIDI track perspective :
example : If you had A01 triggered by #37, it is now triggered by #36
For experienced users who are already using blank programs, the only issue is : the new range is #36-#99 instead of #35-#98.
III) Current state (based on OS2XL)
To sum up the current state with few words : the new -pad number / MIDI note number conversion table- is fixed against MIDI IN. It can be considered as a new limitation for some people.
The NOTE tab in MIDI/SYNC mode (see above) has been removed.
The behavior against MIDI OUT is still customizable. See http://www7a.biglobe.ne.jp/~mpc1000/os2xl/midi_out3.htm and updated block diagram below :
It’s possible to trigger pads with #CC thanks to the BUTTON function http://www7a.biglobe.ne.jp/~mpc1000/os2xl/button.htm
What can we do when we have a compatibility problem?
Well the first thing to do is nothing
It’s better to try to remember which project was made on which OS and to stick with it.
Otherwise, there is no miracle solution. All have to be done manually. So it’s better to understand what’s going on and to change things at the program level or in STEP or SEQ edit…etc
Recently I’ve read a topic in which saving/reloading .mid files could be a solution. http://www.mpc-forums.com/viewtopic.php?f=25&t=124757
Personally I had a big compatibility issue when I had to reload projects made in OS1. I was triggering my s950 (#35-#98) and at the same time doing layering with DRUM programs inside the MPC. I had keygroups assigned to #35 in my s950. It was a mess when the new system was introduced.
*OS1 users beware of autochromatic assignment : http://www7a.biglobe.ne.jp/~mpc1000/acae.htm
*Something else to mention : Multitimbrality/Track 10/ NOTE24-35 http://www7a.biglobe.ne.jp/~mpc1000/os2xl/multi3.htm
IV) conclusion
My simple advice is : if you plan to update to a newer OS one day (OS2XL, OS3, 128XL..etc) you’d better use blank programs starting with #36
By the way if something I wrote is wrong don’t hesitate to tell me so I can correct my mistakes and update the first post.
I don’t use MIDI much on my setup. I don’t use a computer either with my MPC. If you had specific issues with MIDI or computers please share them. Any others thoughts, recommendations, solutions concerning this compatibility problem are welcome.
PEace