Hi Everyone,
 
I am using SONAR 7 producer edition.
 
I can't play my project with vst plugins or any kind of audio fx, even with only two tracks recorded and just only two vst (for example guitar rig 5 or even just one audio fx like a compressor!!!!!).
It's strange because I can record and play it the first time I work to a new project, but when i come back to it, after saving and closing it, Sonar is enable to play it and event to export audio.
 
I don't know which is the problem.
 
I use a DELL precision with:
WINDOWS 7
RAM: 8 gb (it's not a problem of memory)
INTEL quad core I7
 
Could anyone help me? Please, I am getting crazy...
 
 
 

Are you saying the FX aren't in the signal path?
Have you bypassed all FX? The letter E will bypass all FX. Also the button FX in the control bar will bypass all FX.
 
Or are you saying you are getting dropouts where audio stops?
Try increasing the Sample Buffer in Preferences > Driver Settings > Asio Panel...
If you are not using the ASIO driver style you should seriously consider it.

Thanks for the reply.
 
I don't have any dropout, only i can't play my project if i have inserted some audio fx in my tracks.
So any drop out, the fx are in the signal path, the sample buffer are setting with a value of 133 as default in 44100 hz both 16 and 24 bit. If i would increse them, the problem remains.
 
The strange thing is that all works the first time i work on a new project....
 
 

I don't know...bypassing FX i can play the project or export it....in another case, i can do nothing....

hmmm puzzle.
 
http://www.resplendence.com/latencymon
 
Try this tool. Let's make sure your computer is up to the job. Please run this for several minutes and post the results to this thread so I can see what's going on.

ops....it has not passed the test i think...
 
this is the message:
Your system seems to have difficulty handling real-time audio and other tasks. You may experience drop outs, clicks or pops due to buffer underruns. One or more DPC routines that belong to a driver running in your system appear to be executing for too long. At least one detected problem appears to be network related. In case you are using a WLAN adapter, try disabling it to get better results. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates.
LatencyMon has been analyzing your system for  0:12:53  (h:mm:ss) on all processors. 
 
 CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed:                                   2195,0 MHz
Measured CPU speed:                                   209,0 MHz (approx.)
 
MEASURED INTERRUPT TO USER PROCESS LATENCIES _________________________________________________________________________________________________________ Highest measured interrupt to process latency (µs):   1317,862329 Average measured interrupt to process latency (µs):   11,052126
Highest measured interrupt to DPC latency (µs):       1264,214836 Average measured interrupt to DPC latency (µs):       2,149021
_________________________________________________________________________________________________________  REPORTED ISRs _________________________________________________________________________________________________________ Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.
Highest ISR routine execution time (µs):              117,682460 Driver with highest ISR routine execution time:       i8042prt.sys - Driver della porta i8042, Microsoft Corporation
Highest reported total ISR routine time (%):          0,074392 Driver with highest ISR total time:                   i8042prt.sys - Driver della porta i8042, Microsoft Corporation
Total time spent in ISRs (%)                          0,084238
ISR count (execution time <250 µs):                   454769 ISR count (execution time 250-500 µs):                0 ISR count (execution time 500-999 µs):                0 ISR count (execution time 1000-1999 µs):              0 ISR count (execution time 2000-3999 µs):              0 ISR count (execution time >=4000 µs):                 0
_________________________________________________________________________________________________________ REPORTED DPCs _________________________________________________________________________________________________________ DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.
Highest DPC routine execution time (µs):              1373,692027 Driver with highest DPC routine execution time:       ndis.sys - Driver NDIS 6.20, Microsoft Corporation
Highest reported total DPC routine time (%):          0,042015 Driver with highest DPC total execution time:         ndis.sys - Driver NDIS 6.20, Microsoft Corporation
Total time spent in DPCs (%)                          0,136194
DPC count (execution time <250 µs):                   1238921 DPC count (execution time 250-500 µs):                0 DPC count (execution time 500-999 µs):                4943 DPC count (execution time 1000-1999 µs):              11 DPC count (execution time 2000-3999 µs):              0 DPC count (execution time >=4000 µs):                 0
_________________________________________________________________________________________________________  REPORTED HARD PAGEFAULTS _________________________________________________________________________________________________________ Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.
NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.
Process with highest pagefault count:                 iexplore.exe
Total number of hard pagefaults                       2691 Hard pagefault count of hardest hit process:          2180 Highest hard pagefault resolution time (µs):          393512,499317 Total time spent in hard pagefaults (%):              0,311916 Number of processes hit:                              13
 
 

Here is another tool that may help, which I posted in another thread (http://forum.cakewalk.com/FindPost/2909231 ).
 
From your diagnostic report, you must have a LOT of threads running on your machine, which is common with a machine built by Dell, HP, etc.
 
The thread above will help with updating drivers, which I would recommend first.
 
From there, you will want to close down applications when you are doing DAW work, especially ones that do not contribute to recording. Just about any program you ever install "launches on boot" unless you tell it not to ( if you "Run" msconfig, you can see all of these on the "Startup" tab). I would hold off on this for now and update drivers first.

thank you so much.....i will try all your suggestions.....and i will come back for any problem....
 
Thanks again!!

Keep using latency monitor as your "guide" as you go, and pay attention to the processes tab in that. One thing that stuck out big in your report post was "Process with highest pagefault count: iexplore.exe" Internet Explorer is a prime example of a process you want to shut down when you are using your DAW. Basically any process that is not needed when you are recording should be stopped.
 
If there is an updated driver for "i8042prt.sys" that will help you as well (this one hit your report in a couple places).

Gosh - looks like my laptop, it has a Core i3 in it; the ndis, i8042prt (ps/2 driver), and Intel AHCI (SATA) driver all go boom. DPC looks good most of the time, it's the interrupt to DPC start time that seems to be the issue.
 
There's certainly a lot for me to look into, but I'm not in a rush. I normally work on my desktop. I plan on using the laptop for tracking, where I can used a bounced rhythm mix as a backdrop for recording vocals, which will keep processing to a minimum. My Motu interface has a built in mixer with monitor FX, another great help.
Once done, I copy the recorded tracks back into desktop project. Will be using Gobbler to stash things in the cloud.