Bug reports & end-user support for Akai's MPC Software 'controllers' including the new MPC Studio 2, the MPC Touch, MPC Renaissance & original MPC Studio and MPC StudioB lack.
User avatar
By GNRFAMZT Wed Oct 21, 2015 6:20 pm
the question is: WHY ON EARTH does andy not possess a mpc touch yet?
:shock: :shock: :shock: :shock: :shock:
i´m completely baffled that akai decided not to give him one in order to let him beta-test the unit. he´s an absolute pro. correct me if i´m wrong but i do recall he got a renaissance long way before its release date, am i right?

btw, here´s a simple reason why akai release the mpc touch now: in the u.s., it has been calculated that a quarter of all personal spending takes place during the christmas/holiday shopping season. it´s all about windfall gain.
User avatar
By MPC-Tutor Wed Oct 21, 2015 7:05 pm
GNRFAMZT wrote: correct me if i´m wrong but i do recall he got a renaissance long way before its release date, am i right?


No, I never got a pre-release Renaissance, Akai have never sent me any hardware, pre-release or not. I had beta access to the MPC Software, but had no controller until I bought my own one.
User avatar
By distortedtekno Wed Oct 21, 2015 7:11 pm
MPC-Tutor wrote:
GNRFAMZT wrote: correct me if i´m wrong but i do recall he got a renaissance long way before its release date, am i right?


I never got a pre-release Renaissance, Akai have never sent me any hardware, pre-release or not. I had beta access to the MPC Software, but had no controller until I bought my own one.

I'll vouch for Andy. I was also a beta tester for the Ren and stopped testing while it was still in alpha because it wasn't worth my time without the controller.
By allank Mon Oct 26, 2015 2:17 am
Iron Leg wrote:i think the issue is the software, the controllers are all fine, it's what they are controlling that is the problem.
the touch screen brings potential for faster work follow but it's restrictions are mostly software based.
the upside to having this released is some extra commitment to software development, but the kind that involves listening to the existing user base.
their faux unboxing video. people are tried of the b.s.


Simple solution.. They need to re-hire JJ as a software designer. He is great at listening to the user base, both with bugs and features. (albeit limited by CPU power).

The workflow and functionality available now in JJOS128xl (or JJOS3) is fantastic.. I'm not an OSXL user myself, but it also is still supported and has many that swear by it.

Combining the software design of JJ, AKAi's hardware (which all looks pretty good still) and modern CPU grunt could make the MPC truly "KING" again.
User avatar
By MPC-Tutor Mon Oct 26, 2015 8:56 am
allank wrote:Simple solution.. They need to re-hire JJ as a software designer. He is great at listening to the user base, both with bugs and features. (albeit limited by CPU power).


Lol, 'simple' is the last word you would use to describe the relationship between JJ and Akai. There is zero trust between the two parties, and TBH given the history you'd have to assume that giving JJ access to the MPC Software codebase is just about the last thing Akai would ever do.

And while JJ is great at listening to his userbase, that would be irrelevant if he were working for Akai again. He'll need to work on the features Akai tell him to work on. TBH I'm pretty sure the existing team working on the MPC Software are more than capable of handling whatever they are asked to do.
By allank Tue Oct 27, 2015 6:08 am
MPC-Tutor wrote:
Lol, 'simple' is the last word you would use to describe the relationship between JJ and Akai. There is zero trust between the two parties, and TBH given the history you'd have to assume that giving JJ access to the MPC Software codebase is just about the last thing Akai would ever do.

And while JJ is great at listening to his userbase, that would be irrelevant if he were working for Akai again. He'll need to work on the features Akai tell him to work on. TBH I'm pretty sure the existing team working on the MPC Software are more than capable of handling whatever they are asked to do.


Of course, it's not simple.. but I wasn't suggesting he do what they tell him.. I was suggesting they make him the principle designer/architect..

This isn't a matter of what a developer is capable of it's more about the approach and the end-goal. IMO, Akai has been beaten by Maschine, and even to some extent Bitwig and Ableton at their own game.

Instead of providing a competing product that is playing catch up, they need to shift gears and provide something that leads the pack again. From what I have seen of the MPC software (admittedly it is limited), they are not being creative. It appears decisions are being made to appease the board..

This is where JJ comes in, JJOS128xl/JJOS3 does things that as an old MPC2kxl user I could not imagine an MPC could do. (OS-XL does too, but I don't use that).. This is on hardware that AKAI only produced a slight improvement on the 2000xl OS, at it's first release and some of the subsequent releases were only playing catch up with JJ...

The possibilities for the Touch could be endless, but AKAI need to be creative and listen to the customer base.

My case in point, JJ-OS128sp has been announced... Many users have stayed away from the large screen as OS128XL loses some functionality they rely on from OS-XL... (while adding others that some others of us may love) .. This will probably sell more large screens and people have been asking for it.
By Chillin Fri Oct 30, 2015 4:56 pm
Mink wrote:Back on topic about the Touch itself, I think it looks quite nice, and whilst the workflow may be better I don't see any justification for the high price that would make me ditch my Studio just yet. If it could be operated completely in standalone then that would be different.

It's nice having a touchscreen, but with the MPC software you already have a screen in your monitor (albeit not touch). What I would have preferred to see is an MPC that can sync up with an iPad for editing controls, much in the same way that you can use an iPad in Logic Pro X as an auxiliary controller. If you had that, then you'd have the best of all worlds - an MPC that continues using the desktop software, but an option to use an iPad as the controller screen, which could of course, be tilted to your hearts desire.

Pie in the sky I know :)



Basically all major brands have this option, or something alike. This is why it is so shocking that the "iMPC pro" doesn't match up with the MPC computer software.


This one goes back 4 years. If I not mistaking, they were the first to add this type of support.

Last edited by Chillin on Fri Oct 30, 2015 5:14 pm, edited 3 times in total.
By Chillin Fri Oct 30, 2015 4:57 pm
TT_Lab wrote:I'll pay up to 50$ for such an app


This is fighting.




And if it can be do for Ableton Live, it can be done for the MPC software, it's a matter of willingness. Rather as an option, without hacking.


By TT_Lab Fri Oct 30, 2015 9:28 pm
That was not the kind of app I'd pay for. I already own touchosc.
And you cannot edit ur samples on it visually.
Maybe airdisplay would be more close, but either way the is not a optimized solution for mpc software.
By Chillin Sun Nov 22, 2015 2:19 am
TT_Lab wrote:That was not the kind of app I'd pay for. I already own touchosc.
And you cannot edit ur samples on it visually.
Maybe airdisplay would be more close, but either way the is not a optimized solution for mpc software.



Not yet, but with the Link implementation you will be able to do so.

I am anxious for Lemur – Liine to implement Link. All that is needed then is the script, which we can code ourselves.