hehe, Logic is so simpel.... You only need to dive into how screensets work, hit the studio in my signature and check the lounge track, all the keys n stuff is audio, nothing via midi. Just recorded a live session and did 3 takes from 2 synths. Drums were used from custom drumkit recorded onto real and dumpted into logic. The scratches were done at uncle nemon's house for use as sanple material, he was not in the mix. All this stuff was loaded into logic and edited from the main screen but none sequenced via midi, we stripped stuff and quantized by ear (just draggin audio bit and giving them the proper fades). The key sections with bass were selected from the 3 recorded sessions, we kept the same build-up of the track but simply took out the "bad parts" and replaced with a better bit of the recording or simply looped a previous section add some diversity but cutting the loop again (slices) and flipped it. I tore up the scratches and try to use it in some sort of texture and pitched/timestretched it in Cooledit which is set as the standard wav editor. I also used them as fx, the rattling in the intro is in fact a fast flare with a hp filter over it and cut n looped, all in logic.
On the mpc tip...
This should go for any platform that sends/receives midi messages;
MPC in midi- thru mode means the MPC is in between the PC and the motif and in sync. PC is master, but can easily be slaved. The principle is this, the mpc controls the motif's 16chnls as usuall except you save all as midi, you write as "midi filetype-1" which means it wont fit all data to one midi-track. No big deal except you can now load the whole session into logic, cubase, fruityloops etc and edit scores and midi parameters (cc's of all function for automating the motif's 16 chnls/sounds) it via the platform's arrange window (nice gui instead of the 2k's step editor). When you're done editing the song you let it record all the midi from all used tracks on the mpc by setting the "S " parameter downleft in the mpc display to "M" on each used midichnl (this is a pain if you dont make a template midi file). Next up simply hit the record button on the mpc, it wont record because it is slaved to the pc, so it waits with recording untill the platform starts. So, now you have the mpc's timing again and even take your setup to stage by simply unpluggin the midi cables of the pc from the mpc.
PC Out -> MPC In1
PC In <- MPC OutA
MPC OutB -> Motif In
MPC In2 <- Motif Out.
I got this setup from midicase, (
http://www.mpc2000xl.com/mpc_computer.htm ). I've made electro/techno livesets this way, made in logic then threw the results into the mpc in order to take the rig on stage. Its also part of the studio and fully patchable on audio and midi so it works for me anywhere basically. It's just to simple when you make a template midi file on the mpc's midi routing. I had setup the way I wanted things to be connected permanently by assigning all available chnls, in this case it would be 16chnl on the motif. Track 1 will be assigned via Midi Chnl B01 to chnl1 on the motif, track 2 on chnl2 via B02 etc untill B16, then save it as midi filetype 1 again. Do the same on your platform, create miditracks and Track one to assign them to midi chnl 1 on your soundcard's output, then track 2 etc till chnl 15. Understand that the miditraffic goes through the mpc, so when editing/writing on the pc it will react aswell, so set the mpc to chnl16 or as prefered. Then save it again as a template (can be in platform's song type, since you can record all data again on the mpc or export it as midifiletype 1).
For automation of cc's I used seperate tracks, of course with the same midichnl of the sound you want to automate to prevent things from getting messy(midimessages for cc's are also eat polyphony, reason why you'd want more midigear because then you have the luxury to set them all to single/performance modes with all available polyphony and power for each machine).
