MPC 3 -- Let's GO!!

On the plus side, we finally have tempo automation.

Bluetooth mouse working fine for me on my MPC Live with 'dev-mode' enabled from 2.x days.

No mouse support on my MPC Key 37 (no dev mode ever set up on this)

dustyslices wrote:I think I've jumped the gun
You just gave an idea that I might have some dev-mode leftovers from the 2.x.
New installations don't delete that folder by default, I remember that same thing happened with my screenshots discovery and Tutor couldn't get them to work because of that folder was missing.
Have to SSH the image and delete it to confirm. Will report back later on - regardless of outcome, we know that the mouse is implemented so in worst case it's just a matter of badgering devs to take it out of dev-mode

dustyslices wrote:Nope, haven't messed with the firmware yet

Firmware img I originally tried (older build) had some additional data of the end that makes the mpc imgmaker app fail to decompress it, I had to use 7zip on Linux, seems to work fine, but with complaints about the extra data. Never got round to actually applying the ssh hack though, but another beta tester did and working fine apparently.

So is the soup done?

Is the pool water ready?

Is it safe to jump in?


I am OK for something to be near-production ready, with a few awkward spots, and even an occasional crash. But I am not up for tons of aggravation and setup. I'm quite OK to wait if the beta takes too much hand-holding and tolerance and understanding.

Wow!!

Unrelated video deleted: Please keep thread this on topic.

jalex wrote:While some people say "the wait" is a marketing ploy, I have a hard time understanding that. I mean, the people who are fretting are the ones that already brought at least one MPC standalone product. Little marketing value in promising access to the public beta and keeping people waiting for 1 month+ since they are already customers.

More likely is that we wait this long because the initial feedback was pretty bad as judged by Akai... and so now we wait for a "politically correct public beta release" which caters more to the OG workflow (I know it's a buzzword... ) and tries to minimize bad mouthing for the next buying customers of ... I dunno what new hardware, because the 61 and the 37 pretty much closed the workstation-daw replacement-synth discussion..
I mean from here from the touch-screen era forward, more can only be CPU/RAM upgrades, since the rest is software and upgradable...

Anyhoo, I'm tired of waiting as they say
When it's comin' I be here, but I won't be checking my mail daily that's for sure

suntan wrote:Seems like it's 4/4 only. No other time sigs.

Yes, that seems to be the case. Bummer. Don't open old files with different time signatures yet! And/or back them up before doing so.

MPC-Tutor wrote:Currently only 4/4 time sigs available, hopefully coming eventually, kind of a deal breaker for many people otherwise!

So how do we make out voice heard on this? or for that matter report bugs?
There's the suggestions feature in the v2 controller mode version I guess??

This is a bad mistake. I ditched Maschine because it can't do more than one time signature without being run as a VST and it's janky at best. Hopefully it's a matter of getting the beta right etc? but I doubt it, you don't remove existing features without thinking you can get away with it.

Dammm , did you go backward,? I think the latest version is 2.15?

joegrant413 wrote:So is the soup done?

Is the pool water ready?

Is it safe to jump in?


I am OK for something to be near-production ready, with a few awkward spots, and even an occasional crash. But I am not up for tons of aggravation and setup. I'm quite OK to wait if the beta takes too much hand-holding and tolerance and understanding.

machinesworking wrote:

MPC-Tutor wrote:Currently only 4/4 time sigs available, hopefully coming eventually, kind of a deal breaker for many people otherwise!

So how do we make out voice heard on this? or for that matter report bugs?
There's the suggestions feature in the v2 controller mode version I guess??

This is a bad mistake. I ditched Maschine because it can't do more than one time signature without being run as a VST and it's janky at best. Hopefully it's a matter of getting the beta right etc? but I doubt it, you don't remove existing features without thinking you can get away with it.

As far as I know we use this form - https://forms.office.com/r/zfb7GymJGp

MPC-Tutor wrote:
Firmware img I originally tried (older build) had some additional data of the end that makes the mpc imgmaker app fail to decompress it, I had to use 7zip on Linux, seems to work fine, but with complaints about the extra data. Never got round to actually applying the ssh hack though, but another beta tester did and working fine apparently.

I've never decompressed it with mpcimg, I always use 7zip and yes, it always complain about additional data after payload but that's just irrelevant bunch of bytes. I'll have a go with it tomorrow as I have suspicions that force clips are in this firmware anyway (I think you're on the right track with firmware numbering convention)

machinesworking wrote: So how do we make out voice heard on this? or for that matter report bugs?

MPC3 Bug Reports

MPC 3 Feedback & Suggestions

The problem is that a lot of the stuff that people will find is probably already reported , I hope they post up a live bug tracker of some description, seems like a really bad way to handle this beta, lots of duplicate bug reports etc.

I have to say this is one really depressing update "feature" for me. Track mutes are coming back, and I never really used Programs to change up things between sequences, but I'm a huge user of multiple time signatures in a song.

machinesworking wrote:I have to say this is one really depressing update "feature" for me. Track mutes are coming back, and I never really used Programs to change up things between sequences, but I'm a huge user of multiple time signatures in a song.

This is a beta and I'm sure they will address this in the final version, it's too important to drop.

dustyslices wrote:

MPC-Tutor wrote:
Firmware img I originally tried (older build) had some additional data of the end that makes the mpc imgmaker app fail to decompress it, I had to use 7zip on Linux, seems to work fine, but with complaints about the extra data. Never got round to actually applying the ssh hack though, but another beta tester did and working fine apparently.

I've never decompressed it with mpcimg, I always use 7zip and yes, it always complain about additional data after payload but that's just irrelevant bunch of bytes. I'll have a go with it tomorrow as I have suspicions that force clips are in this firmware anyway (I think you're on the right track with firmware numbering convention)

Blink and you will miss it.

https://www.youtube.com/watch?v=GUBRJdA ... nENTYqqqkR

takes a little longer to open my default template now. has no plug ins in it. just the YA Mastering set up w some fx.