I upgraded to Foxboro and had craziness when rendering wav files.  If I De-select fast bounce my renders work.  If I roll back I can render using fast bounce.
 
Is it just me?
 
Thanks!   

I have a project that I'm working on...that has two medleys in the project.  Both medleys have tempo changes.  I ended up having to deselect the fast bounce in order for the tempo changes to be recognized.
 
This too is after updating to Foxboro.  Never had a problem with it before the update.

I've done several fast bounces in Foxboro, but not with tempo changes so can't comment on that aspect.

There are 16 songs in this project....but only two of them have tempo changes.  All others rendered out fine.  Just the two with tempo changes were faulty on render.  It was like the tempo change was not recognized...and the tempo of the midi stuff stayed the same instead of changing.

I had this problem tonight as well...fast bounce enabled and the end of the song (which has a tempo change) did not render correctly. I just did an export with fast bounce disabled and it worked fine.
 
Yes, I'm on Foxboro.
 
Glad I saw this thread because I was at a loss as to what the problem could be.

Is this affecting track freeze too? That could mean a rollback for me if so...

watching this space... BAKERS?

I had this problem with Foxboro, thought it was just me.    The bounce was crazy, all over the place tempo-wise.   Uncheck fast bounce, it worked correctly.

Just did two fast bounces in a row, exactly the same selection from the same project.   The first one came out with balance, speed, and vst output completely messed up, the second came out right.   

I had an issue bouncing when I was testing the upsample option. In my case I had changed the option enabled for TruePianos. The bounce was fine. Then I turned off the upsample option and did a bounce. this time the audio was garbled.
 
I reset the audio engine and tried again but it was still garbled. I restarted Sonar and tried a 3rd time this time it rendered correctly. Then when I enabled the option again I had a similar experience.
 
I'm not sure this is related to the same problem but might be a clue. I will keep an eye on this also.