Discuss the various methods you use in music production, from compressor settings to equipment type.
User avatar
By dollabillbeats Sun Aug 01, 2010 8:24 pm
ok well i have my mpc2500 hooked up slave to digi003 into ptools 8
now when i make a beat in the mp, i use a bit of off timing for the hi hats and kicks. so that way i can give it some "bounce" .. so it sounds the way i want it within the mp, but when i track the beat via mpc slave (midi) to ptools, it for some reason makes it sound more stiff, like it changes the timing. mind you i have the same tempo in each device. like it will change the quantize or sumthin. and it wont sound the same as in the mp. how do i fix this? the manual cant help and neither can youtube. hopefully this has happnd to sumone before? if anyone has a solution, please feed advice! much appriciated
User avatar
By dabmeister Sun Aug 01, 2010 8:30 pm
What method are you using to sync with...midi clock or midi time code?

Most will tell you that mtc works best, well at least from my experiences.
User avatar
By dollabillbeats Sun Aug 01, 2010 11:45 pm
ok well here is the cable run..

mpc2500-- midi in2 = digi003 midi out 2

then on mpc2500 the settings are on midi clock. mtc wouldnt work for some reason
. i would press play on ptools and the mpc wouldnt move(metaphorically speaking) . but when changed to midi clock ptools played the mp. but when tracking it the timing is not how it should be like in the mp and the recording has crackle(kinda like vinyl sound) which is odd cuz my 1/4 are great quality and im recording in 48bit and highest hrtz. or 16bit and 41000.. this ishh is makin me go crazy mann. anyone knoww what to do?
User avatar
By dabmeister Sun Aug 01, 2010 11:54 pm
dollabillbeats wrote:ok well here is the cable run..

mpc2500-- midi in2 = digi003 midi out 2

then on mpc2500 the settings are on midi clock. mtc wouldnt work for some reason
. i would press play on ptools and the mpc wouldnt move(metaphorically speaking) . but when changed to midi clock ptools played the mp. but when tracking it the timing is not how it should be like in the mp and the recording has crackle(kinda like vinyl sound) which is odd cuz my 1/4 are great quality and im recording in 48bit and highest hrtz. or 16bit and 41000.. this ishh is makin me go crazy mann. anyone knoww what to do?


I found this off of the PT forum about how to use mtc.

In Pro Tools:

1) Go to the Setup menu and choose “Peripherals…”. Click on the Synchronization tab and set “MTC Generator Port" to the corresponding MIDI output port.

2) Go to the Setup menu and choose “Session". Set "Time Code Rate" to 30.

3) If your Transport window is not already open, open it by going to the Window menu and choosing “Transport”.

4) Go to the View menu and highlight Transport. Choose Synchronization and click on the GEN MTC that appears on the Transport window.

5) Press play in Pro Tools and the MPC should now be playing along with Pro Tools.
NOTE: (When using MTC, it is recommended to add 1 or 2 bars of pre-roll.)
User avatar
By dabmeister Mon Aug 02, 2010 12:19 am
dollabillbeats wrote:and in mpc i set the slace to mtc? and recieve mmc=ON ?


Right! Set the mp to recieve mtc at the formentioned rate and you're good.

MMC (midi machine control) doesn't have any affect at all on sync, so you can leave that off.
User avatar
By dabmeister Mon Aug 02, 2010 1:08 am
dabmeister wrote:MMC (midi machine control) doesn't have any affect at all on sync, so you can leave that off.


MMC is another fancy way of saying remote transport control. Sys Ex commands are sent to tell a device to start, stop, fast forward, & rewind, which are all transport commands.

Nothing to do with any sync preferences what so ever.
User avatar
By dollabillbeats Mon Aug 02, 2010 3:54 pm
bassicaly when i did all those steps. nothing worked. at a point ptools stopped playing the mpc. so i was at square one again. so i got it working again but pro tools wont play when set to mtc, only on midi clock.and when it plays on midi clock on the home screen it reads clk sync.then when i press stop it reads- rk clk- for a moment then goes away. its real tricky and the timing keeps getting corrected after tracked into protools