Good News! I think.

Well, this discussion will get you all nowhere, what you should do is to contact the JJ dude himself and an employee from akai and then make your own opinion in this case. Or.. you can carry on for ever and ever

True...

I wish I knew the whole true story though.

Okay I asked Akai if they were currently working on a new OS for the MPC500 and this was their response.

This Is My Question To Them:
I heard that Akai Pro was working on a new OS update for the MPC500. Is this true? If so, will it have Chopshop and when will it be released?

Thanks For The Help.



Akai's Response:
Hello,

It's not known when a new OS upgrade will be released for the MPC 500
as the
engineers do all of development in the secret 'batcave'. We just hear
of a
new OS once it has been posted to the website. However I can bring the
chop
shop 2.0 feature request to their attention.


Best Regards,
Justin Baro

Akai Pro Technical Support
200 Scenic View Drive
Ste.201
Cumberland, RI 02864
401-658-4032





So yeah now Im really confused. The guy didnt really answer my questions.

engineers do all of development in the secret 'batcave'

its just alfred doing the work in the batcave now... bruce wayne left a long time ago.

Seriously dude that guy straight beat around the bush on that question.

I guess their aint no new OS coming out for the 500

One akai employee says its coming and other one says naw, why the hell do anyone believe on these akai people anymore? same shit when 1000 came out, akai is a real bad customer service company. Now they are pissed off when 3rd party coder does a succesfull and maybe most stable os in any mpc ever and they start to put bad rumors about them (jj)

Guys, please. Hope you will take my word for it: Akai *is* working on a MPC500 update.
Probably the employee that's talked about above has no "clearence" to say anything about it or he just doesn't know, which makes perfectly sense.

But in the first post in this thread the answer from Akai came from a person I know (I talked with him about this post) and he is the guy responsible, so the MPC500 update is worked on. And Chopshop 2 will be added. With the named restrictions as said before. But no release date yet.

Boele

After corresponding with the support guy of the JJ site (Murai), he gathered a statement from Hayashi about the situation and forwarded it to me. Although I don't understand every bit of it, because it's translated badly, Hayashi makes clear, that he is in fact not JJ and also explains his ties to AKAI and also takes a stand to the accusations made in the email that DollarBinDarrell got from AKAI, about JJ stealing code from the AKAI OS. Following is the unedited statement of Hayashi:

The following translates into English the comment which JJ obtained from HAYASHI.

JJ is no comment about this.

HAYASHI-> JJ -> MURAI->stan

The comment of HAYASHI
------------------------------------------------------------
I am HAYASHI.
I am not JJ.
The name of JJ is HASEGAWA.
JJ was my assistant.
He wrote a part of code of MPC.
I am not the employee of AKAI.
I am the manager of a software developer.
My company had contracted with AKAI (JP).

I wrote MPC2000, MPC2000XL, and the code of MPC4000, MPC1000, and MPC2500.
These were not necessarily written by only me.
I am only the member of a team.

"Akai professional" was a Japanese company.
November 30, 2005.
AKAI(JP) went bankrupt suddenly.
The engineer of AKAI (JP) lost his job.
I also lost my job.

After one week.
Since the same amount of money as former was paid from AKAI (USA), there was a request "Continue work."
I decided to continue this work.

There were two things for which money is not remitted even if it sends a bill.
I and AKAI (USA) had trouble.
The end of April, 2006.
I sent the bill for April to AKAI (USA).
Money was not remitted even if two week had passed.
There was also no connection.
It was the 3rd time now.
I asked AKAI (USA).
AKAI(USA): -- "discount Pleas whose wages of yours are too high."
I told AKAI(USA) good-bye.

OS (MPC2500) of my last was released immediately.
I was surprised, because I will not do work of AKAI from now on.
But they have released without testing the OS.
Correction of a bug will generate a new bug.
This is repeated and, finally a bug is lost.
It took in three years until OS of MPC2000XL was stabilized.
I do not make a bug intentionally.
A bug is generated even if it does not carry out it.
The number of the bugs of MPC4000 was about 1800.
The number of the bugs of MPC1000 was about 800.
These are the bugs in the middle of development.
These are set to 0 and released.
A new bug is still discovered.
It was required for six more months to stabilize MPC2500.
----------------------------------------------------------------------.
After three weeks June, 2006.
I got to know the bug of "SYSTEM ERROR".
I told the agency (japan) of AKAI (USA) as follows.
USA -- "please correct" -- if it says, I will correct.
However, the reply did not come.
----------------------------------------------------------------------.
[he even broke the MTC on the MPC2500 before he left us].
When a new bug is corrected, it is an everyday occurrence for the portion which was operating normally to break.
AKAI should correct any bugs.
The engineer who went away is irresponsible.

As for MPC1000, two persons' software engineer other than me wrote the code.
They went away two years ago.
The serious bug existed also in the code which they produced.
I corrected them all.
After I go away, the engineer of AKAI should correct.

When asking me for correction of a bug, I corrected it.
You did not do it.

[he stole our code].
I want AKAI (USA) to cancel about this affair.
May, 2006.
AKAI (USA) and AKAI (JP) had fought for the ownership of the OS code.
I do not know whether it was ended whether the argument would continue now.
I had contracted with AKAI (JP).
When was the contract ended?
I think that it is an important problem.
I have not contracted with AKAI (USA).

P.S
I liked work of MPC.
I think that highest MPC2500 was made when continuing.
The staff of MPC is good people.
They love MPC.
It is not their responsibility that a bug is not repaired.

Since AKAI (USA) did not treat me carefully, I went away.
I will not be concerned with MPC from now on.

HAYASHI

the company was just too damn cheap to pay the engineers...? damn...

so akai jp went bankrupt.

jj stopped working on all mpcs os because of no pay.

akai usa took over and told jj to carry on his work.

akai usa didnt pay jj for the work he put in.

jj stopped working for akai usa.

is this the way it has panned out?

where does this leave us jj os users?

the MPC500 update is worked on. And Chopshop 2 will be added. With the named restrictions as said before. But no release date yet.

just a question for you scd.
you mentioned earlier that chopshop for the 500 will only import the chopped files, you wont be able to create them because of the lack of a graphical interface.
Since all chopping on the 500 lacks this interface, couldnt you have a "blind" chopshop for the 500:
Cut the sample into slices, arrow keys switch between chops,pad plays the current chop, data wheel adjusts the start time. if you can hear the chops thats more important than being able to see them.

mikolo wrote:

the MPC500 update is worked on. And Chopshop 2 will be added. With the named restrictions as said before. But no release date yet.

just a question for you scd.
you mentioned earlier that chopshop for the 500 will only import the chopped files, you wont be able to create them because of the lack of a graphical interface.
Since all chopping on the 500 lacks this interface, couldnt you have a "blind" chopshop for the 500:
Cut the sample into slices, arrow keys switch between chops,pad plays the current chop, data wheel adjusts the start time. if you can hear the chops thats more important than being able to see them.

But then you would only be able to set startpoints not endpoints, won't that be a problem (I am completely not into chopping )

I meant start and end points but didnt say it .
for example : Shift and arrow right :end point. shift arrow left: start point.
without the shift key: right/left would jump between slices.
start of one slice would also be the end of the previous slice.
and some way of dividing/combining adjacent slices.

mikolo wrote:I meant start and end points but didnt say it .
for example : Shift and arrow right :end point. shift arrow left: start point.
without the shift key: right/left would jump between slices.
start of one slice would also be the end of the previous slice.
and some way of dividing/combining adjacent slices.

OK, I see what you mean. Not sure if Akai would embrace such a kind of solution, but asking won't hurt right?

yeah. cool thanks!