This video shows how to sync up your MPC Live mk2/X/One over CV gates to a Pamela’s New Workout.
Honestly, I’m not too worried about the variance in the BPM that shows up at higher levels. I’ve monitored the gates being sent over CV and have seen that it is not dropping gates, so over time the average will be correct, even if there is a small variance in the BPM at a specific gate trigger.
I’ll go over the setup here and show some pictures, as well as do some math to show roughly what the possible difference is for a note and how far off it might be.
To setup your MPC to send gates, it’s pretty simple. First you’ll want to pick a track, and change it to a CV Track type.
As you can see above the CV PORT is set to CV 1, and the GATE PORT is set to CV 2. For this particular application I am not going to be sending CV information, I just want a consistent clock gate being sent. So let’s change this.
For my purposes I have set GATE PORT to CV 1, but you can use any CV you have available to you. The only thing I’d say to remember is that you’ll need a splitter if you’re on the MPC Live mk2 or on the MPC One, otherwise you can only use the CV 1 through CV 4 outputs to interface with your Eurorack. I documented the splitter solution I have using at Akai MPC Live mk2 / One CV outs in case you’re looking for a solution.
With this setup, you’ll need to record some gates. For the MPC the easiest way to do this is to hold down NOTE REPEAT and lay out a single note consistently on your MPC. My process for this is to press Overdub and Play, then hold NOTE REPEAT set to 1/64 and hold down a single pad for the duration of the loop you’ve got setup. This will lay down a lot of note data at a consistently repeating timeframe that will function as our gate data for the MPC to send.
So what you put together should roughly look like the above. In this case I setup two bars of data, and if I need more then I can either record a longer Sequence, or just go to Sequence and x2 it to double the length. The important thing is that you have notes in place for every part of the sequence playing so that everything stays in time.
Pamela’s New Workout Setup
So the way that you sync Pamela’s to your MPC is going to be through CV clock. One thing to note is that the more gates you send, the more accurate it will be and the faster it can react to a BPM change, but the more signals you send, the more you’ll notice hiccups or oddities as they show up. We’re talking about very small timeframes though, so it depends how sensitive you are.
The first thing you’ll need to do is take the CV cable from your MPC and plug it into the Input Clk jack of your Pamela’s New Workout.
At any rate, if you’re on the BPM screen below, just do a long press on the Program knob. This will allow you to edit your settings to adjust your clock rate. Otherwise you ought to be able to rotate the Program knob to get yourself to the BPM page, and then do the long press.
After you open up your settings menu, you’ll want to rotate the knob to get to the PPQN setting. This is where you will set how many Parts Per Quarter Note that you will have. With a 1/64 Note Repeat, this means that you have 16 Parts Per Quarter Note. If you decided to record 1/64 Note Repeat with Triplets, you’ll need to set your Parts Per Quarter Note to 48. So yes, you can send a wild
With this said, you’ve should now be in sync. You may need to press the Start/Stop button to get the Pamela’s New Workout to start triggering, and then you’ll be off and going!
Below is some data that I collected by changing the PPQN values on Pam’s and adjust the events on the MPC to match. I hooked up the Waldorf Iridium over Midi to watch for BPM variance as best I could and see how that might help correlate to the Pam’s Variance.
Just looking at the data I can already tell you that it’s pretty obvious that the tolerance from Pam’s is a function of how many events you are producing and how far they are off. This is why we’re seeing a PPQN of 16 able to go to a higher BPM of 38 than the lower BPM’s from the MPC with a higher PPQN, while maintaining BPM stability. This is roughly what I would expect.
Even with these BPM fluctuations coming from the MPC, you are still not seeing any displayed BPM fluctuations from Pam’s until you break 100 BPM, and 120 BPM if you are using 48 PPQN.
Am I bothered by this? Not even a little. I have confirmed that every single gate triggers, so you are not dropping events, which would be a problem. Further, the more events that you send, the faster that Pam’s responds to the BPM changes and locks into the BPM.
Also, doing the math at 250 BPM, a variance of +/- 2 is less than 1% off (roughly 0.08%) for timing. Human’s are typically not even that accurate, especially over long periods of time. I know some people get very particular about their BPMs, and seeing the displays wobble over time, but I am not one of those people. This is certainly close enough for me.
That said, I do have a breakout for Pam’s, and I will be trying to sync Midi from Pam’s to my other devices to also see how stable Pam’s is for outputting a clock. Stay tuned!