4.99 midi buggin out

Yo I had just came back to my Mpc after about 2weeks and went to record some stuff off my fantom. I use my MPC as a midi sequencer as many of you probably already do. Anyway I have my MPC to count in 1 bar and then I start recording. Well the 1st note which is being played on the first click is delayed or is simply not sounding. When I go into my grid edit the note is there where it should be but it only plays correctly if I highlight the note and use play start instead of play. This shit just came out of now where and I cant fix it. Im going to upload the 4.99b and see if that solves it but someone please holla back

Have you set up a program change for that track?

do you have 'shift timing' on for that track ?

This is a bug that still hasn't been fixed...

One workaround for me is to turn on the Master Sync out on whatever midi port the MPC is sending out to the synth (Midi clock or MTC works)...

But yeah it cuts off the first notes only on the first loop....

I dont believe the problem is as simple as the synth being too slow. The problem to me is the JJ OS keeps sending program changes when we press PLAY START to the synth on all tracks even though no PC's are being used.
I think i have verified this by routing midi to my synth (Korg R3) through pro tools but using the Protools MIDI filter feature to stop PC's going through. When i do this the problem doesn't happen for me.

I think its something JJ needs to look into but it seems he doesnt want to because I have sent the bug to him....

thanx for your responses. I dont know what the hell the problem was but I fixed it somehow. I dont know what single thing did it but its done. There weren't any changes made by me to cause this issue because everything was fine the last time I used my MPC. I ended up uploading the new 4.99B and still had the same problem. I triple checked all my settings and still no luck. I then did the master reset and that seemed to have fixed it for now. I reported it to jj and received no response about the issue. I still believe its a bug though.