Just out of curiosity, I was checking out the OBEDIA video (YouTube) on bouncing down tracks in CbB to an audio file and he says all you have to do is choose Export Audio from the File menu and designate what kind of file you want (MP3, wav etc) and designate where you want it.  If I do that I get an error saying something like "You didn't choose any channel(s) to bounce down".  This isn't a problem, but I'm just curious.  What I have to do is select (highlight) the tracks I want bounced before I go to File and Export.  If I'm just bouncing the whole project I use the old Windows command for Select All, which is Control+A, then File-Export.  I've also been told that all I should have to do (for the whole project) is highlight the Master Buss, then File-Export.  If I do this I get the same error message as above.  What gives here?  Is the OBEDIA guy skipping a step or is there an anomaly in MY setup?
 
Thanks!
John B

• JohnB,

All you have to do is select control all then export the file format of your choice eg wave or mp3 etc.  You can export an entire mix, tracks or clips by selecting the same in the drop down menu. If you don't select all the message will be generated and you won't be able to export.
 
Glenville

Often I simply need to click in any empty space of clip view area and it will auto select all when I expirt.

A long time ago I was told to always use "Select none" before exporting. This has always worked for me 100%. If I miss that step I then might get that warning you got. 
Now that said, "Select all" should always work too. I cannot remember the reason for using select none but because it always works that is what I do.
 
My routine for a perfect export is:
Open the console view playing the song. 
Solo each buss to check all is working. 
I then mute the master to make sure all busses are running through it. 
I go to EDIT- Select none ( you can use the keyboard short cut too) 
File- Save
File export audio
I use what ever the default setting are but will change the bit rate to 16 most times.
I have my file preferances set to open to the location I store my Masters.  

I 've never selected anything when exporting the whole mix. Just routed everything to Master Bus and picked Master as the export source. But I'm on old version, so maybe something has changed?

Kalle Rantaaho
I 've never selected anything when exporting the whole mix. Just routed everything to Master Bus and picked Master as the export source. But I'm on old version, so maybe something has changed?

Isn't every channel routed to the master buss by default?
If so, I wonder why that doesnt't work for me.
 

I also always use Select None before exporting. No idea why that particular command works, but I’ve never had any issues with my exports.

I've had that "no audio selected" thing pop up.  It's a bug of sorts.  Has to do with where your cursor is.  Or something.
 
The bakers should look into this. 

JDNelson
I've had that "no audio selected" thing pop up.  It's a bug of sorts.  Has to do with where your cursor is.  Or something.
 
The bakers should look into this. 

For me, this goes back to Sonar X3 Studio.  It's not new to CbB, so I don't know if the bakers can do anything about it.  It's obviously been a bug since at least X3.
 
JB

The "no audio selected" message happens when a selection is made which contains no tracks capable of rendering audio. IOW a selection of MIDI tracks or clips in MIDI tracks. At least that is how I have managed to get the message.
 
When no tracks are selected, all tracks are rendered to the last bit of data and exported subject to the export preferences. Note this may fail if the project is all MIDI and does not use soft synths because there is nothing to render in the host (IOW, no audio selected).
 
When audio, instrument or related audio+midi tracks are selected (note all cases of tracks capable of generating audio), those tracks are rendered and exported subject to the export preferences.
 
If one can generate a series of steps where selecting tracks that can generate audio causes the "no audio selected" error on export submit it to support so they may review the procedure.