robert_e_bone
I happen to also run as Bitflipper has indicated above...
 

 
That's the other Dave whose username starts with a 'B'. 

brundlefly

dcumpian
This does sound like some other app (or Windows) stealing the audio interface outputs out from under Sonar. When you are working in Sonar, you should turn off all Windows sounds and be aware that switching to audio in your browser or WMP/iTunes and the like can change the bit rate/depth of the interface in a way that Sonar can't take it back. Usually, resetting the interface will solve the problem.

 
This is why - somewhat contrary to popular DAW opinion - I recommend keeping your onboard WDM audio device enabled and set is as the default record/playback device for Windows, reserving your "real" (preferably ASIO) audio driver and interface for SONAR. This ensures that Windows and generic multimedia apps keep their mitts off your audio interface.
 
 

Absolutely...
 
Dan
 

Hi everyone and thanks all for the input. First off:
 
Kperry - I can't hear any of my pre-recorded audio tracks.
 
Zargg71 - preference to share driver with other programs is unchecked
 
Doktor Avalanche - Sonar X3 Studio, still cjecking what aud.ini does
 
dcumpian - have reset the interface many times now without success
 
conradh - Only have one VST at a time - none of them output audio
 
einstein36 - I've just swapped out the Sapphire for a Behringer FCA1616 with exactly the same results, audio out everywhere except Sonar VSTs.
 
brundlefly and robert.e.bone - I hadn't set the windows audio to the internal sound card, but doing so doesn't make any difference - still no VST audio.
 
The key bit of progress seems to be that changing the interface to the Behringer (using first USB and then a Firewire connection) made no difference at all. So I conclude it has to be something to do with Sonar?? 
 
Running out of options now apart from a complete re-install -  - God I hope not....
 

einstein36
Don't feel bad....this is happening to me too....but I have narrowed it down to Saffire's control panel and sample rate...
Both Sonar and Saffire control panel's sample rate are the same, but for some strange reason, it won't play back unless you exit out of sonar, go into saffire control panel, switch sample rate and then back, bam, audio starts working...
I definitely think it's a bug with their driver, control panel, but good luck trying to convince their techsupport of that......
 hope this helps:)

 
I cannot reproduce with a Pro 40 and mix control 3.6.
If you are experiencing this I recomend..
 
1. Uninstall mix control
2. Reboot
3. Install mix control 3.6
4. Reboot
5. Start mix control. Reset the settings and reset the hardware to defaults.
 
Also in windows you should not be using the legacy FireWire driver any more.
Other thing is deleting AUD.INI as previously recommended.
 
If you want to take it even further update your chipset drivers, firmware for FireWire interface and BIOS if applicable.
 
Ta.
 

To the OP another thing you can do is disable your saffire in windows control panel sounds. Just use you internal interface for this. Get a cable from the audio out of your PC and pop it into the saffire.
 
This should resolve any windows conflicts with sample rates etc.

Sounds like a MIDI buffering/rendering issue. Does a synth render properly when frozen/bounced? If so, try raising your MIDI Prepare using buffer to 500 ms if it's not already there, and maybe up to 700 or more if it is.
 
On the output side, I would suggest trying a synth that has internal MIDI patterns or other audition function in its GUI to see if you get output that way- Session Drummer or Addictive Drums, for example.

Yup Brundlefly is right. If it's just VST's his is the most likely scenario.

brundlefly

robert_e_bone
I happen to also run as Bitflipper has indicated above...
 

 
That's the other Dave whose username starts with a 'B'. 

OOPS!!!!! MAJOR apologies in order.  Sorry.
 
Bob Bone
 

Input Echo on ?

Input echo is on !
 
Well another day today, so physically unhooked the lot and ran a couple of virus hunters just in case - which found zilch.
 
Anyway, hooked it all up again and - hey presto it's started to work! I can't believe that simple galvanic isolation of the cables connecting the PC from my studio set up could have affected anything, because the interface worked fine on everything except Sonar - but there it is, it's in service again. 
 
Don't like mysteries, but until it happens again - which no doubt it will, at least I'm enjoying my music instead of screaming at it.
 
Thanks to everyone who took the trouble to respond - much appreciated as always.