Final O.S. Feature Requests...

^^^Nah, I'm gonna wait for 4k vets like Feline/Knoxx/etc. to chime in...

...Then hopefully narrow the list down to applicability, then rank in order (#1-most wanted, and so on), then send it to Akai Pro, with some other suggestions as well...

Better get your skates on with this - do you know how long software development takes? maybe they have already finalised a v2.0 and are testing it? If not, and you are gonna hand them a list like this, and expect half the stuff to be done, then give it 6 to 18 months from when you hand in the list for an update.

Giving the guys a list with 20 or 30 points, some of which are hard and / or imposible IMHO, nothing will happen.

They need a list of a) Bugs that need fixed b) simple and easy and memory efficent updates c) a SELECT few harder updates, of which only one or two would be done tops.

Keep it focused.

Also, the fault and / or update requests need to be explained in a short, consise way.

Finaly, keep all hardware issues seperate.

nik wrote:Better get your skates on with this - do you know how long software development takes? maybe they have already finalised a v2.0 and are testing it? If not, and you are gonna hand them a list like this, and expect half the stuff to be done, then give it 6 to 18 months from when you hand in the list for an update.

Giving the guys a list with 20 or 30 points, some of which are hard and / or imposible IMHO, nothing will happen.

They need a list of a) Bugs that need fixed b) simple and easy and memory efficent updates c) a SELECT few harder updates, of which only one or two would be done tops.

Keep it focused.

Also, the fault and / or update requests need to be explained in a short, consise way.

Finaly, keep all hardware issues seperate.

exactly but since alpha stated not to whine i kept my mounth shut

nik wrote:Better get your skates on with this - do you know how long software development takes? maybe they have already finalised a v2.0 and are testing it? If not, and you are gonna hand them a list like this, and expect half the stuff to be done, then give it 6 to 18 months from when you hand in the list for an update.

Giving the guys a list with 20 or 30 points, some of which are hard and / or imposible IMHO, nothing will happen.

They need a list of a) Bugs that need fixed b) simple and easy and memory efficent updates c) a SELECT few harder updates, of which only one or two would be done tops.

Keep it focused.

Also, the fault and / or update requests need to be explained in a short, consise way.

Finaly, keep all hardware issues seperate.

I agree with keeping hardware and software seperate.

As an FYI... many many many feature requests have been given to Akai seperately and together, for well over 18 months. So they've had plenty of development time, if they were using the resources for that, though I'm more likely to believe that those resources were being used for 1000 and 2500 development though


Another useful thing that I have found in providing bug fixes and RFE's (Requests for Enhancements) is not only say that I want Item 1 but also indicate HOW they are to implement Item 1 with their UI (User Interface). The UI's fairly limited with many of the Soft Key's already filled up and the Window key being used for most items. So you also have to make sure that they can implement your suggestion with how it could be done on the 4000. If you want to add something to the Sample Trim Screen and F1-F6 are already being used, then they might not be able to implement it. Unless it was a new "Edit" screen.

The feature requests of mine that have been implemented, have always explained in full details where and how they could place it within the UI constraints that they will have to go against.


Now of course, that is no guarantee that they will fix/add it. As I believe that Robert's detailed description on how they could implement seperate track lengths was very well written, and has been submitted to Akai for well over 2 years now

Dave

pressing the shift key and one of the F keys simultaniously, perhaps? Ive just added six more keys to the mpc´s control panel

drumtrack wrote:pressing the shift key and one of the F keys simultaniously, perhaps? Ive just added six more keys to the mpc´s control panel

I've used that in one of my requests, we'll just have to wait to see if they ever implement that.

I've also request that we get access to Sequences 97-128 and Mute's 97-128 via shift Pad Bank key.... in the Next Sequence by Pads and Mute by Pad screens....

Shouldn't take up too much more memory or code, and give us full access to what is already under the hood.

Dave

I did not read the whole list but IF nobody mentioned it how about multible undo's?

renegadebliss wrote:Another useful thing that I have found in providing bug fixes and RFE's (Requests for Enhancements) is not only say that I want Item 1 but also indicate HOW they are to implement Item 1 with their UI (User Interface). The UI's fairly limited with many of the Soft Key's already filled up and the Window key being used for most items. So you also have to make sure that they can implement your suggestion with how it could be done on the 4000.

Word, if this list finally gets trimmed down to applicable features for the 4k, then we can all contribute how to implement w/ UI....

For now, I'm just keeping it light, trying to see what other users want, incase Akai Pro is dragging their @ss, and have nothing new to present for Summer NAMM.

However, I wouldn't be mad @ all if O.S. 2.0 is ready & waiting...

As far as features for future UI's, for a 5000, I think a no-brainer would be:

1 soft "Bank" button, which you hold down, then press 1-9 to toggle between banks 1-9...

I'm really big on holding down a button, then pairing with others, for an un-cluttered UI...

multiple undos would be great!

-illiac

illiac wrote:multiple undos would be great!

-illiac

yep

oh I forgot a real simple one

the ability to audition samples from the hard drive and while in the Sample Mode via the 8 outs (instead of having to use the main stereo out)

Ability to move notes by NOTE as well as PITCH in the STEP EDIT screen just as you can in the SEQ EDIT screen.

As far as I can tell this doesn't require any change to the UI.

-illiac

I found this on the futureproducers forum

http://www.futureproducers.com/forums/s ... p?t=134701

that would begreat!
( you can already grab a piece of a sample by pushing two buttons )

Bug.....Long notes cut off unnaturally sometimes in song mode as sequences are changing.

request: External monitor support perhaps through the USB interface....