MPC4000 Timing Issue Put Very Simply

I had an MPC1000 for almost 10 years with the same setup. No need for sync, pressed play on the 1000 in realtime and it synced up for minutes and minutes.

How do I reset the MPC and change the CPU? Thanks for the intelligent and helpful response.

It's in GLOBAL mode, is it not? There's a button (F6?) you can press there to do INITIAL or something like that..... it's in the manual....

Beat clock keeps it in time for the whole session, but it fires inaccurately. Not enough to make a huge difference, but it is kind of frustrating. If I recall correctly, the 16th's may be like 100 or 400 samples off grid.

The problem with beatclock is when I have pro tools looping playback, the MPC does not fire recorded notes for the first two bars of the loop. So if I have a 2 or even 4 bar loop in pro tools its a huge problem.

oh well.

I did try that, and all it did was re-initialize my settings (which is a pain).

Is there a hard reset or something?

Dramatix04 wrote:I did try that, and all it did was re-initialize my settings (which is a pain).

Is there a hard reset or something?

Yes, there is. There is also a Reference Manual

what exactly is 'tab to transient'?

you are doing a lot of stuff that could go haywire but putting all the blame on the mpc. this is hardly a scientific experiment - hence why that other study is a bit more reliable.

your beat clock from the computer is fluctuating because the computer cannot send reliable beat clock. you can read up on that litmus test posted earlier to read why.

forgive me if im misreading, but if you don't mind, some insight into 'tab to transient' and maybe even more excruciating detail on how you are doing your 'tests' might show where the error is happening.

Most of the users on this forum are of no help but instead like to add presumptuous comments and geeky emoticons.

1.) Yes there also is a reference manual. THANKS GUY! Very helpful. I've read it. I've searched for the hard reset. If you have found something regarding this why don't you include it in your reply? it seems like a waste of time to respond otherwise.

2.) Again, as stated in the FIRST SENTENCE OF MY POST I'm NOT running midi clock or any sync whatsoever. wow. wow. wow. wow.

Dramatix04 wrote:Again, as stated in the FIRST SENTENCE OF MY POST I'm NOT running midi clock or any sync whatsoever. wow. wow. wow. wow.

Dramatix04 wrote:Beat clock keeps it in time for the whole session, but it fires inaccurately. Not enough to make a huge difference, but it is kind of frustrating. If I recall correctly, the 16th's may be like 100 or 400 samples off grid.

i was referring to THAT mention of beat clock.

i asked for some more detail on tab to transient (wtf is that) and as much detail as possible regarding your process - i'll say it again - you are hardly being scientific about this. therefore i can't, and you shouldn't, take any of your findings very seriously.

for the high standard of response you seem to demand, why haven't you provided an audio file to show your findings?

this could be user error, and frankly your arrogance only strengthens that suspicion.

if you want to get some help - lose the ungrateful superiority complex and try explaining things better.

tab to transient is a function used to cut the audio region at the transient. Its of no significance here.

People here have been rude to me and yet extremely ignorant at the same time so I find it puzzling and off putting. Not referring to you really.

But honestly, yes, I mentioned midi clock at one point as a comparison to letting the MPC run freely. NOT in comparison to the "litmus test".

Dramatix04 wrote:tab to transient is a function used to cut the audio region at the transient. Its of no significance here.

its the very function that your entire test relies on - of course it is significant.

now how about that audio file?