Forum dedicated to the new portable standalone MPC, the MPC Sample.
User avatar
By Lampdog Thu Mar 26, 2026 1:03 pm
Import Format

.wav, .mp3, .aif/.aiff, .snd, .s1s, .s3s, .flac, .ogg

I’ve loaded a single mp3 file just fine, converts to wav for use inside the machine just like other modern mpc’s.

What I will not do is load an XPJ from XL.
The 1.0 manual doesn’t specifically state that XPJ’s from other mpc’s is supported.
By B-Wise Thu Mar 26, 2026 3:34 pm
Lampdog wrote:Import Format

.wav, .mp3, .aif/.aiff, .snd, .s1s, .s3s, .flac, .ogg

I’ve loaded a single mp3 file just fine, converts to wav for use inside the machine just like other modern mpc’s.

What I will not do is load an XPJ from XL.
The 1.0 manual doesn’t specifically state that XPJ’s from other mpc’s is supported.

Cool but the manual also doesn't mention that it brick you device if load an unsupported file, but it should for something in that case.
By B-Wise Thu Mar 26, 2026 3:44 pm
J.O.BEATS wrote:
I gotta disagree here. occam's razor, common sense and all would tell you that trying to load projects from non supported files wouldnt work. Its clear that cubilese thought it was supported and thats why he was doing it. You can tell from his comments on reddit that he thought mpc3 projects were supported. Not Akais fault

We gonna have to agree to disagree & Occam razor wouldn't made it so that the simplest thing would to just not support the file. Bricking it is more complicated to revolve. I guess we're gonna have disagree on that as well.

Certified Beatz wrote:To make it worst he posts on reddit making it sound like akai dont know what there doing.

He's a mod on that sub. So it makes sense he would report it there to warn others of what shouldn't be a problem in the first place as Akai should've made this danger clear in the manual/their IG or told one of the many YT cheerleaders to warn people of this. No excuse in 2026 with these free ways of communicating. :smh:
User avatar
By MPC-Tutor Thu Mar 26, 2026 3:52 pm
It is not normal for any kind of software to blindly accept incompatible files. There should be a whitelist and beyond that, it's refused or completely ignored. This is really basic stuff and this is 100% on Akai here. Why rely on 'warnings' and 'compatibility coming in April' notices when you can just code the software to not accept the files in the first place?

I'm finding it really weird how people are blaming customers for this.
By B-Wise Thu Mar 26, 2026 5:21 pm
MPC-Tutor wrote:It is not normal for any kind of software to blindly accept incompatible files. There should be a whitelist and beyond that, it's refused or completely ignored. This is really basic stuff and this is 100% on Akai here. Why rely on 'warnings' and 'compatibility coming in April' notices when you can just code the software to not accept the files in the first place?

I'm finding it really weird how people are blaming customers for this.

It's weird but not uncommon as there's a history of victim blaming.
User avatar
By Ultros Thu Mar 26, 2026 6:07 pm
Alright alright, even though we debate and disagree keep in mind we are all friends to some degree...

"without you guys I am nothing. without us you are nothing."

we are stronger as a unit then in division. sometimes i even have to remind myself. I have said some pretty horrible regretful things to ppl and over what? a stupid plastic box with buttons? We also need to not make victims of folks who disagree. especially me.. I have a habit of going from 0 straight to 100 and making peoples feel shitty for their opinions. It's the biggest element of civil decay in our world an I am working each day to rectify my part in it. If you guys vanished and this site disappeared I'd be devastated lol.

It's a shame buddys unit went down buuuut on the plus side. dude took one for the team lol. He got his shit bricked so we don't have to. the sample martyr.
User avatar
By NearTao Thu Mar 26, 2026 6:26 pm
My take is a lot of folks were in the "no way" loading a FW 3.x projects would kill the Sample. I mean... it's just not how the MPC line works. Everything is transient, and you actively have to load a project into memory, none of the other MPCs "just boot" into random projects unless you set it up to do that.

What we've learned is... the Sample will happily copy all kinds of content apparently that can kill itself... and it brings it into local storage, where it then decides it is something it can load at boot time. Seems crazy, but this is probably an execution chain that Akai just hadn't anticipated, and probably hadn't thought to test.

Yep... bro definitely took one for the team, which sucks... but also means that until we get a proper "factory reset" during boot up... probably not a good idea to go poking around too much.
User avatar
By Lampdog Thu Mar 26, 2026 9:55 pm
B-Wise wrote:Cool but the manual also doesn't mention that it brick you device if load an unsupported file, but it should for something in that case.

The manual tells you what's supported.
By B-Wise Thu Mar 26, 2026 11:32 pm
Lampdog wrote:
B-Wise wrote:Cool but the manual also doesn't mention that it brick you device if load an unsupported file, but it should for something in that case.

The manual tells you what's supported.

I get that but like I said it also doesn't tell you it'd kill your damn box. The lack of a warning for that level of consequence, which should be possible, especially for box that's meant to a MPC gateway drug is bad business. If you don't any new input to add let's not go in circles.
User avatar
By NearTao Fri Mar 27, 2026 12:22 am
I'd be willing to be that Akai had no idea... they probably hadn't tested that workflow and didn't know to say "do not do this"... otherwise it's pretty obvious it'd be a terrible business decision to not mention it...

that said... they *probably* should've tested more things... I mean this does feel like something somebody was likely to do...

it's also *possible* that future firmware on either device solves this issue, and due to timing it just hasn't launched yet and had meant to... but *who would know*
User avatar
By Lampdog Fri Mar 27, 2026 1:06 am
The manual tells you what's supported.
By B-Wise Fri Mar 27, 2026 2:37 am
NearTao wrote:I'd be willing to be that Akai had no idea... they probably hadn't tested that workflow and didn't know to say "do not do this"... otherwise it's pretty obvious it'd be a terrible business decision to not mention it...

that said... they *probably* should've tested more things... I mean this does feel like something somebody was likely to do...

it's also *possible* that future firmware on either device solves this issue, and due to timing it just hasn't launched yet and had meant to... but *who would know*

Maybe. I hope it's an easy fix with some secret button combo or whatever.
User avatar
By k_k Fri Mar 27, 2026 3:57 pm
i liked many things about the 404mk2, but couldnt deal with some of its workflow quirks. so the mpcsample seemed ideal for me and i dig it so far. what bums me out though, is how resampling works. i wish i could just choose a pad and resample everything internally, no matter if im playing a sequence, triggering pads or performing with pad fx / flex beat. basically like sample recall, but without a time limit. that would really make this machine perfect for me.

i am new to the akai universe. what do you guys think: how realistic is it that this this could be implemented?
User avatar
By NearTao Fri Mar 27, 2026 6:31 pm
k_k wrote:i am new to the akai universe. what do you guys think: how realistic is it that this this could be implemented?


Akai from 20 years ago would be... you get what you get...

New Akai... not perfect... and I'd never say buy a device on what it could become... but they're clearly taking a lot of notes about what/how things work in the market... and the sampling/resampling could use a bit of work...

Here's to hoping!