MPC 5000 OS 2

scd wrote:

AWW_NAWW wrote:you are going to need more memory now
128 aint gonna cut it

Well you won't be able to load *every* sample program out there, but 128 MB is a decent amount of sample memory I should say. But if necessairy you can extend it up to 192 MB.

do you think it possible for akai to maby make a 1g ram expansion for the 5k?
I know people would go nuts if they did.
Trust me that along with extreme sample converter and what ever VSTI of your choice would be a crazy!

AWW_NAWW wrote:

scd wrote:

AWW_NAWW wrote:you are going to need more memory now
128 aint gonna cut it

Well you won't be able to load *every* sample program out there, but 128 MB is a decent amount of sample memory I should say. But if necessairy you can extend it up to 192 MB.

do you think it possible for akai to maby make a 1g ram expansion for the 5k?
I know people would go nuts if they did.
Trust me that along with extreme sample converter and what ever VSTI of your choice would be a crazy!

No, I have no idea if it would be possible to extend the maximum possible RAM in the 5k.

scd wrote:

Jauly wrote:
FX parameter automation, may this include Synth parameters too?

As it is now: no.

still 2 or 3 months at least to pass until spring.... hint, hint

thanks akai!

Congratulations to all the 5K users, this is great news for you!
Great job Akai.

Sincerely,

Forgotten 25K user

elliz wrote:Congratulations to all the 5K users, this is great news for you!
Great job Akai.

Sincerely,

Forgotten 25K user

No my brother....you are not forgotten. A brand new JJ OS has just been released for the MPC 2500:
http://www7a.biglobe.ne.jp/~mpc1000/mpc2500/

Askia Shaheed wrote:

elliz wrote:Congratulations to all the 5K users, this is great news for you!
Great job Akai.

Sincerely,

Forgotten 25K user

No my brother....you are not forgotten. A brand new JJ OS has just been released for the MPC 2500:
http://www7a.biglobe.ne.jp/~mpc1000/mpc2500/

C'mon man...
You know he meant forgotten by Akai.

SCD, I have three requests that SHOULDN'T BE HARD AT ALL TO IMPLEMENT !!!!

1) The kurzweil K series has a feature where, a midi sequencer track will overwrite data as many times as you want, WHILE RECORDING. Usually on the MPCs, after the sequence makes it's first loop, it goes into overdub mode. I would like to REQUEST that the MPC5k have a mode that will overwrite all the data on A TRACK for as long as you record.

2) This function I mentioned last year, but I don't think it was given any consideration. Since each "bar/measure" in a sequence has 960 steps, could you allow me to set a loop point within one of those 960 steps, instead of just within one bar?

Basically, this would destroy my need to tell the MPC what tempo I'm working with. All I do is get my sounds, lay down my sequence, and fine tune the ending loop point. So even if the master tempo is set at 120.00, but my playing is 90.00, it wouldn't matter because I could set the loop points wherever I want. Only problem would be, is that the tempo-synced effects wouldn't work so well.

Thank you, again.

LvngDead wrote:SCD, I have three requests that SHOULDN'T BE HARD AT ALL TO IMPLEMENT !!!!

1) The kurzweil K series has a feature where, a midi sequencer track will overwrite data as many times as you want, WHILE RECORDING. Usually on the MPCs, after the sequence makes it's first loop, it goes into overdub mode. I would like to REQUEST that the MPC5k have a mode that will overwrite all the data on A TRACK for as long as you record.

2) This function I mentioned last year, but I don't think it was given any consideration. Since each "bar/measure" in a sequence has 960 steps, could you allow me to set a loop point within one of those 960 steps, instead of just within one bar?

Basically, this would destroy my need to tell the MPC what tempo I'm working with. All I do is get my sounds, lay down my sequence, and fine tune the ending loop point. So even if the master tempo is set at 120.00, but my playing is 90.00, it wouldn't matter because I could set the loop points wherever I want. Only problem would be, is that the tempo-synced effects wouldn't work so well.

Thank you, again.

Is it me that can not count, or is it you?

1. I will make a feature request for that.

2. That sounds easier than it is I think. On what track should the loop info be set? You would need a "loop point track" or something like that? And I can think of 40+ other roadblocks. You already mention the tempo-synced FXs. But the idea is not bad at first glance. Need to think it over before I could do a proper request. And I will (think it over).

ok, both are added. We'll see.

hehe. I was going to add "individual track length", but I realized copy and paste might fix that problem.

And the loop point would be set for all the tracks within A SEQUENCE.

Thank you, again.

I wonder how JJ is feeling at the moment. And I wonder if this new OS will start a chapter for future MPC's?

homeboy should be feeling good. he took care of MPC users for almost 3 years in a big way. made money off of what he did and showed a big corporation what they were doing wrong.

not to mention, his OS IS THE REASON why akai sold as many 1000s as they did. despite there being a known flaw with the pads.

scd wrote:
Is it me that can not count, or is it you?

Request 3 was synth automation

This really should easily be implemented (as FX automation already is) and would give the MPC's synth it's owning pole position

Do you realize that you can "control" the synth externally with midi CC? Some paramters such as cutoff and resonance can be recorded on a synth track to "automate" it. What is your definition of synth automation?