mpc stops when synced to pro tools with loop playback on

Hi all,
I 've got my 3000 synced to PT 7.3.1 w/o any trouble. But, when I try to loop say the first 8 bars in PT by turning loop playback on, the MPC plays fine and then stops on the 1 when PT loops around. Its almost like PT is sending some sort of reset message on the 1 which the 3000 interprets as a stop command. I can't be the only one this happened to so hopefully You Guys know a work around. I'm using PT 7.3.1 on a pc.
Thanks

Yes.

If you have a loop in your DAW , the MPC3000 will stop when it gets to the beginning.

There's no workaround.

Perhaps if you give a little more information, I can provide some tips.

I.E. What exactly you're doing with the MPC3000 in conjunction w/PT.

ok say i'm using the MPC 3k for the drums in my song only, and I want to create the keyboard parts in Pro tools while the MPC runs along in sync. This works fine until I turn on loop playback in PT. When PT hits the first bar of the looped section, the MPC stops. I don't have this problem in Cubase, which alows me to set loop points anywhere in my song and still have the MPC locked tightly. Its definately something about the way PT is handling the loop function. In fact, I used to do this all the time w/PT 5.3 in OS 9 on my old mac and the same 3000. I upgraded to 7.3.1 and that's when I hit this road block. If it works in Cubase, then hopefully it's still possible in Pro tools.
Thanks for responding

Still running OS9 here

However, I've never known that it will work with loop points, so maybe ur right about the upgrade.

For me personally syncing my 3K, to any DAW is blasphemy. The 3K's sequencer is what I paid the big bucks for. I always sync PT/DP to my 3K. If I'm using the sequencer in my DAW , my mpc will be turned off.

I record everything in the 3K. I'll then transfer the MIDI file to the DAW for fine tuning , and then print the audio.

I strongly urge you to also make PT the slave.

You should also check out the new OS here:

http://www.mansell-labs.com

Yeah Ur right about the 3k sequencer, I love it, but i've collected so many rtas and vst instruments that, for certain songs it's just easier to rock in pro tools, and let the 3k handle the boom bap! I'm going to get 3.5 for sure once i get past this roadblock. Thanks for the ideas Zeusmajor. Anybody else have any thoughts? Thanks again

Aahhh, VST's , right.

Not using too many of those on my 300mhz G3.

It might not be unwise ( if someone doesn't give u an answer here ) to post the same question in the Production Techniques section of the board. Lots of PT users there.

Just be sure not specify that it's a 3K cuz it'll be moved back here.

Good idea,I'll try that. Just to update You though, I tried the same setup w/my MPC 2000 and my SP 1200. The 2k keeps playing but hiccups on the 1. The SP keeps playing but is silent on the 1 almost as if You momentarily hit a mute button. PT is doing something real naughty on the 1. lol I used to lock up my SP to Emagic Ceator (the original LOGIC AUDIO) running on an Atari STe no prob! So much for the advancement of technology. Anybody? Thanks Zeusmajor

tonebeats wrote:Hi all,
I 've got my 3000 synced to PT 7.3.1 w/o any trouble. But, when I try to loop say the first 8 bars in PT by turning loop playback on, the MPC plays fine and then stops on the 1 when PT loops around. Its almost like PT is sending some sort of reset message on the 1 which the 3000 interprets as a stop command. I can't be the only one this happened to so hopefully You Guys know a work around. I'm using PT 7.3.1 on a pc.
Thanks

The "STOP" exhibited via the MPC3000 is as a result of a coding decision made by Digidesign:

http://www.digidesign.com/index.cfm?nav ... emid=21978

The MPC3000 will only "STOP" when following a MIDI CLOCK when it:

a) receives a STOP command via MIDI.
b) if the clock actually stops.
c) receives bad positioning information.

Where setup of sync modes for the MPC's and PROTOOLS are concerned.

Digidesign have this link at their knowledge base.

http://www.digidesign.com/index.cfm?nav ... emid=27770

Most MPC models are covered.

If MIDI CLOCK doesn't work for you ... use MTC.

Personally I choose to use other recording systems that are coded to generate MIDI clock correctly.

Or, to use recording systems that can still follow clock from external devices.

Rohan

Yep, my worst fear realized. Thanks Digi. And thanks Rohan for the final verdict

Real good info unfortunately as of PT 7.4 it's no longer accurate.
PT 7.4 no longer exibits this behavior.
Fixing that was one of the many undisclosed problems they corrected with PT when they released 7.4.
They inadvertently created the problem when they went from PT 6.4 to 6.7 and didn't get it properly corrected until 7.4.
As Rohan explained it would do it with any device that was trying to use MIDI Clock, however now it works as it should.

The reason it wasn't previously resolved was based on other changes they were working toward in their MIDI.
They chose to let the problem stay and just code for the new system instead of fixing it in the old which they had already dead ended at the time.

mpc3000le wrote:
The "STOP" exhibited via the MPC3000 is as a result of a coding decision made by Digidesign:

http://www.digidesign.com/index.cfm?nav ... emid=21978

The MPC3000 will only "STOP" when following a MIDI CLOCK when it:

a) receives a STOP command via MIDI.
b) if the clock actually stops.
c) receives bad positioning information.

Where setup of sync modes for the MPC's and PROTOOLS are concerned.

Digidesign have this link at their knowledge base.

http://www.digidesign.com/index.cfm?nav ... emid=27770

Most MPC models are covered.

If MIDI CLOCK doesn't work for you ... use MTC.

Personally I choose to use other recording systems that are coded to generate MIDI clock correctly.

Or, to use recording systems that can still follow clock from external devices.

Rohan

Sovereign wrote:Real good info unfortunately as of PT 7.4 it's no longer accurate.
PT 7.4 no longer exibits this behavior.

Nice !
Good to know.
PROTOOLS users:
Upgrade to 7.4 or downgrade to a an older, pre-problem affected version.

Sovereign wrote:Fixing that was one of the many undisclosed problems they corrected with PT when they released 7.4.

Undisclosed as a fix in 7.4 == YES

I'm sure that in time, Digi Designs knowledge base will be altered to disclose the fix as being present in version 7.4

Sovereign wrote:They inadvertently created the problem when they went from PT 6.4 to 6.7 and didn't get it properly corrected until 7.4.

Apparently so.

That was a while back now...

Sovereign wrote:As Rohan explained it would do it with any device that was trying to use MIDI Clock, however now it works as it should.

Yep...

Sovereign wrote:The reason it wasn't previously resolved was based on other changes they were working toward in their MIDI.

Better to improve the system as a whole then.

Whilst an interim update to Protools before the release of 7.4 would have been relatively easy to implement. ( and greatly received by end users )

However ...The software evolution / office politics process behind rolling out a greatly improved version would have moved priority on fixing the "minor MIDI clock transmit/loop scenario" issue further back in time.

Ultimately delaying the inevitable inclusion of such a fix.

Such is life with the software development cycle.

Sovereign wrote:They chose to let the problem stay and just code for the new system instead of fixing it in the old which they had already dead ended at the time.

Re-visiting old code is often a challenge.

Rohan.