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.
By Sli Wed Dec 25, 2013 1:30 am
1. The ability when chopping samples to automatically fill in the current (or whatever) program with the next set of samples. ie. Bank A has all 16, the next 16 slices would fill in Bank B and so on.

2. A better zoom or similar function on sample editor. It's annoying editing a 4 minute song. When you start from the beginning and want to "extract" a portion the "end" marker is all the way at the end and you have to move it up, when you do and let the pad go after previewing it jumps to the "end" marker again. Hopefully I'm explaining this right, it's just annoying as hell.
By bobbybland Fri Dec 27, 2013 12:48 am
Clippyclipp wrote:My only request is the ability to open up vst instrument plugins from the mpc itself rather than clicking the e button and the ability to rewire reason into the mpc software


That'd be nice, I personally hate drop down windows, I think the plugins should be in the browser,and drag n drop in the software, drop down windows are so 2000..
User avatar
By SimonInAustralia Fri Dec 27, 2013 11:44 pm
BremenCole wrote:
SimonInAustralia wrote:- Multicore

Agree, but it would take a full rewrite, which is what NI did for 2.0.....

If correct, it would make me wonder why they didn't write multicore support in from the start, or at least have it ready for it without a full rewrite. :hmmm:

It is not like multicore computers and audio applications have only been invented since the MPC controllers were developed and released in late 2012, that they shouldn't have known multicore would be needed in a multitrack audio application that hosts VST/VSTi, and developed it to support it from the start.
User avatar
By Rokgod Sat Dec 28, 2013 1:55 am
Clippyclipp wrote:My only request is the ability to open up vst instrument plugins from the mpc itself rather than clicking the e button and the ability to rewire reason into the mpc software



bobbybland wrote:That'd be nice, I personally hate drop down windows, I think the plugins should be in the browser,and drag n drop in the software, drop down windows are so 2000..



This is the type of simple little things Im talking about, innovative simple improvements on features that are still very clunky


+x10000000
By Nubian Mindz Sat Dec 28, 2013 7:42 pm
A few things come to mind:

When setting up the q link to control a keygroup filter please include a real time option as opposed to just a note on option

All movements of program parameters should be automatable. For instance, if I'm recording and I do a manual sweep of the cutoff frequency that should record and then be editable.

Allow both fx and prog q links to be setup without causing crashes everytime. You can setup one or the other but if you try to use both on the one program it causes the software to instantly shut down (crash)

Make the q links present when in pad mute mode so you can control elements of the mixer and sound while muting and unmuting various pads (this is essential for live shows)

Full automation of a program, mixer and fx inserts

Bus inserts (we need this for obvious reasons)

Improved sampler: Basically an Akai s6000 or, even better, the Z8 sampler in MPC form would make me a very happy guy!!!!

Better plug in integration when in the DAW world

:mrgreen:
By Eyalc Mon Dec 30, 2013 12:17 am
More virtual outputs - like 32 minimum - 48 would be nice.

The 8 virtual output limitation, for an instrument that's supposed to be a "Music Production Center" is a :hmmm: .

And no, don't want to pan everything left and right to increase the outs - 32 stereo outs minimum. Still really want to get this thing integrated with Logic Pro X, but this limitation makes it unrealistic to do anything meaningful (for what I do).
By bobbybland Tue Dec 31, 2013 4:43 am
And I really hope 1.6 can bounce down/export pads, not just tracks, I mix on the program mix level, what's the purpose of having inserts on each pad,if I can't bounce them down, instead I'm forced to bounce the whole track. A really simple fix is just to add export on prog level, or allow for drag n drop bounce down.

I agree with the sentiments about why Multicore wasn't included from the jump, Akai had plenty of time, to watch NI and all of their growing pains, a smart emulation developer would carefully watch and learn exactly what held the other team up right? :wink:

Either way I'm very interested in what Pete said about adding support, hopefully this means more developers, like JJ lol :nod: or someone who possess that same innovative mindset.