Midi problems when using MPC 2500 as a slave...

Hi,

I could do with a little advice. I'm trying to use my MPC 2500 as a slave, with a Trtion Extreme as the master. I'm well-used to controlling stuff from my Triton but am having problems using the MPC in this way for the first time.

The MIDI connections I'm using are just as you'd expect - Triton out to MPC in, and vice versa. When I hit record on the Triton and play the pads on the MPC, the events are recorded successfully on the Triton's sequencer. But when I play the sequence back, I don't get any sound out of the MPC.

I'm guessing that I must have set up the MPC's MIDI/Sync menu incorrectly in some way, but I can't figure out how. Here are the settings I'm using;

MIDI page;
Active track - 16 (I only need the MPC for one track)
Soft thru - As Track
Program change - on
Pad to internal sound - on

Sync page;
Sync in - 1(slave)
Sync out - off

On the main page, I have the MIDI channel for the program set to A16, the same track as I'm using on the Triton's sequencer.

Any idea what I'm doing wrong? Any advice would be appreciated.

Pete.

....what happens if you play and record the mpc sounds from the triton keyboard into tritons sequencer...?

and it's a pity if you reduce the mpc to a sondmodule....
best is, if you record into the mpc....it's the much better and tighter sequencer....
and mpc does a much better job if it's set to master....

just let both sequencers run in sync, but let them both do what they're invented for....

Hi Reeloy,

The Triton successfully records the note events (the hitting of the MPC pads) into its sequencer, but for some reason won't trigger the sounds in the MPC when I then play the sequence back.

I agree with you that it's a shame to use the MPC as a sound module. I wouldn't usually do it, but the piece I am working on is already 90% finished on the Triton.

You mention running both sequencers in sync. I would very much like that, but can't figure out how. I was hoping that the MPC would start rolling when I started the Triton sequencer, but it hasn't. If you know how to get the two running together, that may well solve my problem.

Thanks for your advice,

Pete.

I've sorted out the problem, (although I still don't know why it was a problem).

Although the Triton was connected to the MPC by the usual MIDI in/out cables, the MIDI out from the MPC was put through a Midi Solutions 2 into 1 merger (together with the MIDI out from another module) before going to the Triton's MIDI in. I decided to take the merger out of it and rewire the MIDI connections so that there was a direct in/out connection between the Triton and MPC. After that, it all worked fine.
It also turned out that the Triton's sequencer only recorded the data generated by hitting the MPC pads when the other module was switched on. Leave the module off, and nothing got recorded. It was the fact that I could record the sequencer data in the first place that was throwing me.

The bit I don't understand is why the MIDI merger only does part of the job - I don't know if that is a normal limitation, or whether it's faulty. Whatever...

Thanks to Reeloy for his help, and also to the other users for all the interesting stuff they post. It's all appreciated.

Pete.