MPK25 firmware update

Edit Subject

Was the controller triggering midi data in you recording/sequencing software before trying this update? Try unplugging any unused usb devices on your system before performing the update. Also what other usb devices are installed on your operating system?

I have the same problem with MPK25. Excuse me for trying to load the most recent firmware. The reason is that I sometimes had problems using Ableton Lite. I didn't know at that time that Windows supports only one midi-program at the same time, so when Vyzex was running Ableton didn't respond. A friendly salesman (who also didn't know about the Windows limitation) told me that it might be a good idea to try the most recent firmware version. Which seemed reasonable to me.

Anyway : I've tried to load the firmware file from your site included in the mpk25_vyzex_preset_editor_software_v1.00 package. I 've tried it on 3 pc's : two Windows 7 and 1 Vista. There are no driver problems, I checked the Device manager. I've tried two different USB-cables. I tried Vyzex, Midi-ox and SenSX. The result is always the same : when I press 'send file' the MPK25 display switches from 'Send Sysex ' to 'Receiving' and keeps showing that message for eternity - or until I remove the USB cable.

As I've tried different hardware and software to load the firmware file to the device, it seems to me that the problem is caused by the device or by the firmware file. As you can't check the device, I'd like you to confirm that the file is correct and complete and has been successfully installed before from a windows PC.
If there's no problem with the file, there's a problem with the device and I'll return it to the store.

I managed to make a snapshot from the Vyzex interface while it was uploading the file. Notice the Midi Out port activity. Also : the last sign here is F7, so the two other hex signs after it are ignored. This is all there is to see during the upgrade, i think the whole file is transferred to the MPK25.

mr Sandeen, the camera is a built-in Chicony usb camera. I've disabled it because I don't use it. In the device manager, properties screen, the status says 'disabled, code 22). I add a snapshot, but you'll notice that my language is dutch.
I saw the MPK working before trying the update. I could see there was a proper midi connection with Vyzex too. It didn't work in Ableton Lite, but that's because I had Vyzex still running.
The midi in and out of the MPK are detected automatically by Vyzex and the other tools I tried. As you can see in the snapshot, the file is sent to the midi out. But the MPK doesn't seem to receive anything. If I understand correctly, the number of bytes received should be shown on the display - well, that number remains 00 - though once, to my surprise, it became 01. What strikes me is that the MPK 'feels' that you send the file, because at that moment the display message changes from 'Send Sysex' to 'Receiving'.
As I mentioned, I tried another USB cable and different USB-ports too. Besides, for a test I sent the file to a Roland USB-midi interface and I could clearly see that information was received because of the LED activity.

I suppose it's no use to keep on trying. I'll bring the MPK25 back to the store, and I'm sure they can provide a solution.

As for the troubles : don't bother. Nothing in this world is perfect, one could fill quite some symphonies with all the bad notes I ever played. So thanks for the assistance. If I ever get a working MPK25, I'll let you know.

Kind regards,
Dirk

I have the same problem and was working on it 6-8h today. Yesterday I tryed the MPK49 the first time and used Live8. Was working well but today the controller worked very strange. It changed always to the first preset. Loading preset 2-30 wasnt possible and so I tryed to solve the problem with loading a new firmware. I used 1.03 and 1.05. I used Vyzex v1.00, v1.02 and v1.05. I also used SendSX with different speeds. Its always the same: 00 Receiving. I used USB for connection and I also disabled ALL other devices. I tryed it with 3 different computers at windows xp and 7.

I read on many websites that AKAI is doing nothing over month with this problem. A lot of ppl r very angry. If u cant give a solution I will send it back in 24h.

Mr Sandeen, after all my attempts to fix the problem, I returned the device to the store. It is new, after all. The manager said he knew about the problem and could solve it with an apple computer. So far, I haven't heard of him.
Anyway, a few remarks on the 'PRO' in Akai.

1) I've been told several times now, that Akai doesn't 'currently recommend' firmware upgrades.It's a pity no one told me before I tried the upgrade. As Lowik pointed out above, the manual suggests something else. Besides, what's the use of firmware that you shouldn't load ?
I recommend : to remove the download files until Akai knows what causes the problems and fixes it. In a large part of the world, it is considered to be very normal to load the most recent firmware version, even for a new device.
If removing would be too difficult : ask the responsible for the download section to add a very clear warning,in big coloured letters : 'Don't touch, it may harm your device'.

2) Everything is case by case : I understand that.
But on the other hand : some issues seem to be 'common' for Windows users. Why not list them up in some kind of check list ? Now I was forced to gather information from several websites. A check list would have saved me a lot of time. And might have saved others quite some irritation too.
Moreover : I sent the information I provided on this forum to the Akai support service too (through the 'Ask a question' facility) and the technician immediately recommended that 'your device be serviced'. How simple can it be ?

So : if your company has some kind of a reward to improve efficiency or to reduce customer irritation : go for it. You can use my hints for free :-)

Oh yes, I've followed the link for the MPK49 too. It wouldn't come as a big surprise if the firmware file turns out to be 'hidden' in the download section, under 'drivers and software' :
http://www.akaipro.com/contentmgr/sho...

But that's just an opinion.

Mr Sandeen, now I'm getting confused too.

I brought the MPK25 back to the store, where they claimed that they would be able to load the firmware with an Apple computer. Apparently, even an Apple computer can't do a miracle : it didn't work.
So they contacted the service center (don't know which one) where the technician didn't really have to examine the device in order to diagnose : he said that if the first attempt to load the firmware file goes wrong, the hardware is affected and the main PCB (whatever that is) must be replaced. If that's true, Silvio is right : the firmware can destroy your machine. Very original, that is.

The technician also said that the reparation is not covered by the warranty.

Now let's put all things together. I buy a new device. The manual refers to software and firmware updates. I find the latest firmware file on an official AKAI site. Without any warning whatsoever. I try to load it and my device is broken.
When I try to find help the 'specialists' all claim that it's a Windows problem, and that loading a firmware file is a very 'sensitive' process. Nice to hear that AFTERWARDS. Meanwhile, I find out that I'm not the only one having this problem. Firmware files are removed from the official AKAI sites.

And if I want my MPK25 to work, I'll have to pay for it. Is that correct ?

Someone added following comment, I received it in my mailbox but for some reason it don't see it on the forum. That's a pity, because if the information is correct, it 's certainly relevant for people who have an MPK25.

" MAybe the people should stop downgrading from version 2.0 to 1.3.
MPKs with version 2 are not compatible with version 1 firmware. When your MPK was build in 2011 or later, it should have firmware 2. If you try to load firmware 1.3 to such MPKs, it won't receive data... "

Sounds a bit like a technician, or at least someone who has access to more information that the average customer ...

What I don't understand is the 'MAybe'. Don't be so cautious : people should DEFINITELY stop downgrading from version 2.0 to 1.3.

The only thing is : they should know that they are downgrading...
Some people may assume that the version presented on an official website is the most recent one. Some people may not have found the version number of the firmware originally installed...
Some people may have downloaded the file in good faith, believing that the manufacturer would certainly not provide possibly harmful software without any warning.

I know, dear technicians, some people are stupid. Can you blame them, if they don't get the information they should receive from you ?

And finally, I think it's a disgrace to even suggest that customers are responsible for this problem.

- software that is freely distributed by a manufacturer should be harmless. It's perfectly possible to test whether an upgrade is required before removing a version.
- all relevant information on versions in software and hardware, and compatibility issues, should be available and easy to find.