We are getting what we asked for, but is it what we need?

The floor’s clean but my eyes might need a rinse

Ultros wrote:Ok one more overly personal off topic for the **** of it. you guys never really seen me before and atm im in a good mood so lol here is me and my dancing partner "moppy". https://streamable.com/u7pvqg

Ultros wrote:There is all is dusty, everything important i grabbed it all.. luckily i keep most my shit in its original boxes or totes. Thats all my music gear, retro consoles, computers and collectables.

I was on the MPC learning curve with v2 and then with v3 since it came out, but have to confess I've just thrown the towel in and downgraded to 2.15... and it was like an old friend coming home

It feels odd saying that as I missed out on the MPC evolution and am not a serious user, but I'm tending to agree with some of the comments here re. coherency with the hardware layout. I'd even forgotten about the trivial things like the method of closing screens by tapping the top-left region, the single page main menu, and the absence of page-swiping vs left/right buttons, etc.

Hats off to Akai for providing a way forwards for those who want it (for free!), but the good news is it's starting to make more sense back on v2, to me and my OCD at least I did worry that I'd be losing out if/when v2 is dropped, but then realised that I'd accepted v2 when I bought the machine, so upgrading is completely optional.

Phil Tipping wrote:I was on the MPC learning curve with v2 and then with v3 since it came out, but have to confess I've just thrown the towel in and downgraded to 2.15... and it was like an old friend coming home

It feels odd saying that as I missed out on the MPC evolution and am not a serious user, but I'm tending to agree with some of the comments here re. coherency with the hardware layout. I'd even forgotten about the trivial things like the method of closing screens by tapping the top-left region, the single page main menu, and the absence of page-swiping vs left/right buttons, etc.

Hats off to Akai for providing a way forwards for those who want it (for free!), but the good news is it's starting to make more sense back on v2, to me and my OCD at least I did worry that I'd be losing out if/when v2 is dropped, but then realised that I'd accepted v2 when I bought the machine, so upgrading is completely optional.

We're institutionalised by the system like brooks hadlen. Put us out in the world and we don't know how to function. "Maybe I could rob the food way so they will send me back home, I could shoot the manager as a kind of added-bonus."

Phil Tipping wrote:We're institutionalised by the system like brooks hadlen. Put us out in the world and we don't know how to function. "Maybe I could rob the food way so they will send me back home, I could shoot the manager as a kind of added-bonus."

...or you could end up with a rope around your neck with a "Phil Was Here" banner as the backdrop

@BackOnDaMPC you've quoted me instead of @Ultros
But now I'm on, just a follow-up to my original comment of sticking with v2.
I've since raised 2 faults re. minor issues with v2.15.1 and have just had these responses:
1. "...since this issue pertains to the old firmware, I doubt there will be another update released for it. That being said, I highly recommend that you consider updating to our latest firmware, version 3.4.3"
2. "...I sadly cannot provide an accurate ETA on when this will be resolved"
So looks like v2 support has had it... you either accept 2.15.1 as-is with little/no chance of fixes, or embrace v3.

Phil Tipping wrote:@BackOnDaMPC you've quoted me instead of @Ultros
But now I'm on, just a follow-up to my original comment of sticking with v2.
I've since raised 2 faults re. minor issues with v2.15.1 and have just had these responses:
1. "...since this issue pertains to the old firmware, I doubt there will be another update released for it. That being said, I highly recommend that you consider updating to our latest firmware, version 3.4.3"
2. "...I sadly cannot provide an accurate ETA on when this will be resolved"
So looks like v2 support has had it... you either accept 2.15.1 as-is with little/no chance of fixes, or embrace v3.

this was already assumed to be the case