Hello to everybody
 
Just a few words about my config :
Sonar Producer X3d
VS 700 Console and soundcard
Windows 7 64 bits, i7 970, 12 Gb ram
 
Few days ago, I opened a new project in order to demo the SOUNDTOYS Native effects bundle. The project results to be not heavy, with about 20 tracks (wav recordings, rex loops ...) and about 5 auxiliary sends, testing various combinations... This was OK at the beginning, but, gradually, when I had to reopen this project, it was very slow to start. Once opened, there was a lot of audio engine drop outs but that worked; when I closed it, there was the message saying that Sonar has stopped to work... And finally, when this project opens, whereas all my routing configuration is correct, I have no playback sound (either without sound indicators in the Vu meter of the tracks and busses as if the tracks were empty, or with signals).Now, THE WORSE  is once the project is closed, my system is disturbed and when I open any sonar X3 project, I have the following message :
 
There are no audio devices for your current driver model on your system. Please go to options/audio and choose a different driver model. But I have absolutely no option to select anything. when I click on drivers there are none to select. 
So I have to restart the VS 700 console and soundcard, but some times, the resut is the same and I have to restart  the computer and the VS700 : very annoying ! (NO problem with the other projects !)
 
Would you have any idea ? Maybe I suspect the Soundtoys plug-ins as they are a little bit cpu consuming in comparison with other plugins, but my processor had leeway. What I don't understand is that at the beginning, things were OK, and it gradually worsens; there were essentially Soundtoys , Waves and Lexicon plugins but I'm very careful and when I don't use a track with plugins inserted, I deactivate them ! Maybe I tell nonsense but the delay calculation for the Soundtoys delay plugins has generated some disturbance in Sonar (??) But the fact that this project causes lost of my audio drivers gives me cause for concern because If it was a serious project, I would lost all my datas !
 
THANK you very much for your attention and will apreciate all your advices !
 
Pierre

Sounds like a memory leak. Watch SONARPDR.exe's RAM usage on the Processes tab in Task Manager and see if it continues to climb steadily over time with this project open.

Thanks a lot brundlefly !
I 'm not very acquainted concerning computer specifications, but it is surprising that only about 20 audio tracks (no Virtual synth...)  push my ram to the limit, with only some plugins. I had "heavier"projects and it was ok (??). Anyway, I will take a look at what you mentioned. Thanks again

Hey brundlefly,
I just checked out the number of the SONARPDR.exe and it moves around 2 876 35... and more; and just at the left,there are 2 numbers which increase and decrease from 0 to 37 or more ... ??
Is it normal or not ? What's wrong  and what to do ?

There are no audio devices for your current driver model on your system. Please go to options/audio and choose a different driver model. But I have absolutely no option to select anything. when I click on drivers there are none to select.
So I have to restart the VS 700 console and soundcard, but some times, the resut is the same and I have to restart the computer and the VS700 : very annoying ! (NO problem with the other projects !)

do you have your internal sound card disabled? I would disable it and make sure Sonar doesnt see it. This can cause what you are seeing.
 

Once opened, there was a lot of audio engine drop outs but that worked; when I closed it, there was the message saying that Sonar has stopped to work...

The new FX you inserted and are demoing may need more CPU, so you will need to raise your ASIO buffers or WDM slider. Some plugins FX need more resources than others and depending on your sound card driver settings, you may need to adjust it.
 
CJ

I have had my MOTU drivers spontaneously delete themselves from my system, when this happens I have this same error.  A reinstall of the MOTU drivers solves the problem in my situation.
 

Thanks very much for your help, highly appreciated !!
Cjays, thanks for the advices, but everything was ok (internal sound card disabled).
Phonic, maybe a reinstall could be the solution, but I don't explain why this is this particular project which is failing (??). 
Brundlefly spoke about the memory in the task manager, but I don't know if the numbers I noticed show something wrong ?

You may have to disable your input and output audio devices in order to change driver mode to ASIO and see devices to enable.  
 
The following only deals with any high latency issues, where you have dropouts and crackles and such.
 
For general starting point settings, I usually recommend:
 
Audio interface: Sample Rate of either 44.1 k or 48 k, ASIO Buffer Size of 128
 
Sonar: Driver Mode of ASIO, Sample Rate must match whatever is set for audio interface, Record Bit-Depth of 24 bits.
 
Try to get your Sonar-reported Total Roundtrip Latency to about 10 milliseconds or just a little less.  If needed, you could also adjust your Record I/O Buffer Size and Playback I/O Buffer Size to somewhere around 500 k, but start with the other above settings first and see how they work for you.
 
If not already running as above, give these settings a shot, and please post back on the results.
 
Also, keep in mind that some effects are meant for mixing/mastering and not for tracking, and some of these can add a great deal of latency.  You can quickly check this by hitting 'E' on your computer keyboard, to toggle on/off 'Bypass All Effects'.  If the latency goes away when you bypass your effects, then one or more of them are likely jacking up your latency, through the use of look-ahead processing or high CPU consumption.  (when done checking this, hit 'E' again to turn the effects back on).
 
I hope any of the above helps, 
 
Bob Bone
 
 

The Task Manager numbers are fine (37% CPU and 2.8GB RAM) so long as that RAM number isn't continually increasing or approaching the limit of what's available.

Go into Windows' Sound and Audio Devices control panel applet and see if Windows can see any audio devices. If not, verify that the Windows Audio service is running. If it isn't, try to start it. If it fails to start, check the event log to see why. If it's already running, check Device Manager and look for exclamation marks next to USB ports indicating a problem with the port, and verify that the audio interface's driver is installed and functional. It should be listed under "sound, video and game controllers". If it's not there or has an exclamation mark beside it, try uninstalling and re-installing the interface drivers.
 
Bottom line is that SONAR cannot list any devices that Windows hasn't told it about. Windows has to recognize the device first.