2.11.5 Bug: MPC no longer supports MP3, SND or REX

MPC 2.11.5 Bug: As of the latest 2.11.5 update, the MPC browser no longer supports mp3, SND, REX and OGG files. These files cannot be load from the browser at all, nor you can't preview them. And if your expansions use any of these files for your 'browser previews' then those previews wont currently work.

This bug is affecting standalone and mpc software (note: rex was only ever supported in the software)

EDIT 1: I have updated all my expansions and the MPC Bible to ensure they are not affected by this bug, you can download the updated versions from your File Bank

Lampdog wrote:I used mp3 import/export alot.

mp3 export seems to be working. But it won't load the mp3 I just exported!

It probably doesn't seem like much of a big deal to many, but as 90% of my expansions use mp3 browser previews, I'll have to update them all asap or face a mountain of support emails. Or hope Akai put out a hotfix immediately this weekend.

BTW, I was using an mp3 for some of the examples at the end of the course in the MPC Bible (tutorial files folder '026 027'). I've just updated these to use WAVs so re-download the bible if you need to.

Really? Is there any real reason for that?

Korzo wrote:Really? Is there any real reason for that?

Yeah, the reason is they don't have automated tests in their software development workflow, or they don't have them properly implemented. As a result, they launch updates with regressions, the classic "I fix one thing, I break another "...



I hope they release a fix for this fix that doesn't break anything else

All of my samples are .mp3's I just tried loading smh really this is bad like epic failure the QA tester really needs to stop working from home ..guess I'm going back to 2. What ever

Where can I find 2.11.4?

Simple Fix....Downgrade back to 2.11.4 until they get their Sh*t together

40Beatz wrote:Simple Fix....Downgrade back to 2.11.4 until they get their Sh*t together

Updated first post with the direct link to the 2.11.4 firmware usb updater:

https://cdn.inmusicbrands.com/akai/M211 ... Update.img

bitermc wrote:

Korzo wrote:Really? Is there any real reason for that?

Yeah, the reason is they don't have automated tests in their software development workflow, or they don't have them properly implemented. As a result, they launch updates with regressions, the classic "I fix one thing, I break another "...



I hope they release a fix for this fix that doesn't break anything else

This is what I find hard to understand.

According to this talk from the one of, if not the most senior software engineer at InMusic/Akai, they seem to pride themselves on their automated test and build pipeline:


Maybe the tests are bad?

But even they are, if the build process is so slick how come we have to so long for fixes? Meanwhile we periodically get features no-one asked for.

Reputationally, I think the damage to the Akai Professional brand might be irreversible. Most people I speak to now are so wary of buying any new MPC product because of the what they've heard about the reliability of the platform. This is such a shame. IMHO the hardware platform is great, but the lack of quality and feature planning in the software just smacks of negligence and a contempt of their customer base on the part of InMusic.

The pandemic was very profitable for InMusic (and the musical instrument market in general) yet they seem unable to invest in better software engineering practices.

It does seem like since he did that talk congratulating their own bug testing processes, the amount of bugs has amplified quite significantly.