By vashypoo
Thu Jul 29, 2021 5:38 pm
hey all, relatively new MPC user here, with a bit of an in depth question, which has now been made a bit more convoluted with the 2.10 upgrade. basically, anyone else having issues making sequences work in Logic without much issue? i'd like to make a sequence in standalone (or even using the VST, which should be the same right?) then export it to midi and then loop that sequence in Logic however many times i need to. this WAS working fine, and now with the upgrade, MPC doesn't seem to recognize the loops in logic, nor does it start any of the other sequences when it's supposed to either.
for context: i am using my MPC in logic via the MPC VST. it has been functional but kind of frustrating. i have a session open and am writing different sequences for different parts of the song. i want to put a certain sequence at a certain part of the song, so i put the marker in Logic where it needs to be, and then create a new sequence and put the tape head in the MPC VST at 1.1 (the beginning of the sequence). i arm record in MPC, then record in Logic, and it will automatically jump ahead some number of bars, and even if i have made the specific sequence only 4 bars, it'll jump to 6 or 8 or whatever it wants. i know it slaves to Logic so I am not sure what setting i need to change or where so i can just write a new pattern/sequence precisely where i put the markers.
like i said, i try to export the midi of each sequence into Logic then loop it in the DAW as a workaround, but now it won't even recognize the Logic loops, so the sequence plays once and that's it. the only other thing i can think of doing is just the "one sequence" workflow and just have one long midi file for the entire song and copy/paste each sequence however many times but that sounds like a pain in the ass.
the other annoying thing is that the MPC sequence will sometimes start playing before the midi pattern comes up in the session, even when i make sure that specific sequence doesn't start for 26 bars in both the MPC and the DAW. (ex: i have the first MPC pattern starting at the 26th bar, so the sequence on the MPC reflects this, and obviously the midi pattern loop only starts at this bar in Logic, yet i will hear that sequence start a few beats or bars early, for no apparent reason.)
any pointers? even if this is a specific glitch with 2.10, i feel like this workflow could be integrated a bit better. surely i'm not the only guy trying to do it this way!
for context: i am using my MPC in logic via the MPC VST. it has been functional but kind of frustrating. i have a session open and am writing different sequences for different parts of the song. i want to put a certain sequence at a certain part of the song, so i put the marker in Logic where it needs to be, and then create a new sequence and put the tape head in the MPC VST at 1.1 (the beginning of the sequence). i arm record in MPC, then record in Logic, and it will automatically jump ahead some number of bars, and even if i have made the specific sequence only 4 bars, it'll jump to 6 or 8 or whatever it wants. i know it slaves to Logic so I am not sure what setting i need to change or where so i can just write a new pattern/sequence precisely where i put the markers.
like i said, i try to export the midi of each sequence into Logic then loop it in the DAW as a workaround, but now it won't even recognize the Logic loops, so the sequence plays once and that's it. the only other thing i can think of doing is just the "one sequence" workflow and just have one long midi file for the entire song and copy/paste each sequence however many times but that sounds like a pain in the ass.
the other annoying thing is that the MPC sequence will sometimes start playing before the midi pattern comes up in the session, even when i make sure that specific sequence doesn't start for 26 bars in both the MPC and the DAW. (ex: i have the first MPC pattern starting at the 26th bar, so the sequence on the MPC reflects this, and obviously the midi pattern loop only starts at this bar in Logic, yet i will hear that sequence start a few beats or bars early, for no apparent reason.)
any pointers? even if this is a specific glitch with 2.10, i feel like this workflow could be integrated a bit better. surely i'm not the only guy trying to do it this way!