Akai Questions today OS update.

NearTao wrote:It's important to remember that where ever this lives, it shouldn't be used for feature requests. ...

I was just thinking about that over lunch - I agree, feature requests would bog everything down. We either don't bother or have a separate feature request list.

1) Bug Title - Something 100 characters or less to summarize the Issue
2) Bug Description - A description of what the issue is and how it manifests itself
3) Bug Reproduction - Steps to reproduce the bug as well as how often it occurs
4) Bug Workaround - Any ways that are available to work around the bug
5) Bug Status - Whether the bug is opened/closed
6) Bug Priority - Derived however you wanted to derive it.
7) Bug Reporter - To know who to contact in case further questions arise
Bug Hardware - Hardware that the bug exists on
9) Bug Version - Version of Firmware that the bug is reported on
10) Bug Number - a sequential unique bug number/id to track the issue against.

Sounds good.

EDIT: Who knows... at the very least might be a good way to communicate with JJ to get JJOS updates smoother.

Hadn't thought about including JJ stuff in it - will have to think about that.

MPC-Tutor has been a great idea with the initiative to propose, I intend to support 100%.

I would add a basic problem that I wish that other users of the MPC5000 I confirmaran.El problem is that the operating system and the motherboard are usually unstable sometimes freeze up losing my job arreglos.Esto reminds me very much to incorporate the MPC5000 in my directos.Cuando go from one menu to another for example track and mute to mute group here and the effects and mixer all this with the play freezes CRASHHH!

I hope this has a solution for that otherwise I will have to decide to stop using it and return to the 2500.

Awesome idea.