My goal is to send the
cps/bpm info to the famous Processing.
Then it will need for generating a visual in-sync with audio.
Ah okay. The cps is inside each TidalCycles OSC message. The easiest way to get a feeling of this is to evaluate OSCFunc.trace(true) in SuperCollider. One message could be look like this:
1: [ /play2, cps, 0.5625, cycle, 2295, delta, 0.54214235314123, n, 0.0, orbit, 0, s, bd]
For this reason, you have the cps automatically available if you change or add the target for TidalCycles.
And if you want to get really deep into debugging, you can try Wireshark: