[Solved] Clicking during tempo changes

Greetings!
First I'd to say X3 is working great for me (thanks much for the Aria player fix!).  However, there's a click whenever the tempo changes.  Makes for some interesting rit's (can't write the actual word as it gets flagged) in my symphonic stuff:-)  Never encountered this before.  Any thoughts?  I mute everything, it's not there.  I un-mute any track, it's there.
-rich
(X3d)

WDI is probably correct.  This will be due to some plug-in that has tempo-sync enabled.  Go through all the plug-ins and disable them one-by-one to find the culprit.  Some tempo-synced plug-ins do much better than others when tempo changes.  If the problem is with a chorus plug-in, for example, see if you have another on hand (or find and download a freebie) and see if that fixes it.  Also, if the tempo changes are not drastic, try setting the plug-in to non-tempo-sync and manually dial in an appropriate time parameter value.  That should clear things up.

Hmmm..  Good ideas.  The cause was Altverb 6 on the master bus.  But I've been using Altverb 6 for years:-)  Could anything have changed in X3 to cause this to show up now?
-rich

Plenty of things could have changed with X3. Nevertheless the fault lies with the plugin or the plugin configuration or parameters.

I totally disagree with Alex.  When something routine works just fine for the last 5++ years, then stops because of a new release, -- not good.  With this release the Aria multi-player didn't load (fixed, thank God) and now this.  People could loose money on problems like these.
 
I see no sync type option and I'm not using Altverb for anything fancy like beat count delays or anything.  But I welcome further thoughts :-)
-rich

WDI
I don't think it's a question of who's at fault. I think it's just the nature of bpm synced effects. I believe even hardware acts this way. For instance the Korg Electribe has bpm synced effects that sound horrible during tempo changes when synced to sonar.

So it's either the way Sonar sends tempo change data or just the nature of bpm synced effects. I'm guessing it's just the way bpm synced effects behave during tempo changes.

Actually, hosts do not send tempo changes to resident plug-ins; the plug-ins ask the host for this information every time they get the nod to do some processing.  At least that was the way things worked prior to VST3, which I haven't looked at (although it's doubtful that aspect was changed). 
 
Any plug-in that uses delay buffers has do deal with readjusting buffer content and position when tempo changes.  Some are obviously going to do it more gracefully than others.
 
Anyway, considering VST 3 brings up a possible explanation as to "why it worked before".  SONAR now does VST 3.  Any chance the plug-in now being called by X3 is a VST 3 version and you were getting a VST 2.x version before?

It is possible to force VST2 use. See Preferences > File > VST Settings for the VST3 migration options.

Just move the Vst3 version out of Sonar's scanning patg