brundlefly
Hey Susan, I think those that hear output must be direct-monitoring their synths.
 
I verified SONAR is sending MIDI, and the synth is responding, but the audio track that's echoing the input is being temporarily Archived along with all other tracks in the project.
 
This makes some sense, as you wouldn't want to hear everything else playing during quantize audition, but SONAR doesn't "know" that the audio track is hosting the instrument being driven by the MIDI, where as it does "know" that when using a soft synth.
 
Since it's using the Archive function, I don't see any way around this other than direct-monitoring.
 
Dave
 
 

Hi Dave-
 
DM occurred to me after I'd shut down for the night and I bet you're right. I'll try it next chance. 
 
Thanks!
 
-Susan

brundlefly
Hey, Tom, did you see my previous post? Are you direct-monitoring? I think that's the only way you could possibly be hearing the audition given that SONAR is Archiving all tracks other than the auditioned MIDI track. Audition length is not going to affect that.

 
I'm not sure I understand, but like the OP, I'm using a hardware synth.  The audio from that synth goes directly to my speakers (not back into SONAR).
 
If I'm mis-understanding, how would I check if I am "direct-monitoring" ?

Yes, direct to speakers is direct monitoring as opposed to having the audio output routed to your audio interface and input-monitored (a.k.a. input-echoed) through an audio track in SONAR. The latter allows you to monitor with real-time FX added among other things. Not to mention, you would need the signal going into SONAR at some point in order to be able to record the audio.

I use hardware synths that audition ok. I do use direct monitoring. I'm wondering why someone wouldn't direct monitor in that case?
 
Feeding it back into an audio track and monitoring via input echo seems a strange way to set up to me. Unless I am missing something?

I've always input-monitored my hardware synths since PC's became capable of delivering decent audio latency. As per my previous post, this lets you monitor with VST FX among other things.
 
And in order to be able to both direct-monitor and record, you either need to be using the DM facility of your interface/virtual mixer, or physically splitting the output signal between your interface and your monitoring system with an external mixer or by some other physical means, right? Since SONAR doesn't support ASIO Direct Monitoring (i.e. automatically switching the interface mode for you when you enable input-monitoring in the DAW), this means that changing routing or monitoring modes requires some button pushing outside of SONAR.

Ah got ya'. I use an external FW mixer so monitoring isn't an issue. I tend to use the FX section on the synth so no need for that either. I don't think I've ever put an audio track in for it until record time.

FastBikerBoy
Feeding it back into an audio track and monitoring via input echo seems a strange way to set up to me. Unless I am missing something?

Using Sonar's input echo means you can run fx plugins on the synth and hear their effect while programming/playing/tracking the synth. If, for example, you build up layers using a lot of delays, input echo is pretty much essential (unkess you've got 30 rack spaces of delays of course).

I've used it ever since I could get a low enough round-trip latency for input echo to work comfortably.