XL3 Pattern to Pad beauty.. triggering MIDI CC/PC strings

With xl3, pads can trigger patterns containing MIDI CC and PC messages. This can be useful when external MIDI gear requires strings of CC messages to perform certain functions. You can set pads to CC to send single messages, but what's nice about patterns is that you can name it to reflect the function it's controlling.

For instance, I've been controlling my looper. It requires a few different CC messages to select a recording track then record. I program a few CC messages onto a MPC track using Step Edit and convert the track of messages using the toPatrn function. I name the pattern (RecLoop1) then assign the pattern to a pad. Hit a pad to record.

This might not be obvious to everyone, so I wanted to point out that this new function is much more useful than simply triggering drum patterns.

Can someone confirm this bug? When a PC message is placed within a pad's pattern, hitting the pad will not send the PC via MIDI. However, it will record the PC message onto a track. Assigning the pad to PC works just fine. 2500 xl3.03

(edit: bug confirmed. to be addressed 3.04)

Yeah it is a beauty. I'm trying to set patterns to track mute the MPC.Hmm another merge issue. I will let him known. Btw I am using a MPC 1000 without a computer so I can't check for your bug.

I got word back.. the PC message bug should be fixed in the next update.

Sulli, I don't understand the merge comment, are you trying to track mute via pad pattern?

consuming wrote:I got word back.. the PC message bug should be fixed in the next update.

Sulli, I don't understand the merge comment, are you trying to track mute via pad pattern?

Yeah track mutes with pad patterns would be the end result of what I'm trying to do. What I did was create a quarter bar mute/rest with the "step edit insert track mute" function--Mode Pad 14/F5.

I created the pattern but when you go to merge it looks like the insertion of track mutes are causing issues to occur.

I did tell JJ on his site.