Can anyone assist me with this problem?  I am working on a song in Sonar using BFD for the drums.  I find it easier to create the drum patterns inside of BFD instead of Sonar.  The song moves between 5/4 and 6/4 time signatures.  The first time signature change occurs at measure 31.  BFD follows Sonar's Now Time until the time signature change.  BFD goes to measure 26 but Sonar displays measure 31 in the now time.  I inserted Geist into Sonar in an attempt to isolate the issue.  Geist also went to measure 26.  Is this a bug or am I doing something wrong in Sonar?  Any assistance is appreciated 

Looks like someone recalculated measure boundaries when the time sig went from 5/4 to 6/4.
 
30 measures @ 5/4 is 150 beats,
then 150 beats @ 6/4 is suddenly 25 measures.
 
The next measure @ 5/4 is 31, the next measure @ 6/4 is 26. Bug, but is it in both VSTs or is Sonar giving a different measure to the VSTs from what it uses for itself?
 
Do the VSTs need to be told by the user when there is to be a meter change or does the API provide for that I wonder?
 
Anything different happen when you start playback @ measure 31?

i think it's about "chase midi notes" feature: playback was started not from beginning
 
https://www.cakewalk.com/...cements#ChaseMIDINotes

The same thing occurs when I start at measure 31.  Can anyone duplicate this problem.  Insert any sequence based VST into Sonar and vary the time signatures.

Jambuw
The same thing occurs when I start at measure 31.  Can anyone duplicate this problem.  Insert any sequence based VST into Sonar and vary the time signatures.

I've got the following song:
 
BAR : TIME
 1 : 13/8
 5 : 7/8
 6 : 4/4
 7 : 7/8
10 : 4/4
11 : 7/8
 
I played in the drum parts manually using AD2, but just to see if there's an issue with tempo changes and sequence based VST's, I inserted AIR Strike 2.
 
Surprisingly, not only did it change time at the right places but it actually sounded fairly good.
 
So I think the issue is with BFD.