For discussion about setting up your studio and advice on the gear and equipment within it.
User avatar
By chrisrob101 Tue Apr 24, 2012 2:26 am
Hello people!
I have an mpc connected to Cubase SX via interface. I can control the mpc from Cubase. All tracks indicate audio being received and I can hear the individual sounds. When I click play on Cubase, the MPC starts playing like it should. However, when I click record on Cubase, I can hear the sounds from the MPC, but the transport on Cubase will not move forward. Preventing me from recording.
When I set SYNC to 'Offline' and press 'record', the transport bar moves, but I the MPC sequence does not start playing when I press record on Cubase.
When I set SYNC to 'Idle', the MPC sequence starts playing when I press record, but the transport bar does not move forward.
Any ideas what setting I may have wrong?
User avatar
By chrisrob101 Thu Apr 26, 2012 2:46 am
Hey Mr Debauch,

Firstly, just wanna say thanks for replying to this.

Here's what I have going on at the moment:

Computer MIDI OUT > MPC2000XL IN

MPC MIDI SYNC IN:

MIDI TIME CODE
FRAME RATE: 25
RECEIVE MMC: ON

CUBASE TRANSPORT SYNC: IDLE

CONFIGURATION:

SOURCE: MIDI TIMECODE

CONTROL OF MACHINE: MMC

CONFIG OF MMC:

DELTA AP: MIDI IN
DELTA AP: MIDI OUT

CONFIG TIMECODE:

SEND: DELTA
RECEIVE: DELTA

Hope that makes sense. Not really sure where to go from here. I want the computer to control the MPC which it does to a certain extent as the MPC starts playing. The main problem is that the transport doesn't move so I can't track the audio in Cubase.

Many thanks,
Chris
User avatar
By Lampdog Fri Apr 27, 2012 10:13 pm
I've already noticed one thing wrong but I can't give you the sandwich.
You gotta be able to recognize which deli slices go where and in what order.
User avatar
By chrisrob101 Sun Apr 29, 2012 11:04 am
Hey Lampdog,

Firstly, just want to says thanks for giving me a heads up and letting me know something wasn't right, it gave me the determination to persist. I learned quite lot when I hit the studio last night and achieved a positive result.

I updated Cubase to SX3 and went through the Akai help notes step by step. I ended up with this:

Computer MIDI IN > MPC MIDI OUT B

SYNC: IDLE, CONFIG: AS IN AKAI'S GUIDELINES

MPC MIDI SETTINGS:

SYNC IN: N/A

SYNC OUT: AB, MTC, FR:25, SEND MMC: ON

MPC MIDI IN 1 > ROLAND SPD-S OUT

ROLAND SPD-S IN > MPC MIDI OUT A

SPD-S MIDI SETTINGS:

CH:9, LOCAL CONTROL: ON, SOFT THRU: OFF, DEVICE ID 9, PC TX/RX: OFF, CC TX/RX: OFF

I was able to sequence on the MPC using a mixture of samples and module sounds and then record the beat sync'd to Cubase.

It was almost perfect except Cubase is a bit slow off the mark. It's not latent, it just doesn't record the first beat or two. Does that have something to do with the left and right locators or is it something to do with the Frame Rate? Cubase automatically detects the FR as 25. I can think of a way to get around it by recording a bit of extra count-in but I'm sure there's a better way. Should I change the FR?

Now, I basically press record on Cubase and then start the sequence using MPC as the controller. To playback I mute the MPC and SPD-S on Mixer (or press SYNC INT on Cubase Transport?) How does that seem to you? This was the only way I could get everything working and I tried and double checked everything.

Once again, thanks for the encouragement and looking forward to hearing your comments.

Chris
User avatar
By Lampdog Sun Apr 29, 2012 4:25 pm
GREAT man, I knew you'd hit the mark soon as you hunkered down and got into it just a bit more. Usually it happens that exact same way, at first it baffles you messes with your brain but the minute you decide to go at it with focus/patience you usually end up getting what you want outta your equipment.

At the beginning of the seq/song whatever program in 1-2 blank bars to give the midi time to lock up and then everything will play in sync once the actual music starts. Many people go that route, I do too.

The muting is fine, that's what mute buttons are supposed to do, lmao.
And it cuts off a potential audio loop problem (sound going back and forth inside the same open route)