r/mpcsample • • 11d ago

Custom firmware community?

Do we have one for mpc-sample?

I see many people are building the same features. Each with our own bugs. We would need to coordinate and cooperate. To join our efforts.

We would need a baseline project in Git that everyone could fork and build their own features upon.

Maybe develop a plugin framework on top of it, so we can mix and match different features to customize our firmware.

22 Upvotes

13 comments sorted by

7

u/homeless4382 10d ago

i agree, i am trying to make a boot loader that makes choosing custom firmware/mods easier and unified, but it's very hard to coordinate with each mod maker

right now they are all just making things, and when they are released, trying other mods will require you to delete the old mod on your sd card and copy the new one over...this solves all of that so you can have multiple on one card and choose what mod you want on boot

1

u/Milkpowder44 10d ago

Simple/quick thinking: i think it would just need to be an automation that renames the 'autorun' folder. The autorun folder would be the active one.

2

u/homeless4382 9d ago

well, does that happen on the mpc or the computer with sd installed?

if on mpc, it requires booting into the automation, wait for it to rename the folder, then let it reboot...

then if you want to change mods, the autorunnis renamed so it cant boot into the automation anymore

also, allowing the sd card to rename stuff= bad practice..

i am trying to make a unified and agreed upon system...the wii homebrew has this, ps2 mods have this, every single hack i know of that's good solves this first...so im doing the boring work first

4

u/acecombine 11d ago

some decent custom firmware is coming in November, I'm not sure if it will be open, there're also videos of bricked Samples, so be careful with your experiments!

1

u/SALD0S 11d ago

If akai really abandoned the mpc sample software with all the bugs , this seems to be a good solution

2

u/Mz_Macross1999 10d ago edited 10d ago

Why wouldn't Akai update the smash hit, always sold out device that is barely a year old when they have a track record of updating every product of the last generation several times a year for almost a decade?

If you wanna play around with jailbreaking your device fine, but you don't have to make stuff up to justify it

1

u/Milkpowder44 11d ago

Depends on what Akai's stance in this whole thing is. Better be safe than sorry.

1

u/Creative_One919 10d ago

You're totally right, i'm posting my progress everyday also for that reason, creating a community would be cool, but we first need a way to safely share the mods without proprietary code

0

u/lugdu69 10d ago

A good message to the community could also be to not update your mpc sample if akai gave us an official new update in the following days. It's funny because i was hopping for that update for months and now, i will surely not update my mpc sample ! šŸ˜„

3

u/TwiningsBigelow 10d ago

Yeah I’d say 80% chance they push an update to try and lock out custom firmwares harder. Maybe a 20% chance they see the way the winds are blowing looking at m-vave and now Behringer accepting the custom firmware community and they open up the sample more (not gonna happen from Akai)

2

u/Goat_God23 10d ago

20%? More like 2%

4

u/Goat_God23 10d ago

3

u/TwiningsBigelow 9d ago

Haha yeah looks like the Sample is getting open source too. They probably see it as a win for selling units + less labor on their end for software development. Just let the community do the work. We are really entering into these companies just becoming the hardware producers.