Pardon me if I'm telling you things you already know, but I'll say 'em anyway, just in case. 1) In order for the metro to work with beat-based timing units such as 64n, the global transport must be on. 2) Sending the message 'bang' to a table uses the table object as a probability table (sends out index numbers with a likelihood proportional to the value at each index) rather than as an array (looking up values by index). 3) Are you sure your ctlout object is addressing the correct MIDI port? If you're addressing a software synthesizer or another application, you probably want the port "from Max 1", and need to be sure that the other application is set to receive on that port. If you're trying to control a hardware synth, you need to be sure you're addressing the correct interface and port. 4) In short, you need to verify that the data you want is actually getting to the place you want. Beyond that, it's hard to advise without knowing details of the receiving synth.

Thanks for your reply. I'm sorry but I should have postd this in the Max4Live forum, which would have made my porblem clearer I think. When I turn on the global transport I get CC messages arriving in the instrumnet track (I can recprd them). I'm not too worried abut the probability table issue at present but thanks for pointing that out. I tried to use the Live remote system to get a synth to respond to CC messages but this does not seem to work if the CCs come from a Max patch in another track. Is there a better wat to do this?