gertie wrote:stereoroid....any tips on midi-ing up 3 hardware sequencers and cubase together...specially to avoid the midi-loop effect
Yeah: that's what the tutorial Page 4 is all about!
- draw yourself a picture with the Master sequencer at the centre - think about the flow of MIDI: here, you want to spread the load across more than one sequencer, but there is still a flow of clock information, from a source (the master) to destination sequencers.
- the Soft Thru concept is absolutely critical here: you
must be clear on what it is, when and where to use it, and when not to use it. Best way to remember: Master only, don't do it on Slaves. (If you can't find the function in your Slave sequencer manual, that probably means it can't do it anyway.)
Maybe I should go further, give specific examples:
- choose a Master, and stick to it. (The MPC does this well, except in specific cases e.g. SMPTE/MTC environments - I'm assuming it's the MPC, but you can substitute another, as long as there is only One Master!)
- All the other devices are Slaves. They might as well be sound modules: yes, even Cubase (with VSTi)!
So why would you use their sequencers at all?
- spread the MIDI load on playback: more tracks, more CPU power.
- reduce latency: every MIDI link means a delay, so the less distance the MIDI travels the better.
IMPORTANT: know why you are doing these things! If you don't know, figure it out, or don't do it! Every action you take follows a requirement, a need, for a specific feature or function. No "just because you can", that's a bad idea when learning (IMHO). And we can't decide it all for you, we don't know your setup or how you want to work.
I'm imagining a scenario with the MPC as the Master, and 3 slave sequencers:
- a Emu PX-7
- the sequencer in a Triton.
- a PC with Cubase SX and a bunch of VSTi
Like in the tutorial, I think only of the "downstream" or "output" side first.
Hook up all the MIDI Out cables:
MPC OUT A -> Triton IN
Triton Thru -> PX-7 IN
MPC Out B -> PC IN
You can send MIDI Events from the MPC to the other devices, and record them there, or Program them directly. But when you hit Play on your Master sequencer (MPC), what do you want to happen?
- The other sequencers should start: that means External MIDI Sync. (MIDI Clock unless you have a MTC/SMPTE requirement for video work).
- You're not sending all the MIDI from the MPC directly, you're using the power of your other sequencers.
- So, you will put the MIDI events in the other sequencers, according to the sounds they control (Triton sequencer for Triton sounds, Cubase for VSTi and audio tracks, etc. ). Remember, external MIDI links (by cable) are slower than internal communication in another sequencer/sound module
- Even if you had the events in the MPC during construction phase, don't duplicate! If you move events between the sequencers, make sure you delete (or at least disable) the old version.
Then the rest of it is as I described:
- Keep it simple: only hook up MIDI cables if you need them. Example: if Cubase is your slave sequencer, will you want Cubase to send MIDI out to the MPC or Triton? No. So don't hook up the PC MIDI Out at all. The same rule for the others. (Dunno? Then think about it, but don't hook up until you
know where the MIDI is going and how to get it there.
- But you may want to use the Triton keyboard to play the VSTis on the PC, so it makes sense to hook that up to the Master, then use Soft Thru to route MIDI to the PC In.
- Why not hook it up directly to the PC? Well, you could, if you're careful, and your PC has 2 MIDI Ins (you need 1 for the Clock already). But "routing" thru the master means you can do it with fewer cables or without replugging, and you have more flexibility (e.g. to play MPC samples from a keyboard like I do).
I honestly can't make it any simpler - if all this is too much, how about using one sequencer only, at first, treat everything else as sound modules until you find your feet? At least start with 2 sequencers, don't dive in head-first unless you know where the rocks are!
