Hakai - MPC Custom Firmware with For MPC X, LIVE and ONE

I'm afraid if anybody is coming to have a fight about source repositories, open source communities, linux distributions, open source licenses, open source morals... you've probably come to the wrong forum. Some of us may be up on such things... but by and large folks are just going to go grab their popcorn. You guys can all have a go at each other, but I don't see anything valuable coming out of it.

Agree.

Ultros wrote:make your own god damn video you lazy piece of shit nooby **** halfwit.

If you agree then why are you busting my balls about credit for the ssh shit. like big deal next time i pack a fw i'll do it kickgen free... sorry if i come off like a jerk i'm just tired and ungrateful people kinda irritate me.

I don't know most of you folks on the forum, so honestly, I reserve my judgement most of the time. What I can say is that this thread started presumably as a good intent, and has devolved into something that seems pretty petty to me, as an outside observer.

Again, I cannot judge any of you, but the words seem to indicate...

• I want the credit. It was my idea.
• I know more than you.
• I’m always right.
• I want control.
• I want to win this argument.
• It’s all about me.

This is just general advice, but none of the above will build interest in a project, and is likely to drive folks away from you, the project, and the community. Just make sure you know what your goal is and what you care about...

Good job on using open source code good work the rest.. im not for it have a good one..

this is mpc forums, this beef should be settled in the call out thread.

One of the ethical principles of open source, and free projects more generally, is to mention the original authors of a work, simply out of respect and gratitude.

A bit like when you make a buddy listen to a demo, and two days later he explains to his girlfriend that he's the one who composed it after changing 2 notes!

The KikGen wrote:One of the ethical principles of open source, and free projects more generally, is to mention the original authors of a work, simply out of respect and gratitude.

A bit like when you make a buddy listen to a demo, and two days later he explains to his girlfriend that he's the one who composed it after changing 2 notes!

Agreed

Certified Beatz wrote:Agreed

Sources are marked in the first post.
Leave the dude alone if you don't know what's going on.

The KikGen wrote:One of the ethical principles of open source, and free projects more generally, is to mention the original authors of a work, simply out of respect and gratitude.

A bit like when you make a buddy listen to a demo, and two days later he explains to his girlfriend that he's the one who composed it after changing 2 notes!

To be fair, the OP did mention you in the original post. By name. Credit was given.

NewAkaiUser wrote:

Certified Beatz wrote:Agreed

Sources are marked in the first post.
Leave the dude alone if you don't know what's going on.

All I asked for was a video and was saying if I had another MPC I would try it.. then he started with the name calling..

Yawn. Got too much work to do with my MPC, Ill just wait for Akai to **** up 3.0 properly themselves and install it then.

How did you activate all those new effects that aren't present in either official firmware?

To be fair, I hadn't seen in my 1st reading that Ultros gave my user name when mentioning the image maker.
I would have preferred a clear and explicit link to the Github site covering all the stuff Ultros used..
For me the subject is closed whoever it is.

So, Let's go back to the substantive topic : what to do with a Force binary running on a MPC One ?

1/ when the Force (or a MPC) starts, it sends an identity request (it is a universal sysex), so the software knows you are not using a Force

2/ To change color of pads, the Force software sends specific sysex sequences not compatible with those of the MPC. But pressing a pad will send the appropriate "note on"

3/ You haven't all the buttons you need to use the Force software, and the "Main" button is inoperant.

4/ Qlinks works on the first group. Nothing on group 2-4

5/ Plugins and effects are embedded in the binary : so no way to activate them even if you see some config files, skins, or presets.
So it is not possible to activate a plugin because the code is simply not here ! The plugin management is totally proprietary...

So for sure, it is "fun" to see the Force app running on a One,a X or a Live, but no real usage in fact. So no need to update your MPC with that.

I also worked on a customer controller that could emulate a Force or a MPC controller, so I could mutate my MPC Live in a Force (I also own a X). I have written a specific library that creates Alsa virtual ports and connects them to the ports of my choice before launching the MPC binary. I'm able now to emulate any button, qlink, or pad of a Force or MPC, and receive and interpret the sysex I was talking about above.

One use case of that is on the Force. It has no "controller mode" as the MPC has. With that special lib, I could bring this "control" mode by allowing mapping with an external midi controller. I'm here...

You have a detailed description of that on the MPC reverse engineering site I mentioned above.