Important: 4k bugfix update

feline1 wrote:At his own personal invitation, I sent Robert Ray @ Akai a big buglist about 18 months ago (i.e. during the Numark era). What happened to that?

I don't know. But do you still have that list? That would be of *great* help!

I probably do have it in my email archives somewhere.

Without wanting to sound like a spoilt child though, I have had the exact same offer dangled in front of me like this about 4 times now since 2002,
and each time I have spent hours of my time collating material and sent it the the nice Akai insider who "was making no promises but really trying to help",
and each time it all just vanished into the aether.

Like the bitch-to-my-MPC4k that I am, I will probably do it all again. But I won't expect a damn thing to happen about it.
KILL ME

feline1 wrote:I probably do have it in my email archives somewhere.

Without wanting to sound like a spoilt child though, I have had the exact same offer dangled in front of me like this about 4 times now since 2002,
and each time I have spent hours of my time collating material and sent it the the nice Akai insider who "was making no promises but really trying to help",
and each time it all just vanished into the aether.

Like the ****-to-my-MPC4k that I am, I will probably do it all again. But I won't expect a damn thing to happen about it.
KILL ME

Could be. But it is still worth the try. I am quite confident this update could happen. Never tried is always miss right?

Could you search for that list please? Even if it is not happening it would come handy to have a complete as possible list at hand with bugs.

I will dig it out for you. May take a day or two.

It is not all "reproducible bugs",
it also contains documentary evidence of advertised features that remain unimplemented,
document errata,
and what would no doubt be dismissed as enhancement requests ( = stuff that works in a half-assed way
But you can have it to keep on file.

feline1 wrote:I will dig it out for you. May take a day or two.

It is not all "reproducible bugs",
it also contains documentary evidence of advertised features that remain unimplemented,
document errata,
and what would no doubt be dismissed as enhancement requests ( = stuff that works in a half-assed way
But you can have it to keep on file.

That's great. Thanks in advance!

Nice to wake up to this this morning. I think, and mostly I hope, this might be an important development.

Feline, I understand your underwhemedness but I will go as far as to say we need you onboard for this

Look at SCDs thread on the 5000 forum - he is clearly not a time waster. Of course we don't know if his contact at Akai is a flake and/or about to leave... but clearly he thinks not. So I think its important to get all the info to them - you have explored the problems of the machine probably more thoroughly than anyone and you've already done the work in compiling it.

There is a chink of hope here and I have NO doubt it is the last opening with Akai we will get...

and most of all I would love to see that document go out of date!!!!!!!!!!

He's already mailing me stuff. Good.

OK. I just sent you a crapload of stuff
(All of which I already sent to Robert Ray in summer 2006)


Here's another BUG:
if you set a program to respond to POLYPHONIC AFTERTOUCH instead of CHANNEL (monophonic) AFTERTOUCH,
this is not saved and reverts to channel aftertouch when you next load it.

please also see the issues with hardwired cc's and footswitches on http://www.mpc-forums.com/viewtopic.php?t=54963

Yes, thanks a lot! I've printed out everything. Since I have a 4 hour drive to the Musik Messe tomorrow I will sit in the back of the car with a marker to make a first overview

This is a good start!

Thanks alot scd and I hope everything pans out.

I think it's in the list I sent you,
but my most ANNOYING BUG that I've found is the way
it just doesn't respond to Note Off velocity properly
(and forgets the Poly aftertouch setting)

I was very annoyed to when I hooked up my MPC4000 up to some fancy controller keyboards which supported Note Off velocity and Poly Aftertouch,
and it turned out that the MPC4000 didn't really respond to them after all:
it was supposed to be a Top of the Ranger Sampler,
instead it was teh suxz!

Changed looppoints that are saved for the second time will not load properly. OS1.5 and above...

poly aftertouch settings are not saved with the program
all OS afaik

Hi,
I'll start digging through all the emails that i sent to [email protected]
where we sent all of the bug reports to.


Boele (scd) would you be willing to publish this Bug Report once you've gotten
it together. Even if Akai decided not to update the OS, it would be nice
to get a definitive list of bugs.


The other main bug is Sysex. I don't know how many of the Feline's list include Sysex
issues.... It's probabably about time that we dig down and make sure that at
least the Sysex works as expected.

Maybe we should start a seperate thread of known Sysex commands that work
and known ones that don't work.

It shouldn't take any Code Space to fix the Sysex, since it's already taking the space. We just need them to correct the ones that don't work....



Dave