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

Danoc wrote:Stand alone mode, runs 2.0, you don;t need a computer am I correct?

No, you don't.
But the same software is on both the standalone and on the computer.
So as long as it's not finished, it's unfinished for both.

I already know 2.0 is on both the machine and software for the computer. Again from what I am seeing they are good for the stand alone. why do they have to wait for the software, if the hardware is good?

Fanu wrote:

Danoc wrote:Stand alone mode, runs 2.0, you don;t need a computer am I correct?

No, you don't.
But the same software is on both the standalone and on the computer.
So as long as it's not finished, it's unfinished for both.

Danoc wrote:Stand alone mode, runs 2.0, you don;t need a computer am I correct?

The standalone doesn't need to be attached to a computer because the standalone has 2.0 installed directly inside it, it's just running the Linux port of the desktop version. As I said, some code base, different port, so until they complete a stable 'master' 2.0 code base, they cannot compile the linux port to be installed and distributed in the standalone. Desktop, windows, mac, linux, standalone, whatever - they all stem from the same code base, so there is no option of having only a standalone option.

I already know 2.0 is on both the machine and software for the computer. Again from what I am seeing they are good for the stand alone. why do they have to wait for the software, if the hardware is good

What you are seeing is a beta version of 2.0. It might even be a 'release candidate', but it could be riddled with all sorts of issues. Any you haven't seen in the demo videos could in theory still be broken. Before they can put it out in the wild, it needs to be run through heavy testing. If they find a 'showstopper' they have to fix it. That fix can in turn, break something else. The process goes on until they are happy the product is suitably stable.

@MPC-Tutor

Ok, what I am looking at is the beta testing, ok gotcha, that explains it. thanks

I'd rather them get it right.

Fanu wrote:What to do: spend a few more months coding etc, get it all right, and lose all the hype and make impatient people even crankier – or get it out ASAP and then face the wrath of those unhappy with an unfinished product?

What's to learn here…? Best not to announce stuff until you really are damn close.

its an assumption that they are still coding and bug finding; u may still find huge bugs in this app upon release

That's true just like everything else. You hit it right on the head.

jpeg wrote:

Fanu wrote:What to do: spend a few more months coding etc, get it all right, and lose all the hype and make impatient people even crankier – or get it out ASAP and then face the wrath of those unhappy with an unfinished product?

What's to learn here…? Best not to announce stuff until you really are damn close.

its an assumption that they are still coding and bug finding; u may still find huge bugs in this app upon release

jpeg wrote:its an assumption that they are still coding and bug finding; u may still find huge bugs in this app upon release

I think that's almost a complete certainty, but that's true with most applications, often a quick patch is required to plug some ridiculous bug that somehow got missed during beta testing, but that's why public betas IMO tend to be the way forward.

@FANU
They will never get it all right, like MPC-Tutor said "Until they are satisfied". Did They get Ren's software ALL Right? Nope. That's the problem they are having with customers now. I am glad I didn't get the Ren.

jpeg wrote:

Fanu wrote:What to do: spend a few more months coding etc, get it all right, and lose all the hype and make impatient people even crankier – or get it out ASAP and then face the wrath of those unhappy with an unfinished product?

What's to learn here…? Best not to announce stuff until you really are damn close.

its an assumption that they are still coding and bug finding; u may still find huge bugs in this app upon release

Danoc wrote:@FANU
They will never get it all right, like MPC-Tutor said "Until they are satisfied". Did They get Ren's software ALL Right? Nope. That's the problem they are having with customers now. I am glad I didn't get the Ren.

Yeah, they'll never get it 100% right, safe to assume. To me, getting it right would involve working PDC, which is probably very far away

Ren 1.0 was hell...public beta testing hell at its worst. Never again plz.

Ren 1.0 was hell...public beta testing hell at its worst. Never again plz.

I agree that Public Beta testing for a company like AKAI is EXTREMELY difficult!!

My experience with Beta Testing for other companies overall has been VERY positive!

Im currently involved in Public Beta testing for Serato DJ. It is an ABSOLUTE PLEASURE to work with Serato. Bugs are identified and fixed in a timely manner!!

I don't think it's so much an obsession with a Q1 release as wondering why this company can never hit its targets. 2.0 was announced in January of 2016. Last update to the software was in May of last year. Pretty terrible way to deal with people who paid 800 dollars for a Touch... definitely a middle finger to them. I see the same people who were telling people to calm down starting to lose their sh*t lol. I think it's safe to assume they're probably not hitting April either if you get through the month without some actual product demos beyond Andy's worldwide Rihanna acapella tour. I can tell you that if I had a financial stake in Akai, I'd be in the office saying, "WTF are you doing? You're giving other companies our business." Terrible business strategy to build hype around dates you can't hit and then just fall off the map when people ask you what happened. If Coz is buying tampons, he better get 'em in bulk because this is a bumpy f'n ride.

jpeg wrote:

Fanu wrote:What to do: spend a few more months coding etc, get it all right, and lose all the hype and make impatient people even crankier – or get it out ASAP and then face the wrath of those unhappy with an unfinished product?

What's to learn here…? Best not to announce stuff until you really are damn close.

its an assumption that they are still coding and bug finding; u may still find huge bugs in this app upon release

Its also a assumption that 2.0 isn't finished yet. It's us who assume that just because they didn't show it at NAMM 2017 that it isn't finished yet.

It may be something else that is causing the hold up and they just let us believe that it's the software because it's a good excuse since that we our selves have made that up based on the cryptic tweets of mr goodliffe.

chino wrote:

Ren 1.0 was hell...public beta testing hell at its worst. Never again plz.

I agree that Public Beta testing for a company like AKAI is EXTREMELY difficult!!

My experience with Beta Testing for other companies overall has been VERY positive!

Im currently involved in Public Beta testing for Serato DJ. It is an ABSOLUTE PLEASURE to work with Serato. Bugs are identified and fixed in a timely manner!!

I've been doing beta stuff for Ableton for a while.
Beta communication and beta forum work really well.
They're super responsive, also with bug reports.
Nothing but maximum respect.

willisill wrote:If Coz is buying tampons, he better get 'em in bulk because this is a bumpy f'n ride.

Or a bloody ride...

I hope the X and Live end up with their own sub-forum so we can split up those who just want a new standalone (me, Danoc, Ill Green etc), and those mainly invested in the software.

Now if ever would be the perfect timing for any company to put a killer standalone sampler out to the market.
Announce it, say it's in shops ---> death of Akai.