Forum to discuss all matters relating to the MPC1000 and MPC2500 operating systems created by 'JJ' (all versions).
User avatar
By King_Vitamin Mon Aug 27, 2007 6:28 am
This would be so simple to do:

The LFO screen is basically 1 step away from being a full fledged arpeggiator...all we need is the ability to shape our own LFO's.

Something like grid edit would be perfect for this. Imagine being able to set, say a 5 note arp to loop up and being able to use this as an assignable LFO.

Since the speed (stepped length of the LFO pattern) and delay features already exist in that screen, this would allow you to assign that new LFO arp to a midi synth or even samples(!) and the ability to make very elaborate patterns. Plus you could play that sh!t in realtime.

This is different from programming an arpeggio in the sequencer in the sense that your LFO arp is TRANSPOSABLE! Meaning that you can play a normal scale and have the arp loop applied to every key you hit and it will play back at the same tempo (i.e. tempo of the arp cycle stays the same regardless of pitch). Think of it as a little sub-sequence within your sequence.

Anyone with me??
User avatar

By udenjoe Mon Aug 27, 2007 10:28 pm
Is it possible to send LFO changes over MIDI? If not add that.
User avatar

By `TK Sat Sep 01, 2007 11:49 am
cool

By jimmie Sun Sep 09, 2007 2:05 am
I've just seen one of those sell on ebay! Was that you?

By jimmie Sat Sep 22, 2007 11:30 am
Not sure. Missed its ending....
User avatar

By `TK Sun Sep 23, 2007 1:50 pm
this one make's premade melody's right ? (arp.)
if its so then why do we need it ?
i can make my own melody's, can u ?
Os size is smal, means we cant have unusefull shit in it.

if this is not right then u nefer readed this

5.37
User avatar

By Zukan Mon Sep 24, 2007 3:37 pm
This is not as simple as it sounds.

An Lfo is simply a low frequency osc that modulates an event like pitch or filter etc.

It is repeatable through it's wave shape and does not create any staggered notes. So, the idea of breaking the Lfo down into note components and then being able to manipulate those components is an entirely different coding proposition than adding to the existing one.
User avatar

By Zukan Mon Sep 24, 2007 4:02 pm
I think there are acres of improvements that Akai could have incorporated into the 2500.

JJ, alas, has run out of space for os feature additions, unless some form of code compression can take place. :wink:

Personally, I think Akai missed the boat with this product. As usual, their lack of regard in dealing with customer feedback and support has led them to stick to their own arrogant ways and ignore what the market demands.
This way of thinking is prevalent right throughout the corporation's ideology.


Shame.
Had they listened and stuck to their promises, then they could have upped their game.

It's a sad day when a third party has to create an os that affords features that they cannot be bothered to implement.
They are, in effect, selling their products based on other peoples efforts.