Don't know the value of echoing a singe reported failure which has yet (and may not ever) be reproduced. Especially if failing to mention the issue has not been replicated. Maybe better to suggest working on a copy of the MIDI track instead.

I had mentioned working with a track copy earlier.
 
I suppose I will not mention that other reported error again - I couldn't recall if it had been confirmed or not, only that I myself couldn't replicate it, which was why I had tried to communicate up front that I wasn't 100% sure of it being an issue.
 
Bob Bone
 

Always use the golden rule for applying CAL scripts to midi tracks. "Always use a cloned copy so you always have the original to fall back on if need be".

I tried using it a short while back and some of the exploded tracks wouldn't sound anymore. Checked all the routing and it was good. I've also had that oddity with some older projects. Just some of those little "buglettes" that crop up now and again.
 

Is there an update in X3 producer on the cal. script.?..I'm still using the cal. script from my X1

Pretty sure Cakewalk has not touched CAL this century.

I can't for the life of me understand CAL being deprecated. Fancy having that function in a program that could allow all sorts of extensions to Sonar's functions and there's no guarantee from one version to the next that it will still be there tomorrow.

I've said it before: CAL is the ONLY reason I am sticking with Sonar.   For a little time spent planning a program, you can do hundreds of hours of slow changes in a moment.    I've converted my gigastudio programs to Kontakt5 (changing patch changes to completely different patch changes,  or changing patch changes to keyswitches, with CAL).    And as to doubts about whether it is reliable, I have never seen unpredictable results from a cal script, though granted I always work with directly in midi tracks, not instrument tracks.    And of course you have to get the syntax right in the programs you write ...