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 Mon Oct 19, 2015 9:57 pm
the system requirements for the mpc software have drastically changed!

System requirements MPC Touch:
4 GB Ram (8 GB recommended)
Dual-Core processor, 2.5 GHz or better
Macintosh: Mac OS X 10.9, 10.10
Windows: Windows 8, Windows 10
http://www.akaipro.com/product/mpc-touch#system_requirements

System requirements MPC Renaissance/Studio:
2 GB RAM (4 GB recommended)
Macintosh: 2 GB RAM (4 GB recommended)
Mac OS X 10.7 - 10.10
Windows: 2 GHz Pentium® 4 or Celeron® compatible CPU or faster (multicore CPU recommended)
Windows 7 and Windows 8
http://www.akaipro.com/product/mpcrenaissance#system_requirements

given the above facts, one can assume that v1.9 won´t run properly on computers that were able to cope with previous software versions in the past. btw, right before the ren was released dan was busy answering questions here. where is he NOW? akai didn´t learn a thing regarding consumer interaction. pitiful! even professional nukai fanboy jah did not show up here so far to promote the touch. wtf is going on??
User avatar
By jonestown massacre Mon Oct 19, 2015 10:48 pm
You would have to expect that the processor and RAM loading on a touch screen interface are going to require a larger bandwidth than a button type, output only display option.

Just sayin.



The whole customer service thing is a whole other topic of conversation, lol.
User avatar
By MPC-Tutor Tue Oct 20, 2015 12:59 pm
Eyalc wrote:I'm amazed that anyone would think that they would continue support for the Studio and Ren for much longer after the Touch release. That is their track record - 3 - 4 year shelf life. This is no different.


There's no evidence to suggest they are dropping support for previous generation controllers yet. Ultimately these things just control the MPC Software so should still control any future versions of the MPC Software, even if they won't be able to access some newer features (as they won't have the necessary hardware features, e.g. touch screen, available/spare buttons etc). If the MPC Touch is allegedly using a different fork of the main MPC Software, this doesn't mean they are abandoning the main version of the MPC Software.

This is supposed to be one of the clear advantages of going the software route, the hardware can come and go but the software remains universal, so any generation of controller can still control it, just like the Maschine software can be controlled by any of the five different hardware controllers they've created over the years.

Any deviation from that would be pretty dumb IMO.
By Eyalc Tue Oct 20, 2015 1:41 pm
MPC-Tutor wrote:
Eyalc wrote:I'm amazed that anyone would think that they would continue support for the Studio and Ren for much longer after the Touch release. That is their track record - 3 - 4 year shelf life. This is no different.


There's no evidence to suggest they are dropping support for previous generation controllers yet. Ultimately these things just control the MPC Software so should still control any future versions of the MPC Software, even if they won't be able to access some newer features (as they won't have the necessary hardware features, e.g. touch screen, available/spare buttons etc). If the MPC Touch is allegedly using a different fork of the main MPC Software, this doesn't mean they are abandoning the main version of the MPC Software.

This is supposed to be one of the clear advantages of going the software route, the hardware can come and go but the software remains universal, so any generation of controller can still control it, just like the Maschine software can be controlled by any of the five different hardware controllers they've created over the years.

Any deviation from that would be pretty dumb IMO.


Agree that it doesn't mean abandonment is definite. I just think it will be. I can't imagine them maintaining multiple software forks. Doesn't seem like that kind of software house. Eventually the new capabilities will dominate developer time and resources and focus will shift to the "new", just like they did with every other MPC in the last 10 years.
User avatar
By GNRFAMZT Tue Oct 20, 2015 2:06 pm
taken from https://en.m.wikipedia.org/wiki/Planned_obsolescence
Planned obsolescence tends to work best when a producer has at least an oligopoly.

inmusic has one. m-audio, alesis and akai are flooding the market with usb/midi masterkeyboards and controller hardware like never before. it seems as if jack o´donnell doesn´t give a damn about cannibalization. i find that strange. in marketing strategy, cannibalization refers to a reduction in sales volume, sales revenue, or market share of one product as a result of the introduction of a new product by the same producer. one example: triggerfinger and triggerfinger pro from m-audio vs. mpc´s of akai.
User avatar
By MPC-Tutor Tue Oct 20, 2015 2:08 pm
pspsounds wrote:If that becomes the case a lot of users will have to freeze their laptops. But that will be a problem for some users who use their laptops for other things besides music


Yes, certainly based on previous history I can see why people are going to assume the worse! I do feel they've improved a lot these past couple of years, they've kept updating the software regularly, they've listened to many of the feature requests, they have actual MPC users on the beta testing team etc. Fingers crossed they stay on target and don't spoil it by gimping the existing controllers.