MPC X sometimes "looses" keys

Hi all - and especially AKAI Pro teams.

There was an incident which occurred a few times before yesterday evening. During recording some MIDI sequences, all of a sudden a "D" key on my synth stopped working. As it was MIDI routed to my Virus, I assumed something went wrong on the Virus - rebooted it, as it takes a few seconds. No change. Even though the synth played its voices OK I rebooted this too - maybe something went wrong with the MIDI protocol. No change.

Then I rebooted the MPC X - working like a charm. This key binding issue happened a few times since I have the MPC X.

Another funny thing happened the other day: Starting a MIDI recording from a day before - the M3 and the Virus were out of tune - I did of course check first of all the recorded sysex's on the MPC X - nope. I deleted all sysex protocolls exept of the Note ON/OFFs to identify the issue... no change. I rebooted the MPC X - and the issue was gone.

I must say - this machine is not running as it should - the software needs a lot of work in the details. Functionality is fine, but a little unstable, as it takes me ages to identify an issue. One could of course say - just boot it, if this is the solution - nope this is NOT a solution but a workaround for immature software.

Please make this machine running, or I have to move to a more reliable solution. DAWs are no option, as I tried it, but "fiddling" around with drivers just because a OS has some updates is even worse than the MPC X

DeaDeus wrote:Hi all - and especially AKAI Pro teams.

There was an incident which occurred a few times before yesterday evening. During recording some MIDI sequences, all of a sudden a "D" key on my synth stopped working. As it was MIDI routed to my Virus, I assumed something went wrong on the Virus - rebooted it, as it takes a few seconds. No change. Even though the synth played its voices OK I rebooted this too - maybe something went wrong with the MIDI protocol. No change.

Then I rebooted the MPC X - working like a charm. This key binding issue happened a few times since I have the MPC X.

Another funny thing happened the other day: Starting a MIDI recording from a day before - the M3 and the Virus were out of tune - I did of course check first of all the recorded sysex's on the MPC X - nope. I deleted all sysex protocolls exept of the Note ON/OFFs to identify the issue... no change. I rebooted the MPC X - and the issue was gone.

I must say - this machine is not running as it should - the software needs a lot of work in the details. Functionality is fine, but a little unstable, as it takes me ages to identify an issue. One could of course say - just boot it, if this is the solution - nope this is NOT a solution but a workaround for immature software.

Please make this machine running, or I have to move to a more reliable solution. DAWs are no option, as I tried it, but "fiddling" around with drivers just because a OS has some updates is even worse than the MPC X

This site is not an official Akai Pro forum. You should post your issue here: http://community.akaipro.com/akai_professional

I know, but sometimes key-users, and I expect one or the other is in this forum, has a some good - maybe even a better - influence.

And - of course would I like to hear if someone else is having this issue, or had it in the past., Maybe I am just doing something wrong.

And - I feel this forum has more experienced users. People "living" with their machines.....

DeaDeus wrote:I know, but sometimes key-users, and I expect one or the other is in this forum, has a some good - maybe even a better - influence.

And - of course would I like to hear if someone else is having this issue, or had it in the past., Maybe I am just doing something wrong.

And - I feel this forum has more experienced users. People "living" with their machines.....

I understand, the reason I say post that question there, is you'll get an official reply from them. I'm sure they read or view the comments here, but I never see any official responses. Having to reset the device to fix it, is a pain and it should not function like that. Are you updated to the latest OS patch?

CharlesRandolph wrote:I understand, the reason I say post that question there, is you'll get an official reply from them. I'm sure they read or view the comments here, but I never see any official responses. Having to reset the device to fix it, is a pain and it should not function like that. Are you updated to the latest OS patch?

My latest update was 2.2.2 and I was a lucky one without a booting issue. Now that 2.2.2.1 is out, and I have read a disturbing thing on the official forum (http://community.akaipro.com/akai_profe ... -5-minutes) about hardware to be sent in after USB issues after patch level 2.2.2.1, I will not update to that... there is anyway no patch level report out on 2.2.2.1 as yet.

General rule is post everywhere and get as many replies possible : ]

DeaDeus wrote:

CharlesRandolph wrote:I understand, the reason I say post that question there, is you'll get an official reply from them. I'm sure they read or view the comments here, but I never see any official responses. Having to reset the device to fix it, is a pain and it should not function like that. Are you updated to the latest OS patch?

My latest update was 2.2.2 and I was a lucky one without a booting issue. Now that 2.2.2.1 is out, and I have read a disturbing thing on the official forum (http://community.akaipro.com/akai_profe ... -5-minutes) about hardware to be sent in after USB issues after patch level 2.2.2.1, I will not update to that... there is anyway no patch level report out on 2.2.2.1 as yet.

I think that's your problem 2.2.2 is very very buggy so buggy that they removed it from the site 2.2.2.1 is the stable fixed version, its the version I've been running and my boot up time has improved with and without usb drives plugged in. Other stability I can't comment on as my Live has always been pretty stable.

Thanks Moho.
I have updated to 2.2.2.1 now - with a little bad feeling, as USB drive issues are reported on the official forum - leading to sending hardware to AKAI for repair...
But as I have currently no external drive attached, I might be safe.

As I could not reproduce the error, I need to see if it happens again.