I reinstalled Sonar X3 and noticed the synths go silent when reloading a project that contains even ONE synth track.
 
I did a loosely-targeted Google search and stumbled upon a Troubleshooting page for no sound. One of the solutions was to check the Audio Engine button.
 
It seems as though the Audio Engine button is turning off every time I exit the project!
I Googled this as well, and found the following link. Please let me know what you make of this:
 
http://forum.cakewalk.com/Audio-Engine-turns-off-m2441661.aspx
 
When I installed for the first time, I had to minimize the latency because notes were being delayed and I'm not using an external interface. Right now, my buffer size is minimized (Audio -> Driver Settings -> Mixing Latency). In MIDI -> Playback/Recording, playback is set to 200-millisecond buffers.
 
I believe this is the solution. Now to figure out where these levels should be...

Here is some text you posted above: "I assigned the TTS-1 Output track to the correct input. The meter lit up, but I heard no sound, even after selecting another instrument through the Mixer and the Patch button."
 
Please explain EXACTLY what you set the TTS-1 Output Track (the audio track labelled TTS-1 Output) to, AND also please DETAIL exactly what steps you took to attempt to get it to play sounds.  (how did you try to trigger sounds on TTS-1, was the midi input echo on button for the correct midi channel lit? etc).  Be specific, because something you are/aren't doing is making it work for me and not for you, or your system has a problem.
 
Bob Bone
 

robert_e_bone
Here is some text you posted above: "I assigned the TTS-1 Output track to the correct input. The meter lit up, but I heard no sound, even after selecting another instrument through the Mixer and the Patch button."
 
Please explain EXACTLY what you set the TTS-1 Output Track (the audio track labelled TTS-1 Output) to, AND also please DETAIL exactly what steps you took to attempt to get it to play sounds.  (how did you try to trigger sounds on TTS-1, was the midi input echo on button for the correct midi channel lit? etc).  Be specific, because something you are/aren't doing is making it work for me and not for you, or your system has a problem.
 
Bob Bone

TTS Output track is set to "TTS Output 1 Stereo" as you suggested. The meter would light up, but so sound is heard. The Input Thru button is always lit. I would try to trigger sounds through PRV or through the Mixer.
 
HOWEVER -- as Post #11 suggests, I believe I've narrowed the problem down to the Audio Engine button. It's totally consistent with the issue.
 
The Audio Engine button turns off when I close/open the application.
The Audio Engine button remains on while remaining IN the app, closing and reloading the project.

You see how much time people waste when there is no audio interface involved! I'm afraid Sonar just plain don't cooperate if you do not use a proper audio interface with good drivers. 

All the work above is unnecessary with no audio interface that Sonar needs to provide decent performance its a waste of time trying to troubleshoot this. 

Are you saying that there's no way to keep the Audio Engine button from turning off on exit because I've minimized the latency (to prevent notes delaying/dropping) and I have no external audio device (suggested, but not required)?
 
I refuse to believe that Sonar is that restrictive to allow me to adjust latency/buffers and turn off my Audio Engine button every time I close the application. I was able to adjust the latency the same way in MC6 and still do my work without note-dropping and the audio engine shutting off on me.
 
Unless there's an entirely different reason why the Audio Engine button disables when the application is closed and reopened.
 
Granted, I'm still learning, I'm just merely stating my observations. :)

Sonar is a pro quality DAW and to do its best it needs a pro quality audio interface. In a pinch with a laptop and on the go it has been done when people use the audio chip on the motherboard to do some simple editing. For working with low latency audio you need to add a good audio interface that has solid drivers.
 
You may not think this is so but it is. No DAW will perform at its best hampered by inadequate audio. Keep in mind that the audio chip that comes on the motherboard is meant for media playback where latency is unimportant. 
 
A DAW lives or dies on latency. 
 
If you ask around you will get the same answer from anyone that understands digital audio. 
 
 
 
 

The audio engine shuts off if excessive demands are being made on it. This can be latency, conflicting processes within the computer, project complexity, all of the above, etc. Standard Windows drivers and an on-board sound chip were NEVER designed for pro-level audio tasks.
 
Here's a simple test. Change Sonar's audio latency to something really big, like 200 milliseconds. If the audio engine doesn't drop out, it's almost certainly a sound chip/drivers issue although it could be other conflicts as well.

My favorite explanation is -$400 Audio software doesn't run on a $10 Audio chip. 
Your audio interface is the heart of all computer recording systems.
You buy the interface before you buy the software. 

Cactus Music

You buy the interface before you buy the software. 

I didn't know this in '96!

I found out real quick. 😊😊