New JJ Os For The 2500 Is Here. Check It Out.

is there a stereo chop shop? if so im gonna send jj my love juice

Manilla wrote:is there a stereo chop shop? if so im gonna send jj my love juice

Yeah, JJ finally managed to make the chop shop usable!

version 3.02
http://66.249.93.104/translate_c?hl=en& ... n%26sa%3DN

maxim1 wrote:version 3.02
http://66.249.93.104/translate_c?hl=en& ... n%26sa%3DN

I'm guessing this is the latest OS from the JJ. Will this one be the finished product??

Nah, my guess is there will be quite a few more 3.xx versions and then a commercial 4.xx version with some tasty new features. That's what happened with the 1000.

yeah your probably right.

I don't really care to look in the 1000 forums,but how is the 1000 JJ OS holding up. I wonder if it's really buggy??

No need to wonder..its is buggy. Just check the JJ page. Its lists some/all of the bug fixes. With every new OS version, its seems something is added and something is broken that previously worked.

I see alot of happy users in the 1000 forums aswell. The JJ OS has taken the mpc1000 to places no one ever thought it would go.

I'm hoping he'll do the same for the 2500. The tone in our 2500 forums seems to be quite negative about JJ's OS. IMHO he should be praised and encouraged. It's early days. There's bound to be bugs because it's still in development, but I think there's a bright future

Rozzer wrote:The tone in our 2500 forums seems to be quite negative about JJ's OS. IMHO he should be praised and encouraged.

yeah, sad thing is all the negativity comes from only one guy...name starts with j and ends with e.

Red Ketchup wrote:

Rozzer wrote:The tone in our 2500 forums seems to be quite negative about JJ's OS. IMHO he should be praised and encouraged.

yeah, sad thing is all the negativity comes from only one guy...name starts with j and ends with e.

Actually the response is more positive since he fixed:
-The Detect Tempo
-MTC
-and possibly the file problem

Things Akai has been slow about.
Akai has done a good job of debugging but they didn't get those dealt with.
Unfortunately they have to work on scheduled projects and can't just jump

Sovereign wrote:Akai has done a good job of debugging but they didn't get those dealt with.
Unfortunately they have to work on scheduled projects and can't just jump

akai has done a VERY bad job with the OS, and unfortunately, the programming team (which is probably 1 or 2 guys) is either a bunch of lazy bastards or just being mismanaged by their bosses.

another observation: there's a few ungrateful bastards here. JJ's OS is an option, we get it for free, and yet we still complain? if i were JJ and read this forum i'd say **** you america and the rest, I'll keep my own custom OS just for me & my mates here in Japan. so at least be glad that YOU HAVE AN OPTION. akai didn't give you an option at all, just a buggy OS.

-Red

<---- passes a spliff round the thread and makes some JJ grateful beats

Red Ketchup wrote:

Sovereign wrote:Akai has done a good job of debugging but they didn't get those dealt with.
Unfortunately they have to work on scheduled projects and can't just jump

akai has done a VERY bad job with the OS, and unfortunately, the programming team (which is probably 1 or 2 guys) is either a bunch of lazy bastards or just being mismanaged by their bosses.

-Red

Dude you make no sense.
Akai only has a few unanswered bugs.
Get real.
One the Tempo Detect was a design choice.
The MTC got broken because when they originally added it they had a problem with it disabling the transport controls.
When they fixed that it seperated the receive start that MTC sends.
The file system problems aren't something that everyone experiences, but did it exist prior to trying to be compatible with the XL files?
The programmers aren't free lance they have to follow scheduled agendas and that means work on a given project before moving to another.
The OS is far from buggy.
And understand Jahrome's son did not cause his problem.
When I first loaded v3.02 I selected Input Thru and the unit crashed.
Came back up since it just basically did a rest and then began to do a reset everytime I selected a function.
Did a total shutdown waited a while then turned it back on and it was fine.
That's a h*ll of a bug.
The only thing I can see that Jahrome and I have in common is the the 40g Toshiba, 128 and CD-M25, other than that nothing that would make the units crash other than the JJ OS.
While I am running the JJ OS currently because of 2 things it fixed I know it's risky.
But recent convo with Akai lets me know not to worry things will pan out so I'm good limping arpound with the JJ OS.
As it stands I would pay the $30 or whatever for the December version unless he could actually get the 2500 code.
Still too many little things that don't work quite right because of the differences in the 1k and 2500, that are kinda annoying when working.
If you purchased an early 2500 then you can fully appreciate what Akai has debugged and quickly they did it.
If you got one more recently then it's transparent.
No different than the 1k people talking about all JJ has done without remembering what the 1k was before Akai upped it.
People on this forum talk about software programming like they can do it themselves yet most have trouble even programming their MPC.
If Akai is doing such a bad job they should program your own code.

Sovereign wrote:Dude you make no sense.
Akai only has a few unanswered bugs.
Get real.

hey buddy, you have valid points, but i disagree with you, because a "few unanswered bugs" are MTC not working and the file corruption on HD that most here who DO work for real on actual music projects have experienced...

I call that SERIOUS BUGS that a serious company should not let out of the manufacture.

take a step back, look at the whole picture, there are problems at akai, no doubt.

Music is what I do and I have had no issues with saving, creating folders or any file functions.
In fact in 8 months the only crash/freeze/reset I have experienced was with the JJ OS v3.02.
Think of the Akai programmers just like any other job, they do what the people paying require you to do.
If some one wants a their mix a certain way that's what I give, if they want a certain type of track that's what I try to give.
It's the same for them.
If Akai say finish coding the 500 that's what they had to do.
If they said work on XYZ then that's what they have to do.
If the 2500 would have been based on the XL OS that would be one thing but for a new product with a turn in direction to be down to less than 5 real bugs in a years time is actually good.
Yes there are companies with bug free products but they are actually re-incarnations of previous technology they had or have been around for more than 2 years.
The original MPC2k had it share of issues for quite some time, the XL wasn't bad since it was an improved OG 2k.
My point is not to defend Akai but to state the reality of the situation.
Akai's true mistake was waiting too long to declare bankruptcy.
It's what stalled the progress of the 4k as well as caused them to past control of the company to another entity.
At least they are still around, when it happened to Ensoniq it ended them.
Red, look at it like this it's like you walk in your kitchen to get something to drink but before you can drink something that you purchased with your own money you have to call me and ask if it's ok.
In Akai's situation they have to get more done with even less staff than they had previously.
But hey they do have a current job posting.