Help get this topic noticed by sharing it on Twitter, Facebook, or email.
I’m confused AF

MPC X Incoming midi filter / channel select

Hi, I have a 20+ piece midi hardware production studio w a standard 3 port (48 ch) I/O template for use with multiple sequencers & a DAW. I like the MPC X a lot but I’m having a major, show stopping issue with midi.

ALL the midi, on BOTH midi inputs going in to the MPC X, is being recorded to whichever track is recording! I have three other synths and another sequencer on the same midi cable as the X so all the midi for the other gear, is being recorded onto whatever midi track is recording within the mpc. Needless to say its... frusterating.

I’m in here trying to WORK & the bassline from the SE Engine triggering the Minimoog is also making casaba shakers go off in the X, & in a very un-casaba-shaker-ish way! Sounds awful, THEN IT GETS RECORDED!?

Where is the incoming midi filtering/routing view?

WHERE IS THE MIDI INPUT CHANNEL SELECT!? (at the very least)

Theres 2 midi inputs & 4 midi outputs; I’m assuming Akai knew there would be hardware midi users trying to hook into this thing...

I have a 35y/o Prophet 10 that knows how to input filter; that has separate input channels for its two synth boards. I have an 18 y/o MPC4000 that has complex midi routing & filtering & input chanel selection built right in. Whats going on here?

Did they really just release a $2000+ drum machine with 1982 style omni midi in?

Am I missing something?
4 people like
this idea
+1
Reply
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated

  • 1
    Something must be done for real! Two (2) physical midi input ports ..but no splitting.
    As "strange" this might be, as obvious it seems that there will be more to come via
    software updates. The last update brought the MPC standalone forward ..midi-vise.
    Now there's need to get into details via updates. We're curious about the next MPC update, since we think Akai devs can/will deliver.

    PSOUND
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated

  • Wait, they started selling it before it even had midi in stand-alone? LOL! Nice.

    Hey, dont get me wrong, its totally possible for the X to be top dog flippin amazing. Its has functions I never even thought of & I’m really enjoying getting to know it!

    BUT: they have GOT to keep working on these kinds of details for it to get it where it needs to be.

    CANT WAIT TO SEE WHATS NEXT o_O
    • We think the MPC hardware is convincing, the software (updates) needs to push
      it forward. On the other hand the MPC software is already positively thought thru,
      that's why we're here. (talking about 4 sound layers per pad, serious filter options,
      external midi controller support/update 2.2x, random event creation/update 2.2.x)
      Complainers go check them machNIes, and come back again.. if they can notice.

      But, one mistake we're not doing again is ..waiting or godot
      aka waiting for something/MPC updates which might not appear at all. It's a one
      foot in the door and one foot out ..situation. We'd like to have both foots in t.b.h.

      PEACE/o
      PSOUND
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited sad, anxious, confused, frustrated

  • Hey everybody,

    Thanks for posting!

    MIDI filtering and multitimbrality is a commonly requested feature and I would really like to see it added to the MPC X and MPC Live workflow myself. Be sure to submit this as a feature request with the MPC 2 Software's built-in feedback module. The feedback module is represented by a smiley icon at the lower right side of the software next to the browser icons. This information goes directly to the Akai team for consideration!

    If you need an alternative method of submitting feedback, you may use the following links:

    MPC - Submit a Feature Request

    MPC - Submit a Bug Report

    Thanks for your feedback!
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated

  • Also, what Akai refers to as multi mode, is coming. This has been confirmed by an Akai representative in a different forum (gearslutz.com). However, for way over a year now, the big question has been when.

    I bought my MPCX about 6 months ago, and after about a week or two, after the initial wow factor, I ran into the very same issue, had a hard time accepting that the machine had been out for a year and couldn't deal MIDI properly. Having a lot of MIDI hardware, but cannot use them all at the same time, I had to segment various hardware with different MIDI routers, so using different route programs I can use certain hardware. This takes away creativity. Also, the reason I chose the MPCX was to replace computers.

    I used Cubase (since before it was called that) and BitWig, tons of plugins and got sick of updates, upgrades, side-grades, dongles, DRM, etc. Too much management of software, not music. Dedicated hardware is just so much more straight forward.)

    I try to make sense of it in my mind, but it is pretty obvious that anyone using multiple MIDI equipment presume the MIDI implementation of 4 outs and 2 ins to have the ability to address 64 channels and 32 channels.

    Ironically, even Akai themselves in the MPCX user guide explains MIDI Channel this way: "This is a very important element of most messages. A receiver can only respond to incoming messages if its receive channel is set to the same channel as the one the sender is using to transmit data. Subsequently, the sender can address specific receivers individually. MIDI Channels 1–16 are available for this purpose."

    So I would guess that omitting a proper MIDI implementation was originally some poor decision in some meeting to shortcut getting the machine on the market. This is just a guess, of course, who knows.

    Anyways, so according to Dan from Akai, multi mode is coming. Hopefully before I retire. LOL!

    My gut feeling is that it will be implemented and that we will also be able to use USB MIDI inferaces. This latter however, I have not seen in a direct quote of from Akai, but several posts elsewhere, has indications about it. This could also be future plans or that they simply discussed the possibility with people.

    At this point, I really think that the MIDI implementation just needs to be cleaned up and completed. You know, pad-to-midi note mappings cannot be changed in standalone. The audio in the machine is already pretty freaking awesome, so it pains me when I cannot truly use it as what it is being flagged as, with ALL my gear. Well, OK, some older devices cannot do channels either, but they are OLD!

    Yeah, technically speaking, the CV outputs have a better implementation than MIDI, and is even older. ;) I love it, though, lots.
    • view 1 more comment
    • I agree, and they'll get there.
    • __
      So I would guess that omitting a proper MIDI implementation was originally some poor decision in some meeting to shortcut getting the machine on the market. This is just a guess, of course, who knows.
      __
      It very much sounds/feels like that, t.b.h. Anyway, if updates deliver what's left
      behind ..we're fine with that.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited sad, anxious, confused, frustrated

  • Also along these lines would be the ability to change the way the sequencer responds to midi start/stop. Its no secret most sequencers suck when it comes to continuing mid sequence from a stop, but most gear will reset to sequence start awhen stop is double tapped. Thats also going into the feedback form. :P
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated

  • Regarding the decision not to include this, I suspect it comes down to the fundamental ethos of the design. The MPC is a pad oriented beat maker first and everything else second. To this end, all notes (+velocity and aftertouch) are essentially handled in exactly the same manner as pad strikes (this is supported by the channel pressure bug). That is to say, though MIDI is the "lingua franca" of the device it was implemented primarily to support the pads.

    it seems to me that full MIDI support is an adapter on top of the pad centric view of the world. To that end, since the device only has one set of pads, there is only one true channel for MIDI ingress. If the software was built with this as a design principle, allowing more refined MIDI routing becomes more complex and disallows the usage of the Pad code paths as a means of driving MIDI. It may, however, be the case that by the time such messages reach the actual track programs, No MIDI channel is provided (as the pads don't have one). Instead the MIDI must become the first class citizen with the Pads becoming "just another MIDI input". I put that in quotes because likely it would exist on a non addressable channel to avoid the user having to explicitly map it around their synths.

    Going back to my point around this being a beat making device from their perspective, this says that they would build the hardware and software to support that. The means that from a UX perspective, any MIDI related features shouldn't interfere with the devices function in that regard. The question would be, how would the feature be added to the UI?

    Presumably for all program types you would need an input (multi) selector allowing you to select the Pads, and/or one/all MIDI channels, which MIDI In port (or all) and whether such messages were to be received at all times, or only when the track is selected. If the default were all channels+pads, only when the track is picked, and all MIDI ports. This wouldn't change the default behaviour and allow the flexibility we want, but it would take up space on screen (which is at a premium). it would also add a potential point of confusion to users.

    To the point about CV, I think the only reason it was handled better is that it is so different to MIDI/Pads (a single value per 'track' that is defined at all times) that they couldn't reuse existing code. In many respect it's orders of magnitude simpler to implement and handle than MIDI data, so if they didn't do that right: I'd be very concerned.

    Don't get me wrong, I am very much in support of this as it's extremely helpful for studio and live use, but I suspect it wasn't a priority because it was considered a minority use case. The MPC X alluded to the fact that it could be an all in one studio center piece but I get the impression that the software was built with the MPC Live in mind. That's to say the MPC X is treated like a Live with extra external controls (quite possible analogously to the Pads) and I/O. The consequence is that the software was not made to be a studio centerpiece even though the hardware would suggest it is intended as such.

    I think the best we can do is keep reiterating, through feedback to Akai and these forums, that there is a demand for features supporting live and studio electronic music creation. There are people with a room full of synths that want to just walk around freely (without constantly going back to the MPC) and play on whichever keyboard they choose. This is the model supported by most MIDI sequencers but unfortunately that's not the MPC... for now.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited sad, anxious, confused, frustrated

  • We think the MPC was put on the market with the software beeing a bit unpolished
    ..let's call it that. Having physical non-active midi ports, not active preset slots seem
    hinting for that. We're fine with that.. not beeing heavily in music production or in live
    playing preparations. Users depend on support (updates), since their hardware runs
    by software. If support is not provided, people go elsewhere. If people go elsewhere,
    the product gets dropped + support stops. Hopefully the MPC Standalone hardware
    isn't just a test balloon project with reduced resources to see how the market reacts.
    We enjoy the MPC platform much but quite dislike the above mentioned dependency.
    Proper product related communication, infos about what's next/most wanted features
    would be vital signs of user & product support. Is it just missing or wasn't it planned?

    Having said that ..back to the music

    PSOUND
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated