os version 1.22 sync issues

so my mpc 2500 was working perfectly besides the lower octave issue. i saw there was a new os update and i was thrilled. finally! so i update my os on both my 2500 and was very disappointed cause now im having a snyc issue when dumping to pro-tools. i called tech support and them bastards gave me os version 1.21 which did nothing for my snyc problem so now im basically **** and dumping all the beats the old school way which sucks cause it so time consuming. if anyone has or had a similar issue with there 2500 and knows a solution hit me up please and let me know how to fix the problem
thanks
joe g

Same here. support claims they have not heard of this issue so..basically couldnt help. so i just went back to the original os. sucks though because the new functions on 1.22 was off the hook.

New features in OS 1.22?? I must have missed those new features...
As far as sync issues..there are about 2 or 3 threads on this..

im having a similar problem syncing w/ Logic.. the 2500 will go slave thru midi clock, but the beats slow and the timing is off.. i dont know what to do.... im dumping beats the oldschool way also, shit sucks..

^^^^^ also ive tried os 1.21 & 1.22

jahrome wrote:New features in OS 1.22?? I must have missed those new features...
As far as sync issues..there are about 2 or 3 threads on this..

where are thesew threads? I have a difficult time finding anything using the search engine on this forum. it alsways pulls up loads of posts that have nothing to do with my search, for example - customizing my mpc came up when i search for mpc2500 sync.

anyways, i haven't tried to sync anything yet. i just got mine friday but i will be syncing to digital performer. my question is, someone at guitar center told me that unless your midi interface supports MIDI TIME STAMP your mpc will drift.

WTF? Is this true? And if so, can someone enlighten me to this theory and format because I can't find MIDI TIME STAMP on any search on the motu forums, gear slutz, or here. Even google yields no results.

This guy said you need to save your MPC files to the CF card then take the card and put it into a reader thats attached to your computer. Dump those files into your DAW and then use that sequence to trigger your MPC for tracking.

Really? I mean, this will solve all your guys syncing issue that I do find, but this can't be the RIGHT WAY - really?

the only way the syc issue will go back to normal is by going back down to os 1.1. i had the same issue,sucks because 1.1 doesn't have mtc and it has that ugly pop,but i'd rather have my sync issues straight. it's very important.

Try setting the MPC as a master and then set it as a slave and report your results....exactly what you think/feel is wrong.

forget about it,when you set the mpc as a master,it's wayyyy outta sync.

Can you explain exactly what you been by that? Your answer is very vague.

the protools session and the mpc have the same tempo,but when i press play on the mpc when it's in master mode the sync is not on time at all.

I just got my 2500 and I'm crazy frustrated with the sync problem. I'm not sure if I have os1.21 or 1.22, but when I try to sync to either PT Mpowered or Cubase, the tempos drift. Now, when I sync the MPC2500 to Reason 3.0, the sync is PERFECT! But when I try it with the DAWs, there is always a drift. I just don't know what to do. I want to Rewire Reason to my DAW (Cubase or ProTools) and use the MPC as an audio instrument and dump the wave in perfect beat sync. Shit just won't work. To be honest, it didn't work with my MV8000 either so its a DAW thing and not an MPC thing. I know that don't make you feel better, but at least it ain't just a MPC thing. If there is a special trick to get these samplers to sync to DAWs, I'd be willing to pay to get that info. One.

As far as i am concerned the most usable os is 1.20 [The System Test OS],
MTC works fine on this one. The only downside is the system test issue, and the solution to that is to keep the first OS on the flash drive for emergency. Yeah I know it sucks to go through this but u still gotta make this machine work for you despite the circumstances.

joeg wrote:so my mpc 2500 was working perfectly besides the lower octave issue.

Wait a second... this is the MPC creating this problem? I thought it may have been my Moog. So, let me get this right - the MPC 2500 does not record the MIDI data for the lowest octave?

Is there a fix for this? I am still running OS 1.1 because it syncs well.

midi clock running ok in ur 2500?? it is just mtc the problem?