MPC1000/2500 X-Large LCD w/modified JJOS

^ one sneaky way around this would be to try to sell your 2500 and then buy a new one and jump straight to 128xl from the default akai os...that way you preserve your value if jj doesn't give an update discount.

sally wrote:

(leaked by james jeffrey)

(leaked by james jeffrey)



but ... what kind of mpc is this?
you can see!

MIDI PRODUCTION CENTER!!!!!!!??????


MY 2500 IS
MUSIC PRODUCTION CENTER


IS THERE ANY DIFFERENCE?
WHAT IS BETTER, THE OTHER?

Nym you want to make smoke?
Take it if you want

It's the new 2000XL style casing skins that they have for the 2500. They also have the 2500 SE skins up now.

^ yeah, this is Mike's mpc2500 that he graciously let me borrow for testing purposes. i am clumsy as a mule on it after 8 years of MPC1000 love. it feels like i'm typing with one finger.

so i've been in communication with mike and the jj team on a couple of points.

i received a beta copy of os128xl to test this morning. i'm at work right now, so it's burning a hole in my inbox...

anyway, let me summarize my current understanding of the situation (features, etc)

currently, many bugs exist in 128xl due to insufficient testing. i will work hard to knock out as many as possible, but of course i do not use every function in every imaginable way...so there WILL be bugs that we will need help finding upon release. this is the burden and privilege of the early adopters. i can attest that being a beta tester can put you in an influential position regarding workflow fixes, FRs, etc.

to clear up some confusion (mine included), ADSR AMP was not deleted due to CPU consumption, and it may well return. i was asked - is AMP ADSR essential for DRUM pgms, INST pgms, or both? i would say primarily DRUM pgms, which are the majority of pgms used. of course, ADSR in INST pgms would be odeal as well for synth patches.

to answer the following, extremely valid question:

Will all the features of OS2XL ever be available on the OS128XL?

many deleted functions are not necessarily related to the LCD. some are functions were removed because they were deemed no longer useful, others because they interfered with deeper changes in the OS design structure. jj's primary focus is to finish programming the OS to fit/take best advantage of the large screen - then considerations may be made to bring back some older functions.

the explanation for feature gain/loss is difficult. think of it as a house. currently, we are working on the foundation in order to end up with a better building. when we take out a pipe in the basement, we need to remove/rework the kitchen plumbing. jj says that in order to get the OS out there for public use in the month of July, he needed to remove these functions to accommodate for others.

a lot has changed beneath what you see on the screen/comparison chart in this version of JJos.

Therefore, as for the function which many users need, an addition may be taken into consideration.
However, since the code of software differs from OS2XL, it may be unable to add easily.

so - do not necessarily give up on some features which are currently absent. the issue, most of the time, is not the CPU but rather the programming involved. there is a joke among programmers when clients use the expression "a simple matter of programming" ... because this is almost never the case.

Please tell that from you to the user of a forum.

thnaks for the heads up

Nym wrote:^ yeah, this is Mike's mpc2500 that he graciously let me borrow for testing purposes. i am clumsy as a mule on it after 8 years of MPC1000 love. it feels like i'm typing with one finger.

so i've been in communication with mike and the jj team on a couple of points.

i received a beta copy of os128xl to test this morning. i'm at work right now, so it's burning a hole in my inbox...

anyway, let me summarize my current understanding of the situation (features, etc)

currently, many bugs exist in 128xl due to insufficient testing. i will work hard to knock out as many as possible, but of course i do not use every function in every imaginable way...so there WILL be bugs that we will need help finding upon release. this is the burden and privilege of the early adopters. i can attest that being a beta tester can put you in an influential position regarding workflow fixes, FRs, etc.

to clear up some confusion (mine included), ADSR AMP was not deleted due to CPU consumption, and it may well return. i was asked - is AMP ADSR essential for DRUM pgms, INST pgms, or both? i would say primarily DRUM pgms, which are the majority of pgms used. of course, ADSR in INST pgms would be odeal as well for synth patches.

to answer the following, extremely valid question:

Will all the features of OS2XL ever be available on the OS128XL?

many deleted functions are not necessarily related to the LCD. some are functions were removed because they were deemed no longer useful, others because they interfered with deeper changes in the OS design structure. jj's primary focus is to finish programming the OS to fit/take best advantage of the large screen - then considerations may be made to bring back some older functions.

the explanation for feature gain/loss is difficult. think of it as a house. currently, we are working on the foundation in order to end up with a better building. when we take out a pipe in the basement, we need to remove/rework the kitchen plumbing. jj says that in order to get the OS out there for public use in the month of July, he needed to remove these functions to accommodate for others.

a lot has changed beneath what you see on the screen/comparison chart in this version of JJos.

Therefore, as for the function which many users need, an addition may be taken into consideration.
However, since the code of software differs from OS2XL, it may be unable to add easily.

so - do not necessarily give up on some features which are currently absent. the issue, most of the time, is not the CPU but rather the programming involved. there is a joke among programmers when clients use the expression "a simple matter of programming" ... because this is almost never the case.

Please tell that from you to the user of a forum.

Cool. It looks like a big upgrade.

Nym wrote:^ one sneaky way around this would be to try to sell your 2500 and then buy a new one and jump straight to 128xl from the default akai os...that way you preserve your value if jj doesn't give an update discount.

I could do that, but currently Im lookn at replacing the sensors I dont think this work out in my favor or breaking even....guess I'll ride this one out til my next mpc

Great news Nym is beta testing also love JJ working from the ground floor up.However it is still going to be a gamble not being a try before you buy.O.S. Props JJ Props mpcstuff. My opinion TYPO

.However it is still going to be a gamble not being a try before you buy.O.S

yes, this is unfortunately true for people who have already invested in os2xl/os2/os1
for those who are new to jjos who would buy a screen anyway, they will be able to try before they buy.
for this reason i will try my hardest to show different functions being used as i become familiar with them. of course, with jjos, this is somewhat of a moving target as features develop and the OS evolves as a whole. right now i'm working on a good AV recording system (got a document camera, it's good but has no audio input so i have to record audio/video separately and sync it up after the fact....not ideal) so i can take requests from folks.

Thanks for the news!

No idea an MPC could do all that............. Akaipro are you watching??!! Idiots!

konc3pt wrote:Im bascially throwing $150 out the window and that thought is not sitting well with me.

Nah man, you paid $150 for all the work you did with the product.

And not only that, you supported the developer of a product you like, which enabled him to not only maintain and improve that particular product, but also to make new products that you would probably like...

And third, look at that **** display dude! And them **** screenshots! My only beef with JJOS is the sheer number of screens, and the fact that sometimes he had to stuff too much info into a particular screen. Now, he has some SERIOUS elbow room to work with.

mp3 wrote:Now, he has some SERIOUS elbow room to work with.

In screen real-estate terms yes, but it'd be nice to know what kind of additional strain (if any) this screen is putting on the machine.

it'd be nice to know what kind of additional strain (if any) this screen is putting on the machine.

this is somewhat of a miscommunication. CPU strain is apparently not a big issue here - i have acquired a translator to assist with future difficult communications.

part 2

will the 128 support ndc?, that's most important feature to me

mp3 wrote:

konc3pt wrote:Im bascially throwing $150 out the window and that thought is not sitting well with me.

Nah man, you paid $150 for all the work you did with the product.

And not only that, you supported the developer of a product you like, which enabled him to not only maintain and improve that particular product, but also to make new products that you would probably like...

And third, look at that **** display dude! And them **** screenshots! My only beef with JJOS is the sheer number of screens, and the fact that sometimes he had to stuff too much info into a particular screen. Now, he has some SERIOUS elbow room to work with.

I agree with you 100%, I really had no regrets making that payment to JJ for the work he's done for us. I mean if it wasnt for him I wouldnt even touch mpc. all I really want in 128 edition is ndc