Akai Questions today OS update.

Question/Comment :
Hello I wonder if going to do further updates of the operating system of Akai MPC 5000 because I have found many such bugs in handling the track mute, q-link and the application of hard disk recording .

I wrote several times but did not give me an honest reply to what can happen with regard to the issue of updates to Akai MPC 5000 if I can give you a reply like that do not have access to such information would appreciate it greatly digest me where I have to run to give me an answer on this.



Best regards.


Akai say:

As far as new OS updates, we do not hear of what’s coming in advance but only once they become available on our website. What specific issues are you having?


Mi say:

Specific problems I have are the following:

"Recording to disc with high latency.
"The Q-link knobs running out of time when running both in recording and in play.
Track mute and next-sequence do not respond well to the times they are put that is 1 / 16 etc. ..
"Listening to the samplers from mode / disk must be done from the F5 button would be very well able to do it directly from the pads.
Trim-mode does not work with precision with the MPC1000 and 2500 to ike chop mode nor responds well to the adjustment (the hard disk so these functions could also lead directly without having to resort to TRIM again. )

The automation is not working properly as it should be.

I would like more verifications added that if the machine such that in the next paragraph we could record the sequence sequence as is done in track mute mode 1 / 16 etc ...

I am a total fan I have 3 models MPC500 MPCS, mpc2000 and MPC5000 to work in line with Ableton Suite and would appreciate greatly if that would make users and devote their time to further develop the OS for all their machines because this type of machines are instruments conttinua rise even though the OS is not developed with the dedication that should be.


Best regards.

I got the same reply to. They requested me to send them the problems and they will forward it to the weekly meetings they are having.

It made me wonder if this site/users has send a bug list to Akai on aregular basis. According to another thread Akai is under the impression that the 5000 is stable.

I would have sent many complaints and as always it is a shame that this company be so irresponsible with their productos.Se users focus more on working with Ableton removing plastic hardware tools in their own half and leaving them without upgrading to interesting reforms.

Hopefully JJOS put your hand on his MPC 5000 and get the most they deserve the users of this tool as creative.

Greetings to everyone.

Pd: continue to send my complaints weekly Akaipro.com encourage you to make a barrage of complaints directly to them not only in this forum.

Response from Akaipro = ""crickets"".

D

you should maybe write to alesis to get a bugfix...since the 5000 is based on the fusion...


and there goes another akai os tread....

pull-over wrote:you should maybe write to alesis to get a bugfix...since the 5000 is based on the fusion...


and there goes another akai os tread....

well why not just cut to the chase and write numark who owns both akai and alesis at that point.

Numark's contact info is exactly the same for both companies .

'Akai say:

As far as new OS updates, we do not hear of what’s coming in advance but only once they become available on our website. What specific issues are you having?'

This indicates to me a severe lack of organisation and communication within the company.

Why must everything be secretive and why must the user and investor in their products be treated with such contempt ?

Would it hurt to say that they are working on a bug-fix for the mpc5000 or an OS upgrade ?

I would have thought that it would increase sales of this ( potentially ) great machine if the showed their ongoing commitment towards the mpc5000 and stopped acting like they were inside some nuclear bunker during the cold war.

It dos not instil confidence - it promotes fear ( that the mpc5000 has stopped being supported ) and loathing ( that they are unwilling to share information with their users ).

Like I said. Akai is under the impression that we users find the 5000 good as it is. If we don't regularly send them emails with complaints and wishes nothing is going to happen.

Akai has weekly meetings to discuss stuff. So i'm going to copy/paste the wishlist and just send it to them on a regular basis untill I get banned.

The situation seems to be more like, the line is in it's twilight. Why spend money on an OS for a machine that on it's way out. Akai has moved past the MPC's.

I completely agree with psiagarik about the current situation, nothing to add to that whatsoever.

I've just sent a 5000 bug report to Akai, got a response within a couple of hours that it would be checked out. I'll continue to send these as I find them.

What would be great would be a 'submit a bug' form on their web site, which in turn would be reviewed, verified and then added to a public bug list. For a start, this would stop people re-submitting the same bugs all the time - it would also provide great transparency and stop the overall feeling that the product has been abandoned.

Actually, that gives me an idea - I could set up something like this on MPC-Tutor.com - I could then submit the current bug list on a regular basis to AKai. This would at least give people a list of reported & verified bugs, hence saving them the time to submit them personally, plus letting them know that at the very least Akai have been informed.

Any thoughts? I'm thinking a form that specifies MPC model, OS version, and bug report. I could then verify each one and then add them to a public list of bugs grouped by MPC model. This list will indicate verification, date of submission to Akai and date of fix.

Any other ideas on what this could include?

Might be worth setting up Bugzilla for sorting bugs and feature requests, as well as giving people a place to post suggested work arounds for known issues.

I worked for 12 years as a release engineer, so am quite well versed with the reporting tools, processes and procedures that go along with them. If you want to bounce some ideas feel free to PM me, the bigger question though will be how responsive is Akai going to be to getting bug reports?

EDIT: Still might be useful to the community to have something like this to track work arounds though.

'submit workaround' option sounds good. I think bugzilla may be overkill for this, I just want something fairly simple and to the point, something bespoke I can knock up in an afternoon using php/mysql.

As for Akai response, that's the final piece in the jigsaw and I guess only time will tell. All we can do at this stage is collect the info, give that info back to the community to help them on workarounds, and keep submitting the reports to Akai as they come in. At least everyone will know that the bugs have definitely been reported.

I will also try my best to get something official from Akai about the OS development status on all MPCs.

Bugzilla is probably overkill, since it isn't customer facing for Akai, but it does help give some priority (from the community?) tracking.

Priority might be useful to track issue severity.

Example...
P1 - Data Loss, Completely Broken Feature, No Workaround Exists
P2 - Annoying Behavior, Minor Corruptions, External Workaround
P3 - Newbie Issue, Easy Workaround, Slows Workflow
P4 - All the usual annoyances that will almost definitely not be fixed

It's important to remember that where ever this lives, it shouldn't be used for feature requests. You don't want to get the two mixed up. Sure the two can go into the same email, but bugs and feature requests shouldn't be addressed in the same space if this is to be taken seriously. EDIT: And useful for current/existing users.

Anyway... what at least should be tracked in my mind would be...

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

EDIT: Duh
10) Bug Number - a sequential unique bug number/id to track the issue against.

I know it probably sounds like a lot, but I'd track at least those fields. From that you can generate something akin to 'Release Notes' so that somebody can look up their hardware and all open bugs, print out the issues and workarounds to know what they are in for.

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

MPC-Tutor wrote:'submit workaround' option sounds good. I think bugzilla may be overkill for this, I just want something fairly simple and to the point, something bespoke I can knock up in an afternoon using php/mysql.

As for Akai response, that's the final piece in the jigsaw and I guess only time will tell. All we can do at this stage is collect the info, give that info back to the community to help them on workarounds, and keep submitting the reports to Akai as they come in. At least everyone will know that the bugs have definitely been reported.

I will also try my best to get something official from Akai about the OS development status on all MPCs.

I was just going to spam them But this must be taking seriously indeed. I much apreciate what you are planning to do and will contribute as much as possible.

And ,btw, let us force them to participate in this forum. There isn't a cheaper way for a company to know what's going on with their products and their consumers. What more do they want?