Support and discussion for all of Akai’s modern standalone MPCs including the MPC X / X SE, MPC Live 1, 2 & 3, MPC One / One+, MPC Key 37/61.
By Frilly Bit Sat Jan 16, 2021 12:17 am
I'm recording my MIDI patterns from Roland TR8S with Akai MPC Live II. Recording the patterns works as expected, with notes being recorded as expected (and can be synced with Sync Receive set to MIDI clock).

However, Live II does not seem to record TR8S motion data (this is the data for knob changes, such as changes to Tuning, Decay, etc.). When the pattern/track recorded by Akai is played back to TR8S the motion data is missing so for many patterns don't sound the same.

Is there a way to capture this motion data in Live II over MIDI?
By Frilly Bit Sat Jan 16, 2021 12:36 pm
Update: I tried recording the same pattern with Ableton - Ableton records the TR8S motions so the TR8S is sending that data over MIDI (i.e. Ableton's recorded MIDI plays back the motion data when played back to TR8S.

I would like to understand why MPC Live II is not recording this motion data? Is there a setting to enable recording all MIDI data or does MPC Live II store only notes?
By Frilly Bit Mon Jan 18, 2021 10:02 pm
Thank you for suggestion. I've tried with automation on both W and R but neither make any difference. Nob changes are not recorded. Very strange. As it works with Ableton, the TR8S must be sending and receiving motion data over MIDI - not sure why Live II can't see these?
By Cockdiesel Mon Jan 18, 2021 11:01 pm
Knob changes are recorded off my Jupiter xm just by recording a sequence do t even have to hit automate write.
Care to elaborate on your actual process for recording these changes? Like are you playing with them some and then hitting overdub or maybe recording these changes on the Roland?
By Frilly Bit Tue Jan 19, 2021 9:57 am
I have a pattern stored in my TR8S that I'm playing back. This has "motion" (knob movements) recorded. I'm simply playing back the pattern on TR8S and recording that MIDI channel 10 in Live II. Also, I've tried making new knob movements on TR8s during Live II's recording but these are not recorded either in Live II.
By Cockdiesel Tue Jan 19, 2021 1:57 pm
Ok so you have the midi ins and outs both hooked up to the Roland?

Are you triggering sounds on the Mpc or just playing from the audio inputs your patterns?

When you turn knobs, hit pads etc does the little midi indicator light up on the Mpc? Both the midi in and out should like up when Information is being passed through.
By Frilly Bit Tue Jan 19, 2021 2:18 pm
Cockdiesel wrote:Ok so you have the midi ins and outs both hooked up to the Roland?

Are you triggering sounds on the Mpc or just playing from the audio inputs your patterns?

When you turn knobs, hit pads etc does the little midi indicator light up on the Mpc? Both the midi in and out should like up when Information is being passed through.


When I'm recording MIDI on MPC, I start the pattern playback on TR8S, MPC records the notes. When I play back from MPC, the MIDI note playback on MPC but without the motion data.

I do exactly the same with Ableton, however, Ableton plays back the motion data.
By Cockdiesel Tue Jan 19, 2021 2:42 pm
So you’re triggering samples on the Mpc?
What exactly do you have the knobs mapped to on the Mpc that isn’t changing?

The issue may be that the midi being sent out doesn’t have a parameter on the Mpc to change.

You may need to tweak your workflow some to get what you want to do.

I have Mpc and Jupiter xm hooked up midi in and out, so I can use it as my keyboard controller but the Jupiter is also my sound module. When I record a sequence I can automate anything on the Jupiter and it will be saved on the Mpc. Like if I want to do a filter sweep or change the envelopes. This is only possible because the Jupiter is essentially programming itself with the right midi data going to the right spot. This data would appear on ableton too, but my question what the destination is.

I have a feeling you would need to have your tr setup the same way and am unsure if the usb midi is bidirectional. You may also need to do some midi mapping, but I think it should be straight forward. Is there anyway you can hook up 2 midi cables between the two?
By Frilly Bit Wed Jan 20, 2021 11:04 pm
Thank you for the suggestions, I connected the TR-8S to Live II with two direct MIDI cables to see if the issue might have been with USB. The same issue occurs with MIDI cables, I can record notes but motion data is not recorded (or not played back).

It just seems that Live II is not seeing TR8S motion data (whereas Ableton can).
By Cockdiesel Wed Jan 20, 2021 11:16 pm
I think you’re overlooking something. Those motion signals have to have a destination. Try keeping the midi cables hooked up and and sequence the tr from the mpc. Once you have a simple beat hit overdub and twist the knobs.

You have to make the tr the controller AND sound module with the MPC in the middle being the sequencer. I believe Enoch when he says it works for him and it works on my Jupiter, leads me to believe that you’re doing something wrong.
By Frilly Bit Thu Jan 21, 2021 11:05 pm
I finally figured this out :)

First, I found out that TR8S motion/automation values are sent by MIDI CC codes (full details at https://static.roland.com/assets/media/ ... ng01_W.pdf) Then I used the Live II's MIDI monitor but could not see any CC codes arriving.

I fiddled with all TR8S MIDI settings and found that if I enable Utility | MIDI | TxEdit Data then the CCs are transmitted (hooray!). Also, to play them back I enable RxEdit Data in the same menu.

According to the TR8S Reference Manual: these xEdit Data options: "Specifies whether MIDI messages that edit the kit settings (panel operations) are sent/received"

Thank you all for your help with this - this is a great community!
User avatar
By EnochLight Fri Jan 22, 2021 6:50 pm
Frilly Bit wrote:I fiddled with all TR8S MIDI settings and found that if I enable Utility | MIDI | TxEdit Data then the CCs are transmitted (hooray!). Also, to play them back I enable RxEdit Data in the same menu.


Yeah sorry about that - I had all of that on in my TR-8, so that's obviously why it worked fine for me from the beginning. Glad you got things sorted! :)