[Edit] Added version 2 to this post, it uses floating point internally and better manages smoothing. Should now track Ableton clock pretty exactly.
Many have commented that clock sync between Ableton Live and Resolume 3 is a bit dodgy - the BPM seems to bounce up and down uncontrollably. Unfortunately, this seems to be an issue with Live, not necessarily with Resolume. Max/MSP also receives a jumpy clock from Live. It seems like Resolume is actually following this inaccurate clock very precisely! (It is also very possible that the issue is due to the MIDI Yoke drivers - any experience on Mac OS X?)
Here is a simple Max patch that takes the MIDI clock from Ableton Live, smooths it, and sends it to Resolume 3 via OpenSoundControl.
You'll be able to see how the incoming clock from Live bounces around. The patch works by averaging the last few values (default = 5) and sending them out. Of course, this means that response to tempo changes is laggy.
Just download the file and unzip, and open the Max patch in Max/MSP or the Max runtime.
From top to bottom, controls are:
Checkbox for on/off - oddly, once turned on, this doesn't seem to do anything
Menu for selecting MIDI source - select whatever source the Ableton Live clock is coming in on
Button for tap tempo - you can tap in the tempo if you want (but be aware that you have to tap a lot, to affect the moving average)
Number of samples to average - default is 5, smaller number means jumpier clock
Then there are two number fields, one displays the incoming clock from Live, and the other displays the smoothed clock being sent to Resolume
Finally, two fields that let you define the host IP address (127.0.0.1 for the same machine) and port (7000 is Resolume default).