By WaterHead
Sun Mar 07, 2010 9:11 pm
Since I had some serious problems syncing my MPC5000 to Logic I did some further testing with OS 1.02 and 2.00 today and thought I might let you guys know of the results. I use MIDI Clock. Before anyone asks: Yes, I know that MIDI Time Code is more reliable than MIDI Clock. But there are certain problems when using MIDI Time Code. Here is a list of advantages and disadvantages I have yet encountered:
MIDI Time Code:
+ tight timing
+ will cycle a loop in both the software sequencer and MPC regardless of MPC loop setting
+ will sync from any time ruler position
- tempo and tempo changes have to be set on both sequencers separately
- when jumping back to the beginning of a cycle, the MPC will go out of record/overdub mode
(and I mean, hey, one of the cool things with the MPC is to pile up MIDI sequences in multiple runs)
MIDI Clock
+ tempo and tempo changes are transmitted
+ MPC stays in record/overdub mode when jumping back to the beginning of a cycle
- loop settings have to be set on both machines separately
- slightly less tight timing
- playback has to be started on a quarter note on the time ruler in the software sequencer
I personally think that, other than the slightly worse timing of MIDI Clock, one can work around the other disadvantages. But getting dropped out of record mode while piling up ideas in a loop is a real creativity killer to me.
System used:
Apple Mac G5 Dual 1.8 GHz
Mac OS 10.5.8
Logic Pro 9.0.2
MIDI Inferface: MOTU MIDI Express 128 and Ploytec USB-to-MIDI cable
MPC Sync Settings:
Sync In Mode: MIDI CLOCK
Receive MMC: ON
Logic Global Sync Settings :
Send Song Position Pointer: Activated
MMC-Format: Standard
Logic Project Sync Settings:
Send MIDI Clock activated (corresponding MIDI-Port chosen)
Send MMC activated
(descriptions may vary, I am using the German version of Logic)
Test Scenario
For the test I used a drumloop sequence I created in the MPC5000. I used the same Logic project to test with MPC OS 1.02 and OS 2.00. What you will hear in the following audio data is the MPC's sequencer triggering drum sounds of Kore Player in Logic. The sequence was created in the MPC and is fully quantized. I activated Logic's internal click and hit play in Logic starting at the beginning of the project. The signal of Kore Player as well as Logic's internal click was then sent through the S/PDIF-output of my MOTU 2408mk3 and sampled back in the MPC5000 while playing. I used a MOTU MIDI Express 128 and alternatively a relatively cheap USB-to-MIDI solution from Ploytech. The results were the same with both MIDI-Interfaces. Again: I used the same project in the MPC, the same project in Logic, no settings were changed whatsoever. The difference is not a single phenomenon in my case, but can be reproduced EVERY time. I went back and forth between OS 2.00 and OS 1.20 two times, the results were the same. I did initialize the MPC after flashing the OS each time.
Here are the results with OS2 and OS1.02:
Sync Test with OS 2.00
Sync Test with OS 1.02
Results:
You will notice that with OS 2.0 the sync is off the whole time, while with OS 1.02 it just takes a slight moment to catch up and will stay tight.
Personally, I am going back to OS 1.02. Will miss the zoom in chop mode the most …
If anybody is missing any information about the test setup just let me know.
Since I also have licenses for Cubase 4, Cubase 5 and Ableton Live 8 I might do some more tests on specific request with those sequencers too. I highly doubt this is a issue related to Logic though.
Hint for Logic users
When the MPC is slaved via MIDI Clock, don't click just anywhere in Logic's transport bar to start playbackor the MPC will not sync. Instead use the "," and "." keys (german keyboard layout) to position the play locator. This way you make sure playback starts exactly at a quarter note and the MPC will be in sync. In Cubase playback seems to always start on a quarter note, I didn't see the problem occur there.
MIDI Time Code:
+ tight timing
+ will cycle a loop in both the software sequencer and MPC regardless of MPC loop setting
+ will sync from any time ruler position
- tempo and tempo changes have to be set on both sequencers separately
- when jumping back to the beginning of a cycle, the MPC will go out of record/overdub mode
(and I mean, hey, one of the cool things with the MPC is to pile up MIDI sequences in multiple runs)
MIDI Clock
+ tempo and tempo changes are transmitted
+ MPC stays in record/overdub mode when jumping back to the beginning of a cycle
- loop settings have to be set on both machines separately
- slightly less tight timing
- playback has to be started on a quarter note on the time ruler in the software sequencer
I personally think that, other than the slightly worse timing of MIDI Clock, one can work around the other disadvantages. But getting dropped out of record mode while piling up ideas in a loop is a real creativity killer to me.
System used:
Apple Mac G5 Dual 1.8 GHz
Mac OS 10.5.8
Logic Pro 9.0.2
MIDI Inferface: MOTU MIDI Express 128 and Ploytec USB-to-MIDI cable
MPC Sync Settings:
Sync In Mode: MIDI CLOCK
Receive MMC: ON
Logic Global Sync Settings :
Send Song Position Pointer: Activated
MMC-Format: Standard
Logic Project Sync Settings:
Send MIDI Clock activated (corresponding MIDI-Port chosen)
Send MMC activated
(descriptions may vary, I am using the German version of Logic)
Test Scenario
For the test I used a drumloop sequence I created in the MPC5000. I used the same Logic project to test with MPC OS 1.02 and OS 2.00. What you will hear in the following audio data is the MPC's sequencer triggering drum sounds of Kore Player in Logic. The sequence was created in the MPC and is fully quantized. I activated Logic's internal click and hit play in Logic starting at the beginning of the project. The signal of Kore Player as well as Logic's internal click was then sent through the S/PDIF-output of my MOTU 2408mk3 and sampled back in the MPC5000 while playing. I used a MOTU MIDI Express 128 and alternatively a relatively cheap USB-to-MIDI solution from Ploytech. The results were the same with both MIDI-Interfaces. Again: I used the same project in the MPC, the same project in Logic, no settings were changed whatsoever. The difference is not a single phenomenon in my case, but can be reproduced EVERY time. I went back and forth between OS 2.00 and OS 1.20 two times, the results were the same. I did initialize the MPC after flashing the OS each time.
Here are the results with OS2 and OS1.02:
Sync Test with OS 2.00
Sync Test with OS 1.02
Results:
You will notice that with OS 2.0 the sync is off the whole time, while with OS 1.02 it just takes a slight moment to catch up and will stay tight.
Personally, I am going back to OS 1.02. Will miss the zoom in chop mode the most …
If anybody is missing any information about the test setup just let me know.Since I also have licenses for Cubase 4, Cubase 5 and Ableton Live 8 I might do some more tests on specific request with those sequencers too. I highly doubt this is a issue related to Logic though.
Hint for Logic users
When the MPC is slaved via MIDI Clock, don't click just anywhere in Logic's transport bar to start playbackor the MPC will not sync. Instead use the "," and "." keys (german keyboard layout) to position the play locator. This way you make sure playback starts exactly at a quarter note and the MPC will be in sync. In Cubase playback seems to always start on a quarter note, I didn't see the problem occur there.
