Why no JJ for 500

there just aren't enough MPC fans with that level of tech knowledge

robthom wrote:Check out the JJ os threads, there are many posts regarding that.
If I'm not mistaken, it had something to do with the only reason that JJ was able to customize the OS for the 1000 and 2500 was because they are technically similar to each other and he was a former Akai employee who had worked on those os's for Akai. And this is why he has to remain anonymous because it was somewhat legally dubious to have access to and then alter Akai's intellectual property (even though a lot of the work was his, Akai owns it). And that the OS's for the other MPC's are actually different enough that the customizations he did for the 1000 and 2500 cant be tranferred to the other models.

I dont know about OS's and programing, so I'm not sure what exactly makes them hard to crack. You see hackers cracking the OS's on playstations and xbox's all the time. But the enthusiast's working on that are legion, and it still takes them a few years. Maybe there just aren't enough MPC fans with that level of tech knowledge who can dedicate the kind of unpaid time and effort that it would take to crack one.

namotu wrote:someone intervied him or posted up and interview ... and why he won't do one for the 500...

brazeca wrote:I don't understand why people keep asking this question... Do they really think that JJ OS will boost their creativity or imagination?! 500's OS is now relatively stable and provides everything needed for effective production. Even before numerous bugs were fixed by Akaipro themselves it was operable.

namotu wrote:...post this up in the JJ forums for the 1000 and the 2500, maybe one of them will know...

stan steez wrote: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

drunken monkey wrote:
a company facing bankruptcy would have no desire whatsoever to sue one person (if we assume that JJ is in fact only 1 person).

akai have no reason to compete with JJ in the market of an MPC OS. people are paying for the hardware and the cost that JJ is charging is basically minimal in comparison to the price of the MPC unit.

remember when you are paying for a product you are paying for the R&D also.

JJ has added a lot of features to the MPC1k but the appearence of this OS has also caused a lot of confusion in regards to what actually goes into the development of a product like an MPC.


features are left out of products so that people will have incentive to buy the models that are more "top of the range" in the category.

let's not forget that when the MPC 1k was originally announced it was marketted as a portable MPC solution or an MPC for people who previously could not afford one.

in regards to "bugs" in the original OS you have to take into account how some (and i stress that word) companies go around testing their products. you are dealing with a very small user base of testers who are looking for bugs and features. i have no doubt whatsoever in my mind that if akai wanted to implement features into it's OS that JJ has already done for the 1000 then they could have easily done so.

to me the JJ situation looks like an ex-employee who has access to the source code and therefore has the ability to upgrade and maintain a third party OS.

the ammount of "assumed" knowledge and plain guessing on this forum is pretty ridiculous IMO.

the original MPC1k had some "hardware" problems but this is only to be expected when you look at the actual price of the unit. most companies are staying away from the hardware game as of late and it's becoming more and more apparent that in the VERY near future hardware could become a niche market and for akai to stick to making units like the MPC 500 and 5000 is very applaudable.