MPC 3 -- Let's GO!!

there is no rush for 3.0; dudes need to stop crying about the delay, 2 months ago most of u did not think there would ever be 3.0 ( u said it was vapourware, an urban legend or not needed) but now u acting all entitled, calm urselves.

Monotremata wrote:All they did was say 'in a few weeks'. That could be 2 that could be 20. The users are the ones overhyping themselves thinking something is just around the corner, when nobody has said anything of the sort, except the one moron who thinks he's the Akai Nostradamus nowadays.

When you plan to release a soft in 20 weeks and you don't have customers for idiots, you announce ‘a few months’, because a few weeks is 8 max, because after that you should count months.

it's kind of wild how they were silent about the beta for over a month, before finally saying "we actually have no idea when we're rolling this out" Like, what were they even working on during that whole time? and how are they still clueless as to what the rollout timeline is???

also, it's super bizarre how so many dudes act like AKAI didn't hype up 3.0 and ask people to "beta" test it. people aren't being impatient, they're literally just asking about the shit AKAI had a whole promo run for. like, is it even a beta if you can't try it until it's perfect? it's 2024, people know wtf a beta is and that their might be software bugs. either have a real beta and solicit feedback, or stfu and announce it when it's actually done, not this weird half assed roll out

Remember Akai is a business. They could've announced it early to keep customers & potential customers focused on their product to prevent them from buying some else. Letting their base know a major update will be released "soon" forces people to factor that in.

This may suck for the users potential customers, especially the impatient type, but it works for Akai. Just like the delay with Stem for standalone.

ha! i called it a few days ago it would come out on today thursday!!!! just in time for my x se i just picked up !!

ontherun wrote:https://akaipro.onfastspring.com/mpc-3-public-beta

Niceeee

marctronixx wrote:ha! i called it a few days ago it would come out on today thursday!!!! just in time for my x se i just picked up !!

u have to wonder about the public anouncment being all marketing cos they made the public notice last week and then droped the beta today, this is all trickery from akai

Yoooo, now we can start complaining about missing features without breaking the NDA.
WHERE ARE CLIP PROGRAMS AKAI That was a big part of the "live" part of mpc live. HUH ???????????

ontherun wrote:https://akaipro.onfastspring.com/mpc-3-public-beta

Awesome. For people who already have the beta: when they say to 'back up your projects', is there a potential problem storing 3.0 data/ projects alongside 2.0 projects? I'm going to back up my projects anyway, just curious as to what the worst that could happen is.

Conversion of your projects into MPC3 format means the project will no longer work in MPC2. Hence keep a separate backup of the MPC2 version safe somewhere so you can go back to it within MPC2 when you need to.

IvoryBlack589 wrote:

ontherun wrote:https://akaipro.onfastspring.com/mpc-3-public-beta

Awesome. For people who already have the beta: when they say to 'back up your projects', is there a potential problem storing 3.0 data/ projects alongside 2.0 projects? I'm going to back up my projects anyway, just curious as to what the worst that could happen is.

MPC-Tutor wrote:Conversion of your projects into MPC3 format means the project will no longer work in MPC2. Hence keep a separate backup of the MPC2 version safe somewhere so you can go back to it within MPC2 when you need to.

Gotcha, thanks!

Edit: Also, is the beta timed or can one just continue using it until 3.0 proper comes out?

this is 3.4 right now. there is no sign this will "time out" . there is an option to downgrade the beta back to public stable.

It's my understanding that this public beta has no expiry date and the final 'stable' release will not need an activation code either, only beta versions need one.

And yes, 3.0 is not a thing, the numbering carries on from the current Force 3.3. I'm assuming that this update is also going to be ported over to the Force and they will now share version numbering (I might be wrong, but seems too much of a coincidence).

All bug reporting via this form apparently:
https://forms.office.com/r/zfb7GymJGp

Without access to a bug tracking database surely just going to be 1000s of identical bug reports. Not good for Akai, not good for wasting people's time reporting known bugs.