dropouts (just started)

The first thing to do is install latency monitor by resplendence and see if it says your PC is ok.
 
http://www.resplendence.com/latencymon
 
 

Muted tracks still must be processed. Try archiving unused tracks. Freezing active tracks is another way to free up resources. By-passing an FX bin (right-click in the FX bin for the option) will remove FX rack from processing. The FX button in Mix module, shortcut E will by-pass all FX bins. Disconnecting synths will unload them from memory. The connections are maintained in the synth tab menu when the browser is docked. When the synth rack is undocked, each synth has a power button to (dis)connect synths.

In order for the mute function to be available while the transport is running.

Anderton

ChewingAluminumFoil
Sometimes you just have to reboot I guess. 

I've found re-booting a panacea for a lot of ills with various programs. I think sometimes Windows just gets overloaded with stuff and needs a vacation. Fortunately since computers think in nanoseconds, a re-boot would be like six weeks off for humans 

 

Craig - I have done a human reboot, and I've even swapped out some of my aging components, yet I STILL can't solve some nagging audio issues - meaning every time my ex calls, I hear nagging audio, and that's an issue.  hee hee
 
I DO agree that sometimes it just helps things in Windows to do a reboot - though I have no detailed information on exactly WHY that seems to be the case.  I often choose to do so before starting an anticipated lengthy or complex Sonar session.  I think some of that is sort of a long breath for myself too, while waiting for the computer to restart.
 
@chewingaluminumfoil - you might consider adjusting some of the Sonar buffers in Preferences.  I have adjusted mine as follows: Preferences>MIDI>Playback and Recording - Prepare Using nnn Millisecond Buffers - that is adjusted upwards to 500, and Preferences>Audio>Sync and Caching - under File System I have both the Playback I/O and Recording I/O buffer sizes adjusted upwards to 512 kilobytes.
 
In addition, some plugins are not meant to be used during recording, but instead are meant for use during mixing, so you will want to make sure that any plugin you have in place during recording isn't going to cause issues with audio when the ASIO Buffer Size is set to a smaller size for low latency when tracking.  Plugins that either chew up CPU or use Look-Ahead Processing should either be temporarily bypassed during recording, or even swapped out for less consumptive plugins - and then when you have moved on to mixing you can put those more resource-intensive plugins back in, because they work fine when the ASIO Buffer Size is set to a very large value, and when mixing you no longer need to worry about low latency, since you aren't trying to record at that polnt.
 
Bob Bone

Been awhile but I think you run V Vocal, fix the track and then bounce it. 
Especially back in X1 days V  vocal was a buggy app and many a post could be found complaining. 

after updates, or before starting a project, i reboot my system. this resets the memory pools and services. many many applications, services, etc can leave holes in memory resulting in fragmented memory locations, pointers to bad memory space, etc which can disrupt the operations. very often you see this in Java where the garbage collection is trying to catch up and/or developers went around the JVM to directly access objects leaving holes etc. if you have SSD drives, the boot process could be under a minute and you will find much more happiness...

One last question for you folks.  Do any of you recall how V-Vocal edits were stored?  Like I said, SONAR seems to find the rendered V-Vocal clips but not the source edits.  I hear the pitch correction happening until I open the clip, and then I'm presented with a clip with no edits and no audible correction.
 
If these are in separate files with vaguely human-readable names I'd like to go see if I can help SONAR get sane again.  Or is stuff also stored in the project file? 
 
It's pretty messed up. What do I have to lose?
 
CAF

ChewingAluminumFoil
One last question for you folks.  Do any of you recall how V-Vocal edits were stored?  Like I said, SONAR seems to find the rendered V-Vocal clips but not the source edits.  I hear the pitch correction happening until I open the clip, and then I'm presented with a clip with no edits and no audible correction.
 
If these are in separate files with vaguely human-readable names I'd like to go see if I can help SONAR get sane again.  Or is stuff also stored in the project file? 
 
It's pretty messed up. What do I have to lose?
 
CAF

i had a quick google and couldn't find an answer, and don't have it installed but if you make a minimal test project, do the vvocal thing, save & exit, then examine the output, cwp, audio folder etc, any extra files in there? vv may also be saving its data somewhere other than the cw project folders
good luck!

i think sysinternals includes a file/hd monitor also
 
but maybe someone from cakewalk could save all the investigation work and just tell us!!