Forum to discuss all matters relating to the MPC1000 and MPC2500 operating systems created by 'JJ' (all versions).
User avatar
By distortedtekno Fri Oct 26, 2007 4:46 am
-----------------------------------------------
Bug fixes & Change: Ver4.88 25-Oct-2007
-----------------------------------------------
1.[PAD Senser]
PAD sensitivity is corrected.
Velocity level is corrected.

2.[GRID]
TYPE=MIDI
When TAP TEMPO is pushed, a display is sometimes strange.

3.[OTHER]
F3[FOOT SW]
REC+START and OVER DUB+START are added.

4.[TRIM]
F6[EDIT]
Edit:BIT CONVERT
Over write is added. 5.Timing Correct value remembered.
User avatar

By Lithion Fri Oct 26, 2007 4:49 am
chuch.


am I to assume the pad sensitivity on this version fixes the pad issue?
User avatar

By Mr modnaR Fri Oct 26, 2007 6:01 am
Lithion wrote:chuch.


am I to assume the pad sensitivity on this version fixes the pad issue?


no, you'll still have to buy the pad upgrade. :lol:
User avatar

By joeybells Fri Oct 26, 2007 10:34 am
TC value remembered...
is that what I think it is!!!

:shock:
User avatar

By bees80 Fri Oct 26, 2007 11:27 am
sounds good.. i just can't work on my mp with the dead pads :(

By earwolf Fri Oct 26, 2007 12:41 pm
Lithion wrote:chuch.


am I to assume the pad sensitivity on this version fixes the pad issue?


when you assume, you make a Kawai K1 SysEx dump of sound bank (original name = A104.syx) out of Head: F0 40 00 21 00 03 00 00 53 74 61 72 20 43 68 6F 69 72 54 01 32 4F 3E 02 29 00 30 1B 32 32
User avatar

By Antonym Fri Oct 26, 2007 1:25 pm
895KB


:wink:
User avatar

By Antonym Fri Oct 26, 2007 1:25 pm
2.[GRID]
TYPE=MIDI
When TAP TEMPO is pushed, a display is sometimes strange.


thanks, jj.

By what what Fri Oct 26, 2007 1:42 pm
i don't feel the huge difference. the pads are still hard as **** to get into higher velocities
User avatar

By Antonym Fri Oct 26, 2007 2:09 pm
low velocities are now achievable. here's what the programmer emailed me:

Hi nym
About PAD sensitivity

PAD SENSITIVITY = at the time of 16
The problem used as lowest achievable velocity = 8 corrected.

A threshold was not necessarily changed.
The bug was in PAD level to Velocity.
It became clear that AKI OS V2.11 had not changed the threshold.
How to check.
AKAI OS 2.10 and OS2.11
1.[SHIT]+BANK D C B A ->Display PAD TEST screen
2.F2[VLO255]
3.push pad very gently
4.display lowest level = 20

AKAI OS 2.11 and OS 2.10 the same value is displayed by both.
20-255 -- It changes into > Velocity 1-127.
20=PAD ON treshold.

NEW OS part2 was succeeded.
part1 and part2 can use them now, changing.
JJ


basically, previously we could only get a low velocity of 8 on sensitivity 16. now, we can get lower.

however, the CEILING is still too high for full 127 hits.
basically, we need to get more sensitive than 16. 16 should be the middle, IMO, and we should be able to pull the ceiling DOWN so lighter hits trigger higher values.

still a little work to be done but progress is being made with the jj os. isn't it always?

By what what Fri Oct 26, 2007 3:19 pm
i managed to get higher velocity ratings in the akai 2.11 os at lower force, so why i can't get a decent one now pretty much sucks.

By master-ceo Fri Oct 26, 2007 3:36 pm
Oh shoot, Thanks for the info G. :) :) :) :) And special thanks to JapaneseGenius :idea:
User avatar

By Antonym Fri Oct 26, 2007 3:57 pm
what what wrote:i managed to get higher velocity ratings in the akai 2.11 os at lower force, so why i can't get a decent one now pretty much sucks.


as i said, its because the ceiling needs to be pulled down - or better yet just give us more sensitivity settings.
User avatar

By Lithion Fri Oct 26, 2007 4:47 pm
earwolf wrote:
Lithion wrote:chuch.


am I to assume the pad sensitivity on this version fixes the pad issue?


when you assume, you make a Kawai K1 SysEx dump of sound bank (original name = A104.syx) out of Head: F0 40 00 21 00 03 00 00 53 74 61 72 20 43 68 6F 69 72 54 01 32 4F 3E 02 29 00 30 1B 32 32



:lol:

By arzes Fri Oct 26, 2007 5:15 pm
Was the play start + stop on the foot switch option added on and of the versions before or are we still awaiting that?