Forum to discuss all matters relating to the MPC1000 and MPC2500 operating systems created by 'JJ' (all versions).
By Accent Fri Aug 21, 2015 3:58 am
One thing I've been experimenting with a little recently on my Machinedrum is using it to sequence some of my external effects units. However, the Machinedrum will probably get traded soon since the MPC1000 is better for my needs. Anyhow, this has led me to explore the Pad to Midi CC function of JJOS2XL. As far as I can tell, you can only assign a static CC value to a pad. Is this correct, and is there any way around this, so that velocity or something can alter the value sent? It's cool that the feature exists, but it isn't very...continuous. As far as I can tell, to accomplish something like a filter sweep you would need to assign a different value to a range of pads and try to hit them in smooth succession to keep it from sounding steppy (good luck), instead of being able to hit one pad and vary the sweep by velocity or pressure, etc?

Of course, you can also program the CC changes in Step Edit (can't do it live), or use the Q-links (great, but there's only two), but being able to just use Bank D to play effects in real time would be a real game changer for me. Please, someone tell me I'm missing something.
User avatar
By Bugfix Fri Aug 21, 2015 9:39 am
You need other controller with to do that, it makes a huge difference. Look at BCR2000 it's cheaply built but it's a monster inside, it also got LEDs that show automation as you playback. Just don't expect to have this thing working out of the box :smoker: you have to program it manually. You can get a keyboard with some knobs as well, but they could be limited to send only CCs, depend on $$$
By Accent Fri Aug 21, 2015 6:30 pm
Yeah...I've got a pretty decent hardware studio. No shortage of controller options. I've also got a Monomachine and Octatrack which could serve the same purpose as what I've been using the Machinedrum for, but I'm trying to keep those midi channels clear for other things.

So, that said, is there any way to have the Pad to Midi CC play a CC message that is actually continuous, and not a static value? If not, so it goes, but it would be really helpful if it is possible.
By Accent Fri Aug 21, 2015 10:27 pm
Bummer. Fortunately, you can still use step edit for automation, but it would be nice to have more playability over CCs. I doubt that most of my effects units respond to poly pressure/aftertouch, but I think one or two do, so that might be worth experimenting with.
User avatar
By bliprock Sat Aug 22, 2015 2:54 am
Accent wrote:Yeah...I've got a pretty decent hardware studio. No shortage of controller options. I've also got a Monomachine and Octatrack which could serve the same purpose as what I've been using the Machinedrum for, but I'm trying to keep those midi channels clear for other things.

So, that said, is there any way to have the Pad to Midi CC play a CC message that is actually continuous, and not a static value? If not, so it goes, but it would be really helpful if it is possible.

YES THERE IS A WAY :)
Its called pattern to pad. Just make blank tracks of CCs only. You have up to 200 bars to use.
Oh and there is the Qlink sliders of course to. But any type of midi CCs can be made into a pattern and assigned to pad and target track
By Accent Sun Aug 23, 2015 12:36 am
bliprock wrote:
Accent wrote:Yeah...I've got a pretty decent hardware studio. No shortage of controller options. I've also got a Monomachine and Octatrack which could serve the same purpose as what I've been using the Machinedrum for, but I'm trying to keep those midi channels clear for other things.

So, that said, is there any way to have the Pad to Midi CC play a CC message that is actually continuous, and not a static value? If not, so it goes, but it would be really helpful if it is possible.

YES THERE IS A WAY :)
Its called pattern to pad. Just make blank tracks of CCs only. You have up to 200 bars to use.
Oh and there is the Qlink sliders of course to. But any type of midi CCs can be made into a pattern and assigned to pad and target track



Ok, this is really interesting. It doesn't sound like quite the same thing as what I had in mind as far as being able to dynamically play/perform any control over a CC by pressure/velocity, but you can create CC patterns and then save them as pad assignments? I'm looking at this in the JJOSXL manual now...do I understand this right that I could then assign these preset automations as pad assignments in a program and then play this automation? Because while that isn't what I had in mind, that could be insanely useful for me.
User avatar
By bliprock Mon Aug 24, 2015 12:52 pm
yep that is exactly how it works. I doubt you would be able to make velocity change a CC though, that is kinda asking too much imo, but i can see how you can use it, to me though it would not be accurate enough to warrant it, and would not use it myself, as you can just use a controller instead. Pattern to pad will allow complex chains and sweeps as well as having the pad to cc as well. So get into it and make some patterns and you should be able to work around your problem and come up with something close.

yeah you wont be able to get velocity to CC data, it just does not work that way at all. its the value programmed and that is it, though you have 16 pads and 4 banks so that is a lot of CC to pad. and you could make say 4 a range of the CC you want. So pad one is CC71 at 12, pad 5 is CC71 at 25 etc.
User avatar
By consuming Mon Aug 24, 2015 11:44 pm
I don't exactly remember how the MPC outputs MIDI pressure, but if you have a computer in your chain it can probably be accomplished easily using Puredata. if you're trying to keep it hardware-only, an Arduino can be programmed to convert incoming MIDI note velocity/pressure to CC values. Sorry, these aren't in-the-box solutions but possibilities if you're stuck.
By Accent Tue Aug 25, 2015 12:18 am
As it turns out, the trade I was going to do fell through, so I'll be keeping the Machinedrum and don't necessarily need the MPC to fulfill this need, but if I can create programs (just like a drum program, but for automation) with complex automation that can be fired off by hitting pads, that may be an even better option than anything I had in mind. I really appreciate the tips.