[OFFICIAL] - MPC X & MPC Live Photos, Specs & Pricing

jpeg wrote:

Fanu wrote:Yup, no latency is one of the big selling points and joys of a standalone. You play it, and it plays back exactly when you hit the pad.
We all like to mess with all kinds of plugins in DAWs, but that hinders the playability of pads with them.

I think the latency is mostly academic; cos for all intents and purposes you wont notice the latency when using controllers.

Even though the latency may be measurable using some sensitive equipment; most users cannot perceive any latency unless ur buffer settings and sound card settings are messed.

I defo have note noticed and difference in latency or note placement when comparing the mpc studio to the mpc1000.

also the gear4 music video has now been made private did anyone watch?

They showed a few more screens in the live, but it was mainly focused on clip launching.

Living Bate wrote:I've got a 2kXL and a Renaissance, and I can quite honestly say I notice no difference in response times from hitting the pad to hearing the sound....

I can only assume people have their settings wrong, or are using busted azz lagging computers or something....

it really doesn't need to be like that....

...until Desktop OS 10.2.xxx or whatever happens, and now something's wrong, and Akai drags their heels for 6 mo. to fix it.

At least, once the OS on a standalone is optimized, it'll STAY optimized. One set of hardware specs to optimize code for.

I've worked w/ MPC 1.9x for a while, and it's fine by me. But I usually wait 4-6 mo. before updating the Mac OS, for fear that I'll be without MPC for a while, if there's a conflict.

It'll be nice to not worry about the health of two separate pieces of code, and if some update will jack a driver, deep in the OS, that cripples me w/ weird communication errors.

How to solve this problem in the mpc software.... Set you audio device properly to minimise latency or turn on time correct on the MPC and choose an appropriate resolution before recording MIDI.

That's not going to solve anything for me, I work with Reason 9 and Studio One, and I don't have the MPC software. Nor do I wish to use it. I am well aware of trying to fix the resolution yada yada, the DAW midi grids just don't do it like the MPC stand alone, sorry they just don't. I play keys and when I play fast it's difficult to try and put all the midi notes on the one.

Reason and Studio One did improve a bit, where if its off you can highlight every note, then hit quantize and the notes will fall in place but some notes slide under another midi note and then I have to move it and replay then move it and replay...... Man I am tired of that.

I remember having the 2000xl and making the drums and then playing keys and record into the MPC put what I played on a pad and it would fall right in, cause I had the drums tight. It was an unorthodox way to produce but I got the track done, and it helped develop my playing.

So what you offered has been done already thanks, the only thing that will solve this is the X.

Danoc wrote:
A person that gets it.

I had arguments over this some said it was latency or jitters or quantizing. The fact was my notes be off and getting a standalone is going to eliminate that.
.

i understood what your problem was, i just wanted you too. one core of a macbook will smoke all MPC units.
so saying your computer is not accurately placing your hits is well, mistaken.

eclipxe wrote:I understand what you're saying. It isn't the sequencer or it's timing that you're taking about. It's latency. When you play standalone there is almost zero latency. The pad is hit and boom the sample is triggered instantly. The timing is all right there.
When you go through a DAW, you have latency from the controller to the computer and then back out from the DAW to the sound interface. That latency is what doesn't make your timing feel as tight and why notes end up out of place when recording. Your timing is tight but the latency makes it feel like the sequencer isn't right.

greavous420 wrote:How to solve this problem in the mpc software.... Set you audio device properly to minimise latency or turn on time correct on the MPC and choose an appropriate resolution before recording MIDI.

and

Living Bate wrote:I've got a 2kXL and a Renaissance, and I can quite honestly say I notice no difference in response times from hitting the pad to hearing the sound....
I can only assume people have their settings wrong, or are using busted azz lagging computers or something....
it really doesn't need to be like that....

so my point was your computer is not up to par, or your setting are not tight. i have zero latency when banging pads. i also have owned 1000, 3000, 2000, and still have my 2kxl. i truly don't have any difference in latency. and i never use quantize. what is your buffer settings?

jpeg wrote:also the gear4 music video has now been made private did anyone watch?

yes it was mostly about playing with the stems again. nothing you haven't already herd or seen.

pspsounds wrote:Man I didn't know what latency was until I got a controller. I'm so ready for a standalone where I can zone in on the music and not buffer sizes and audio drivers.

Exactly. I am sick of it, I am strictly in the box and I love it, but I need a standalone, I have projects and I don't have time fixing midi notes. I hear dudes say they put their buffer down to 64 then go back up to 1024 when they mix, I am like wtf do you go through all that for? It's ridiculous and the time is now to get the X and be done with it, and I can get back to having fun and work.

Danoc wrote:
So what you offered has been done already thanks, the only thing that will solve this is the X.

Dude,, its the SAME software! how in the world would you think that the mpc in standalone running the same software as the computer, is going to handle simple midi note placement Better? its software on a smaller chip system then your comp. it will not be processing faster then your computer can. So what i hear from you is your excited ass heck to cop the new X, and its primarily for a tighter grid?
how do you even get the notion that the Grid is any different then any other mpc, maschine, FL studio?
What are you gonna do when you bring the big bad boy home and there is no noticeable difference for you?
what happens when you get the same result?

Fanu wrote:Yup, no latency is one of the big selling points and joys of a standalone. You play it, and it plays back exactly when you hit the pad.
We all like to mess with all kinds of plugins in DAWs, but that hinders the playability of pads with them.

Profound, this is what I was trying to explain to those nuts in Gear Slutz they are to blind and attention whores to see what I was saying. People talking about hitting the pad and it being on point when I hit, I am not talking about pad sensitivity, that's fine I am talking about the midi notes not falling on the one was they suppose to and having to fix them. If I play a complex piano loop say of 4 bars and the scale is huge and I have to fix the notes that is very tedious. Hell 4 bars is a lot. so what I developed as a work around to do it in chops. I am sick of that. I shouldn't have to do that, hell my old way with the 2000xl worked better than this. But I am glad Akai did this.
As you know my main two things I am going to love and wanted is:
1. MPC's tight no latency sequencer
2. Being able to export my drums patterns, pad melodies etc out of the MPCX and save it to my desk top on my PC and drag and drop that into my favorite DAW which is Studio One 3 and Reason 9. I love to mix in Reason 9 with the SSL board, I freakin love it. I love using Studio One with my VSTi's and Vsts. Their native stuff is top notch no need to buy other stuff.

So right there Fanu that's big on my part, but I didn't expect Akai with all the extras which will be a plus. I think they did an awesome job and I am going to pay that $2,299 or if I get a discount so be it. Stand alone is a must in my setup. I waited since 2012 and now I can have fun again.

pk1 wrote:
Dude,, its the SAME software! how in the world would you think that the mpc in standalone running the same software as the computer, is going to handle simple midi note placement Better? its software on a smaller chip system then your comp. it will not be processing faster then your computer can. So what i hear from you is your excited ass heck to cop the new X, and its primarily for a tighter grid?
how do you even get the notion that the Grid is any different then any other mpc, maschine, FL studio?
What are you gonna do when you bring the big bad boy home and there is no noticeable difference for you?
what happens when you get the same result?

How on earth can it be the same software if one is programmed for x32 and x86 processors and the other for arm processors.

They could be the same in functionality for the end user (you and me) but under te hood there are different things going on.

Try to do load up a few heavy vst/vsti and you'll notice the latency kicking in. If you start out your project with your drums you can reduce the latency/buffer size. But when you try to ad them after all those countless vst/vsti your screwed.

Living Bate wrote:I've got a 2kXL and a Renaissance, and I can quite honestly say I notice no difference in response times from hitting the pad to hearing the sound....

I can only assume people have their settings wrong, or are using busted azz lagging computers or something....

it really doesn't need to be like that....

Nope not me, my computer is top notch and I got an i7, that I didn't even open yet, it's not the computer on this end its just the DAWs sequencers are not up to par. I am very knowledgeable on setting buffers etc. why should I go back and forth like some do? The X and Live when solve this.

Im not talking about response time in hitting the pads, I am talking about midi notes not hitting on the one and you have to fix them. Proof in the pudding in Reason 9 and Studio one they know that's why they put a feature there where you can highlight all midi notes hit quantize and they fall into place on the grid but a lot of the times that don't do the trick. If I play a complex piano run and I do that little trick some of my midi notes slide under other midi notes throwing off the whole piano scale. So it's not about the computer as you may think its the DAWs!

Here are my specs that I use right now on my computer and you tell me what's wrong!

Windows 7, 3.0 Ghz speed, 64 bit, 16 gigs ram, 2 TB HDD.

zangetsu01 wrote:How on earth can it be the same software if one is programmed for x32 and x86 processors and the other for arm processors.

From what I gather from Pete's tweets, the MPC Software is developed in Juce, which (in my limited understanding) means you can write a single source code and then compile it to run identically in Windows, Mac or Linux.

pk1 wrote:

Danoc wrote:
So what you offered has been done already thanks, the only thing that will solve this is the X.

Dude,, its the SAME software! how in the world would you think that the mpc in standalone running the same software as the computer, is going to handle simple midi note placement Better? its software on a smaller chip system then your comp. it will not be processing faster then your computer can. So what i hear from you is your excited ass heck to cop the new X, and its primarily for a tighter grid?
how do you even get the notion that the Grid is any different then any other mpc, maschine, FL studio?
What are you gonna do when you bring the big bad boy home and there is no noticeable difference for you?
what happens when you get the same result?

Dude as explained to you before it's not the same. In stand alone mode, the MPC X or the previous MPCS worked on their own and it's not the same as the software, who told you that? The MPC standalone has no latency, the software does, so how is that the same? You have to set buffers in the software, the MPC you don't how is that the same?
I am talking about the sequencer not just the grid dude. The standalone sequencer of the MPCs is better than the DAWs sequencer hands down.

Now I need you to show me an article saying that the MPCX/Live in it is the same as the software.

Remember when in controller mode the X or Live will only be a CONTROLLER! Totally different from standalone.

What he says at Machine Masters, nothing can compare to the MPC standalone sequencer.

https://www.youtube.com/watch?v=_eKBmnf3JIc&t=29s

Danoc wrote:[
Now I need you to show me an article saying that the MPCX/Live in it is the same as the software.

The MPC Software is developed from a single source code and compiled in Windows & Mac, but the framework (Juce) also allows for compilation into Linux, which we already know is the operating system that the Live/X chipset is capable of supporting.

My assumption has always been that Akai will have just added code to the core MPC Software to 'adapt' the UI when running in Linux, but the source code that handles all the functionality will probably be identical.

Think of it like this forum; when you view it in a mobile device the layout is completely different - this is done using a style sheet that detects your screen size and invokes different display rules. But there isn't two versions of the forum - there's only one set of scripts that run everything and interact with the database, it's just the UI that adapts to the different environment, so if there's an error in one of the scripts, both the desktop and mobile versions are effected equally, as they both run the same codebase.

Anyway, that's what I have assumed, and it would seem to make sense rather than have Akai trying to juggle development of two completely separate source codes.

I think the standalone will perform so well because the hardware environment is perfectly optimised for it. Plus there's no screen mirroring like there is on a Touch, so that's going to improve UI responsiveness.

But I can't prove any of this

Danoc wrote:
Dude as explained to you before it's not the same. In stand alone mode, the MPC X or the previous MPCS worked on their own and it's not the same as the software, who told you that? The MPC standalone has no latency, the software does, so how is that the same? You have to set buffers in the software, the MPC you don't how is that the same?
I am talking about the sequencer not just the grid dude. The standalone sequencer of the MPCs is better than the DAWs sequencer hands down.

Now I need you to show me an article saying that the MPCX/Live in it is the same as the software.

Remember when in controller mode the X or Live will only be a CONTROLLER! Totally different from standalone.

ok let me digress a tad. my text's kinda sounds like I'm calling you an idiot that doesn't know what he is talking about. and i don't mean that at all.

so like tutor just explained. they will be the same software running the same regardless if in controller mode or not. This is the common sense i was trying to express. I figured you knew about latency. who the hell doesn't after your first twenty minutes doing computer production as a noob? So I'm figuring you think that the much higher resolution of the MPC software is not placing your midi notes where you want them. Because the lower resolution MPC standalone {of the past} have placed your midi notes tighter? Since the stand alone were in 48/96 PPQN. and you have your MPC software rocking a large 960 PPQN you are getting more freedom. hence harder to make it on the one. And being placed off ever so slightly. Put your Software back into the lower setting and let me know if its as bad as you have experienced in past attempts.

zangetsu01 wrote:Try to do load up a few heavy vst/vsti and you'll notice the latency kicking in. If you start out your project with your drums you can reduce the latency/buffer size. But when you try to ad them after all those countless vst/vsti your screwed.

i don't have this issue brotha. I'm on an 2012 macbook pro with 16gram. not that special. but i still don't have latency issues. I don't run allot of VSTi's but generally allot o VST FX. with only a couple VSTi's running. And when i decide to try different sounding drums or creat a slightly different drum pattern on change up seq. i don't run into any problems. usually my cpu will start spiking. so i resample a cpl tracks with efx on em. so i can delete efx and run dryer tracks.