There is one case that's been noted periodically where Sonar's audio engine doesn't work the way some/many/I'd expect it to:
Say you have a project with midi tracks only... no audio... no soft synths/plugins.
For this project, you want to use Sonar's midi sequencer to sequence external hardware.
You also want to input monitor the hardware while playing/editing the midi.
So... you have your midi tracks, and your routing is all ready to go... hit play and hear: nothing. The midi is going, but the audio engine light goes off.
Like CJ said, the audio engine will disingage, because it thinks there isn't anything to play.
The first few times this happened to me, I thought it was a bug, and I still think it's an oddity (to me, input monitoring counts as audio in a project).
But, for one reason or another, this is not how Sonar works.
However, there's an EASY cure!!!
ANY audio within a project, or a virtual instrument, will cause the audio engine to stay engaged.
All you need to do is one of the following, and it will work as expected:
- engage the audio metronome... if you don't want to use it, turn the volume all the way down... it'll still keep the audio engine going.
- insert a soft synth to the synth rack... again, you don't have to actually play it... it just has to be there.
- hardware monitor/director monitor (this is what I do now)
There might be something else, but I can't remember.
This comes up periodically, and if you're trying to do something similar to the above project, give one of these a try.
Take care,
- zevo