sync problem... sorry if this has been discussed before

again i appoligize if this has come up before. the search function on this site doesn't really agree with me.

here's the deal... i have a 1k with jj. i had an earlier version in but just upgraded to 4.99 and i still have the same problem. i'm syncing to protools HD using midi beat clock. when i start my protools session for them beginning everything is fine but if i stop it and start again the mpc is not locating to the correct bar/beat. i've tried this with mmc on and off. the mpc just starts playing from whereever it stopped no matter where the protools starts from so nothing is in sync unless i either start from the beginning of the protools session or set the bars and beats on the mpc to the same location that i'm about to start protools from. i also use an mpc2500 with JJ OS at my studio and this never happens. it always locates to the right place. does anyone else have this problem or a possible solution?

if there's allready a thread about this can someone give me the link?

thanks

Its the bug! When we people believe me? I've been dealing with this for 2months now except I sync my fantom to the MPC's midi clock but the same result. there is no fix for it right now. All we can do is hope that jj can find it as well and fixes it. I've never really had an issue with a bug before that kept me from working but this one takes the cake. Send it to jj and just hope they aren't too busy with the os2 to fix it! 1way!

thanks. yeah i've tried everything. it just won't locate correctly. i hit jj about it hopefully he works it out. i'm just surprised that it works fine on the 2500 and not the 1000. i thought the software was exactly the same.

yo if this is in os2 as well, there's more incentive to get it done.
i will be testing this tonight, as well as others. tonight's a good night to hunt.
i'd appreciate all the info possible, i remember several threads regarding this
the most important thing though, i have, which is steps to reproduce it. you posted them in the other thread.

Go Nym Go! Lol! Its as simple as connecting both midi cables to a keyboard from the mpc using it as a midi sequencer. Select midi clock as the setting on mpc and the keyboard should be set to be a slave to the midi clock. Select all the appropriate channels on the mpc then attempt to record notes via keyboard. If your keyboard has any reverberating or pulsing sounds then those would be the perfect sounds to use for tests. Record a note on the 1st count of the 1st bar (press and hold a key works better) and then press stop. Press play and the midi clock does not send back the appropriate directions as far as timing to the keyboard.

*Also if you sit at the midi/sync screen on the mpc where you can choose midi clock or MTC, if you toggle between midi clock and OFF you'll notice that when you hit play between the 2 that the start time is perfect when the clock is off but the problem exists when its switched off. Holla! Go Nym Go! Bad JJ! Lol!

1.Power on Mpc
2.Go to the midi sync menu and select midi out channel A master, midi clock, with MMC off
3.back to the main menu and change the track channel to midi, turn the program off, PC off, and the midi channel to 1A.
4.Using 2 midi cables connect one end of each cable to the mpc's midi in and out connections 1 and A.
5.Connect the in of the Mpc to the midi out of a keyboard and the out of the mpc to the midi in of the keyboard.
6.Adjust your keyboard to be a midi slave.
7.enter the record mode on your mpc and on the 1stcount of the 1stbar play and hold a note for 2counts repeating this on the 1st count of every bar for a 4bar sequence. Allow the recorded info to playback for an additional 4bars before pressing stop.

8. Press play start and sound is cut off.

This is extremely disasterous due to myself having a roland fantom in which the tempo can only be adjusted in whole numbers(88,89,90) When tuning samples sometimes the sample tempo is found at 87.4, 86.5,88.3 etc. Without being able to sync to the mpc's midi clock this is impossible for the fantom to playback patches that are tempo dependent!

i just followed these steps in reason.
steps 7 and 8 got a little confusing.
"Allow the recorded info to playback for an additional 4bars before pressing stop," you mean just let it loop for a while? playing a single long tone on every bar?

what do you mean "press play start and sound is cut off?" sound from your slave?

after letting my sequence loop and hitting playstart abruptly, the first recorded midi note played as normal. starting and stopping my MPC throughout this sequence also resulted in normal behavior/sync adherence, as did moving around my cursor keys.

what did i leave out?

I heard that midi clock doesnt transmit song position pointers, mtc does send this but it doesn't transmit tempo info.

edit:ive just tried what nym did:mpc into reason and it worked the same i.e. play start jumps the seq in reason back to bar 1 beat 1. play and stop works with everything still synced too.

Have you tried the fantom with any other sequencer as the master?

double edit:
for me reason is missing the sound from the firstbeat sometimes when you hit play start(more often if you dont hit stop first.)
it seems to work all the time though if you have a count in bar set up for play and record

double edit:
for me reason is missing the sound from the firstbeat sometimes when you hit play start(more often if you dont hit stop first.)

yeah as someone explained to me waaaay back in the day that's a symptom of midi clock, not a bug to any particular device. i don't think that is the issue these guys are having here, though...in fact the more i read their 2 stories the more i feel like it's 2 diff. issues almost

the most confusing part is that 1waymusic said it USED to work, but then stopped working...bizarre.

Nym wrote:the most confusing part is that 1waymusic said it USED to work, but then stopped working...bizarre.

that's it eh...

i've NEVER had this problem...

how many people are actually having this problem?

is it only with 4.99?

i'm still on 4.97 -- MIDI functions exactly as it ought, no clock problems at all.


really weird.... sucks for those having this problem... i feel your pain 1way!


to the original poster, sound asleep --- i'm not quite understanding you, is the MPC slave or master
in your setup?

when you say it's not tracking to the correct bars/beats when you press play again -- are you using
song mode, sequences, one long sequence... ??

these actually sound like different problems to me too.

t_bias wrote:to the original poster, sound asleep --- i'm not quite understanding you, is the MPC slave or master
in your setup?

when you say it's not tracking to the correct bars/beats when you press play again -- are you using
song mode, sequences, one long sequence... ??

these actually sound like different problems to me too.

bias...

yeah my problem is definitely different from the other issue in this thread. i am using the mpc as a slave. using midi clock. the only problem is that the mpc is not locating to the correct bar of the sequence. i'm actually just using it in pattern mode on this track. programming loops and fills/layers and then tracking them into protools and arranging the song there. i haven't tried it in song mode but the mpc1000 is chasing the beat clock in a completely way than my 2500 does. basically if i have the cursor in protools at the very beginning of the project, at bar 1, beat 1 and press play, the mpc will start from bar 1 beat 1, but if i have the cursor set at, let's say, bar 2 beat 1 in protools and i press play it will start from whereever the counter in the mpc is set to. so if i press the bar buttons on the mpc and get it to bar 2 beat 1 and press play on the protools set as this same location it will sync fine, but if i press stop after 1 beat then the mpc rests at bar 2 beat 2. then if i press play again on the protools (cursor is still at bar 2 beat 1) the mpc will start playing 1 beat out of sync to the protools. i'm sure that's very confusing. i'm stoned. it's not working right, unless i play my protools session from the beginning, which i don't want to do just to overdub a new sound at bar 49.

Yes I mean after you record the info let it loop for 4bars and listen to the recorded info. Play start takes you to the beginning of the sequence where the issue occurs.

I know it might sound confusing but its even more confusing for me because this issue came from no where. My setup had not been moved or changed around for quite some time before this issue. I hadn't changed any settings on anything and it just happened.

Im not saying our issues are the same but they both are involviong midi clock

soundasleep -- is there anyreason why you need use midi clock?

why not MTC --- it should work fine then.

mikolo wrote:I heard that midi clock doesnt transmit song position pointers, mtc does send this but it doesn't transmit tempo info.

i'm pretty sure that's right... so long as your BPM's have been set correctly, should be fine...

if that's true why does it work correctly on my 2500?

yeah... good point.

fraid i'm no use to you on this one mate...

ok i just got back from the studio where i have my 2500 synced up to protools exactly like i have at home. here's what i noticed... whenever i click in the edit window in protools the 2500 (with jjOS) locates to exactly where protools is, so when i push play it's always located at the right place and syncs to the right beat. that's what the 1000 is not doing.