MIXVIBES Dj Community old forum

While Cross doesn't officially support a MIDI clock a very talented DJ has written a app called CrossClock for Cross DJ that is a great tool for synching up to Ableton, Maschine or other DAWs that sync to an incoming MIDI clock.

However, if you try and use this tool with Cross it doesn't quite work as expected. After much testing it appears that the problem lies in the video integration with Cross. When Cross has the video component activated the clock in crossclock jumps all over the place, but when de-activated and set so only the relevant MIDI ins and outs are selected in CrossClock , it syncs like a champ.

Hopefully, together with the Mixvibes Team we can figure this out so Cross can synch like Cross DJ can. ( Also respectfully... since Cross owners spent almost 3 times as much, maybe we can get that figured out soon or at least get separate copies of Cross DJ and the old video plugin to see if that works...winkwink)

Any ideas?

All Cross products have the video plugin nowadays. As Cross has more video options than many consumer PCs can handle my guess would be that promising a working clock would require a significant change of priorities at the cost of the video.
Some what the same as the latency strongly influences cpu usage.

Given the number of people requesting it might be good and of course it is great the app is there for those needing it.

I agree with all you say... I was just wondering if there may be a intermediate fix considering how well the crossclock by nillin works with video option in Cross turned off. Are you saying that the clock output itself probably a cpu issue?

Just in my own testing and observing it seems as if it is more of a cross-talk problem ( no pun intended) . Its as if the video generates some form of rhythm that interferes with the beat signal...like its spilling over somehow.

Perhaps since the older versions of Cross worked with a separate plugin ( separate signals ) it might work with the new version of Cross too? I wasn't sure if it possible to install the plug on 3.3+...

The CPU performance would be caused by the need for a stable signal. Even frequent small uses mean other processes have to be unloaded and reloaded to the CPU when running at max.
When running 10 videos + 2 FX + overlay this might be an issue..

So once implemented it would be an irreverseble acceptance of this, which may be of influences to other future feature development.