2.15 and MMC-receive

Hello,

at least for me, the bug that MMC start/stop commands are no more received/interpreted by MPC which was intruduced in 2.14 does still exist in 2.15!!!

Refer also to: viewtopic.php?f=48&t=217562&p=1881583#p1881583

Any other experiences?

I did some quick tests myself with 2.15 out of curiosity, and couldn't get MMC working either. I'd love to speculate why it hasn't been fixed, but at this point I just have laugh it off!

submo wrote:I did some quick tests myself with 2.15 out of curiosity, and couldn't get MMC working either. I'd love to speculate why it hasn't been fixed, but at this point I just have laugh it off!

Reply from support just arrived:

Hi Christian,

Thank you for reaching out regarding the ongoing issue with the MMC-receive function that was introduced in firmware version 2.14 and remains unresolved in the latest 2.15 update. I understand how critical this functionality is for your live performances and the inconvenience this has caused.

The development team is aware of the issue with the MMC-receive function. While the recent 2.15 update addressed other high-priority fixes and improvements, I regret to inform you that the fix for the MMC-receive issue was not included in this update. The development team is actively working on resolving the MMC-receive function issue. Although it was not prioritized for the 2.15 update, it remains on their agenda. Any fixes and updates, including those addressing the MMC-receive function, will be announced publicly through our official channels.

I understand how important it is to have a reliable remote start/stop function, especially in a live environment. We appreciate your patience and feedback, which help us improve our products.

Best Regards,
Velislav
Customer Experience Advisor
inMusic

Thanks for the update! Like I said I'm at the point where I have to laugh all this off. It's gone beyond a joke, and come full circle, and back round to being a joke again.


..... And why they didn't put this as a known issue on the release notes! ....... Grrrrrr it's gone beyond a joke again!!

submo wrote:..... And why they didn't put this as a known issue on the release notes! ....... Grrrrrr it's gone beyond a joke again!!

They would have to put all of the know issues in them as well - who's gonna pay for another technical writer vacancy to pull this off ?

TL;DR "Thank you and shit"

Akai doesn't need defenders, they need competent coders.

Or sane users, if you dont settings > midi > mpc > sync enabled, it wont do shit lol. i bet thats where everyone is going wrong cus the chits working fine for me, never stopped working.

Ultros wrote:Or sane users, if you dont settings > midi > mpc > sync enabled, it wont do shit lol. i bet thats where everyone is going wrong cus the chits working fine for me, never stopped working.

The MMC (receive) on the MPC hasn't worked since version 2.14.

Lampdog wrote:Release notes are for what’s included in the release, not what coulda, maybe you thought shoulda been in there. Illogical ass thoughts.

mmm nope, they started including the known issues in the release notes some time ago, so its logical that if 2.14 introduced a new bug that HAS been reported and verified, they have to include it in the release notes.
anyway, do you agree that continually introducing new features that introduce new bugs and not squeezing them all out doesnt sound competent and smells a bit like "ok we put out new features to lure new customers, bug squeezing is not a priority"...? bugs should always be prioritized unless they are very much irrelevant, and this is not the case.

The MMC MMC-receive is not working in the last 2 updates. Its very crucial for the live performances !!

This issue in combination with the is the bane of my life right now in combination with the multi-timbral MIDI bug. My whole musical reality is broken.

Most recent working version is 2.8

I've confirmed that the MMC bug has been fixed in MPC 3.4.