X2 Export Problem: Mixdowns Consistently Contain One Track

Thanks for reading!
 
I've been having a problem mixing down (exporting) a project in X2 PE. 
The resulting file consistently only contains one track (used to be dry drum track, now dry keyboard track)
I'm selecting "Entire Mix" iand de-selecting "Fast Bounce" in the export dialog box
I've tried uninstalling both the ASIO drivers and Sonar X2 PE.
Also bounced and froze everything.
Tracks and busses meter during export.
After export, the project only plays the track that mixed down, and I have to close it without saving and re-open it to get it to play normally. 
 
Playback is normal and without dropout.
 
Any clues for the clueless?  Thanks for reading!
 

yup, CTRL-A is your friend during mixdowns.

Craig, Guitarmech 111, 
 
Thanks for your replies.  I had not been selecting all tracks prior to export, as I thought that selecting "Entire Mix"
in the export dialog accomplished the same thing. 
 
I tried your suggestion and was confident I had done so correctly, as all tracks ( not busses) were highlighted in blue.  My mixdown result was the same as before....containing only a stereo piano track. 
 
Do busses also have to be selected, and if so how do I do that ( I'm not new to Sonar...just want to make sure I'm doing it correctly) ?
 
Thanks in advance for your helpful replies.

I make sure to go to "Select None" then choose "Bounce to Track". I then select "Entire Mix" and make sure that all Fx, Sends, Busses, and all that is checked. I also use "Fast Bounce" on the first few times to make sure I got it the way I want.

This is one of those issues where if I was looking over your shoulder I could probably solve it in 30 seconds...something isn't right. 
 
Are you still getting only a single track even when you choose Ctrl-A?

Florida, eh? Encounter a problem in January, and if your back room is still available, let's talk 

Craig, Conley, Grem, 
 
Tried to bounce the mix to a track within the project several ways:
1) CTRL+A, selected all buses and master as well, Tracks, Bounce to tracks, new track, entire mix, 44.1 @ 16 bits,
Triangular Dithering, fast bounce (and slow bounce)
 
This produced the same result as before: a stereo track of 2 keyboards through a TTS-1.
 
2) Grem's way: Edit, Select, None, Tracks, Bounce to tracks, new track, entire mix, Triangular Dithering, fast bounce. 
 
This produced a blank file . Thanks anyway Grem, and glad it worked for you.
 
I also tried Exports following the above 2 methods...results were respectively the same. 
 
I've re-checked all my routing and it all seems correct. All tracks go to busses, expcept one or two. 
All busses go to the master. Master goes to the interface driver (UA-25).
 
What's most puzzling at the moment is that the project plays fine, and sounds good, but I can't get it to 
bounce, or export successfully. 
 
I'm out of ideas at the moment, so all suggestions are welcome. Thanks for reading.

Since all tracks/buses go to the master bus I always just export the master bus, never had a problem doing it this way.

chrisbates
After export, the project only plays the track that mixed down, and I have to close it without saving and re-open it to get it to play normally. 

 
This is the key indication that something else besides your selections and mixdown options is going on. But I can't imagine what that might be. Sounds like some sort of project corruption, given that soft synths are frozen.
 
Did the Cakewalk tech suggest non-fast bounce after you had already reported this problem? Because I would not recommend that in general.
 
Try disabling 64-bit double precision engine, as there are some known problems with it in X3c.
 
Other than that, possibly some errant plugin is causing trouble. Try saving a copy of the project with half the tracks removed, and keep alternating and removing another half of the tracks until the project bounces correctly. That might identify the culprit. Alternatively, you can load the project in Safe mode, and only load half the plugins each time (focusing on 3rd-party, non-bundled stuff), then half of the problematic half, etc.
 
 
 

Try to get rid of the 32-bit plugins. I had a X3c project, where the audio channels of BFD2 were completely f'ed up (producing spontaneous pops etc.), whenever a random synth on another track had been "frozen" to audio. Very stange behaviour, and it is difficult to imagine how this could even interfere, but nevertheless - it happened, and it was caused by 32-bit effect plugins, that normally work perfectly in 64-bit Sonar.
It was so weird that I did not even bother to contact support; I simply decided to sort out my last 32-bit effects.
I'd say that "bridging" while working well most of the time, means actually asking for unpredictable problems which are also very hard to track down (as there is no obvious connection).
 
Georg
 
 

 

chrisbates
I am using some 32 bit plugins and my version of X2 is 64 bit, but they work during playback, so why wouldn't they work during mixdown or export.

It's not uncommon for plugins to have trouble with offline bounce which is probably why Cakewalk Tech recommend trying real-time bounce.
 
If you're running a very small buffer, like 2ms or less, try going back to fast bounce and using a larger buffer size; If that works, you can increase bouncebuffsizemsec=0 in AUD.INI to something higher. Zero means SONAR defaults to using your real-time buffer size for offline bouncing.  Some plugs have trouble doing a fast bounce with a small buffer. I found this when Rapture had a problem bouncing at anything less than 4ms. I've had bouncebuffsizemsec set to 20 through several versions now.