Cross 3.3 HID time-lag problem

Hi,
I have been using Cross for the last 4 years with almost no problem.
Until recently I was still using Cross 2.6.0 version on MacBook pro (2.66 GHz Intel Core i7, 4 GB memory) OS 10.6.8. I use HID system and this set up has never crashed even once.
I finally change MacBook pro to the new Retina one (2.5 Ghz Intel Core i7, 16 GB 1600 MHz DDR3) running on OS 10.9.4 AND update to 64 bits Cross 3.3.3. Since then, I have a pretty annoying problem:
The first time I tried the system on HID system using CDJ2000, one deck was working perfectly, but the the other one (deck A) has an issue: there was a big "delay" between the moment when I push PLAY button on the CDJ and the moment when the track will start. Around 1 to 2 seconds. But all the rest was responding well: pitch, jogg etc... I tried several different tracks and the problem remain. The same track was working properly with CDJ2000 linked to deck B but not with the CDJ2000 link to deck A.
I first thought it is link to "Player Start Time" setting. Indeed, for some reasons it happens that this setting will automatically change when using HID and you often need to be sure both faders are set to zero if you don't want to have any time-lag problem. But I checked and the "Players Start Time" were both set up at Zero.
But then I notice another "weird" thing: the actual "graph" of the track which is running on the top of the screen was "wrong": If I tried to "match" the peak of the track's beat of deck A (yellow) with the ones of deck B (red), it looks like there was also the same delay of 1 or 2 seconds. Can't be 100% sure because I was busy mixing the track but it looks like so.
Then I update to 3.3.6 and tried again in the same club. It starts fine, but after 1 or 2 hours the problem came back (also in deck A). It's important to precise that during this 2 hours, I was playing together with a friend playing on USB keys, and that the CDJ2000 were sometimes going from "LINK" (for HID) to USB. Anyway, the problem of time-lag between the actual press PLAY and start of the song appeared again. Fortunately, once more, there was no problem of "time-lag" using the jogg. But when the problem occurred this time. I was playing back to back and using only deck A so couldn't check properly the hypothetical problem of the "wrong graph", since i couldn't compare to the graph of deck B.
Other info:
The buffer size is set on 512 samples (11.6)
Cash in audio memory max : 9.6 GB
Common HID set up using CDJ2000 aggregated as sound cards.
I have been looking for answers on the forum but did not see anything. My new MacBook pro is a few months old and is only used for DJ.
Where does the problem come from ?
I have been using Cross for the last 4 years with almost no problem.
Until recently I was still using Cross 2.6.0 version on MacBook pro (2.66 GHz Intel Core i7, 4 GB memory) OS 10.6.8. I use HID system and this set up has never crashed even once.
I finally change MacBook pro to the new Retina one (2.5 Ghz Intel Core i7, 16 GB 1600 MHz DDR3) running on OS 10.9.4 AND update to 64 bits Cross 3.3.3. Since then, I have a pretty annoying problem:
The first time I tried the system on HID system using CDJ2000, one deck was working perfectly, but the the other one (deck A) has an issue: there was a big "delay" between the moment when I push PLAY button on the CDJ and the moment when the track will start. Around 1 to 2 seconds. But all the rest was responding well: pitch, jogg etc... I tried several different tracks and the problem remain. The same track was working properly with CDJ2000 linked to deck B but not with the CDJ2000 link to deck A.
I first thought it is link to "Player Start Time" setting. Indeed, for some reasons it happens that this setting will automatically change when using HID and you often need to be sure both faders are set to zero if you don't want to have any time-lag problem. But I checked and the "Players Start Time" were both set up at Zero.
But then I notice another "weird" thing: the actual "graph" of the track which is running on the top of the screen was "wrong": If I tried to "match" the peak of the track's beat of deck A (yellow) with the ones of deck B (red), it looks like there was also the same delay of 1 or 2 seconds. Can't be 100% sure because I was busy mixing the track but it looks like so.
Then I update to 3.3.6 and tried again in the same club. It starts fine, but after 1 or 2 hours the problem came back (also in deck A). It's important to precise that during this 2 hours, I was playing together with a friend playing on USB keys, and that the CDJ2000 were sometimes going from "LINK" (for HID) to USB. Anyway, the problem of time-lag between the actual press PLAY and start of the song appeared again. Fortunately, once more, there was no problem of "time-lag" using the jogg. But when the problem occurred this time. I was playing back to back and using only deck A so couldn't check properly the hypothetical problem of the "wrong graph", since i couldn't compare to the graph of deck B.
Other info:
The buffer size is set on 512 samples (11.6)
Cash in audio memory max : 9.6 GB
Common HID set up using CDJ2000 aggregated as sound cards.
I have been looking for answers on the forum but did not see anything. My new MacBook pro is a few months old and is only used for DJ.
Where does the problem come from ?