Thanks for the input jpetersen!  I have been using Adobe Premiere Pro, Camtasia 9, Melodyne Studio,  and haven't had any probs.  (see my above post).  Sibelius has been quirky though (it won't rewire with Sonar), and it runs ASIO, so, maybe related.  Though it seems others have had Sibelius and Sonar rewire issues too,  so maybe unrelated.
Thanks again!!
Bob E
 
 

Wow these are indeed surprising and not typical.  Sorry you are running into these issues.
 
We'll audit the record path to be sure any error conditions that might result in no clip pop an alert so one can know what's going wrong.  A silent fail isn't helpful. 
 
As far as this latest issue, it appears a dropout is occurring for some reason at that particular segment of audio.  Can you send us a bundle file of that project so we can check it out?
 
I'll also contact you privately with some more details.
 
Keith
 
 

Here is a clip that may have more insight into this problem.  The audio clip isn't in sync with the waveform picture, and there's some weird jibberish at the end of the drawings, however, there is no sound there.  Sorry for the vids, but each time I have an issue, I want to document it, so I can explain and demonstrate the issue. 
I have fast hard drives, and I have also tried moving my picture cache folder to a separate drive.  And cleared it out.
 
Is Sonar having issues with the video rendering, or graphics card?   I have an NVidia Geforce GTX 970 and no problems with it.  (I don't play games with this computer)
Any ideas?   Getting desperate here, and waiting, and waiting for a response from tech support.
Maybe this vid, (or the others I posted earlier) can shed some light??
https://youtu.be/JRUVNg18ekY
 
Thanks,
Bob E

This looks strange to me:
 

 
"M:\_myCakwalk Groove Clips plus" is your WAV file location ?!!!??
 
EDIT: OK, I realize that per-project audio folders probably make this redundant... but still, it stands out to me as something abnormal.

Hey Bob I've been watching your videos and things sure do seem screwed up. I guess the good news is that Keith is across it. Hang in there man!

any clues in windows event log? small empty files sound like a file-write issue

Hi Chuck,  that last video regarding the 4kb files is me trying to troubleshoot my issues.  Here is my main issue with the disappearing record takes.  This is another video recorded on 10/16. 
https://www.dropbox.com/s/g9hx4xskttgj45f/sonar_open_save_record_issue.mp4?dl=0
 
This was done with in the new 09/2017 version on the same evening as the excerpt from the vid you saw.
This shows vanishing record takes. 
My other issue, which seems related, has to do with clips that will not play. (see previous video links).  My song will play until it comes to one of these problem clips.  If I move the clip downstream, the file plays until just before this 'rogue' clip.  If I place the playhead after this clip, the file plays.  If I place the playhead on the clip, the file will not play at all.  
 
If I go into windows explorer, this wav file plays fine, using WMP,  or Transcribe.  So that tells me it isn't corrupt.
These recorded 'rogue clips' are not unique to just one file,  but happen seeming random in other projects.
Though it's always after some minor editing, such as cut, copy, pasting, and bouncing etc...
 
Thanks,
Bob E

Keith Albright [Cakewalk]
Also since you are getting storage(disk) related issues, I'd run a system diagnostic to check things out.  If it's a custom built PC, might not hurt to power down and while grounded, reseat the cables between the drives and the motherboard.

Hey Keith - great to see you here. Could "storage related issues" also involve RAM, or would it always be a hard disk?

Thanks Keith,  that is strange, however, i have never worked a project from my desktop.
One thing that I may do, is open Sonar and record ideas without first saving to a named project folder.  My assumption is that Sonar writes the audio to the folder within the Cakewalk projects main folder.  (in my case, D:\calkwalk projects\Audio Data).
Then if the project is worth saving,  I save and name, and I believe the tracks are then moved or copied into the newly named project files 'Audio' folder.
 
What I also noticed, is that in my "D:\Calkwalk Projects" folder I have an 'Audio Data' folder, and an 'Audio' folder.  For instance,  I have a file named 'Track 5 (Bounced, 215)' in both these folders. (same date and size).
In my Audio Data folder I have 342 files, 59 of which are 4kb empty wave files.  In my Audio folder within the root Cakewalk Projects, there are 11 total files.
I suspect that these things are normal and probably not the issues, but figured I would add this info.
 
I'm not sure about CWBRN #s.   It would be good if I can get you another so we can compare.  Is there a way for me to get those report numbers from my system?
 
Most if my issues don't seem to crash the program, but, as we've seen, cause weird issues recording, (and playback).
 
Other observations I have to tell you.
I did record and edit last night, for about 3 or 4 hours. Man, I absolutely LOVE Sonar and it's creative, visual and intuitive workflow!   During this recording project, after various takes and edits,  I had 3 situations where the recording did not stick. In each case, I had to close the file and reopen it.  Then the recording would 'stick' and I could continue on. 
 
When I reopened the project the 3rd time,  the file would not play and I had the audio engine dropout message issues. I closed it and reopened it, still not able to play.  I then closed Sonar, and turned off, (and back on) my Motu Ultralite interface.  I then reopened Sonar and the project played fine. 
 
The thing I also noticed, and this seems very strange, is that when I looked at my Motu after this problem,  while going to reset it, the front screen said 44bit.  My projects are always recorded using 48bit and I am sure when I began the recordings, that the Motu was set at 48.
I reset it back to 48, (after turning it off and on again), and then, as I mentioned, the project played fine.  I don't use the Motu for windows playback or any other programs while Sonar is open. 
It seems, maybe, that Sonar is having write issues communicating with the Motu drivers?
Al is working fine, and something, or some action, corrupts the audio driver during record, editing or playback?
Is there something that would cause Sonar to 'change' the Motu from 48bit, to 44bit? 
This is the only time I noticed this, and it could be that the Motu drivers got corrupted and set itself to 44.   (my motu 'audio console' software is always set to 48, but in this instance, it was reset to 44, hmm)
 
My Motu drivers are as current as they can be.  Not having issues with other recording/playback software using this interface.  I will also do a system check on cables and connections also, as you mentioned. 
 
Please don't feel you need to answer all these questions Keith!  I realize I'm writing a novel here.  I'm just trying to give you as much info as possible, and maybe something 'pops' out.
Thank you so much for helping resolve this!
Bob E

First I want to thank everyone who tried to help. In particular,  Keith Albright, who was absolutely awesome! Going above and beyond to help me find a solution!  Thank you Keith!!!
Although this thread was last updated a few weeks ago,  Keith was in contact with me throughout.  Lots of help behind the scenes!
 
Ok, so anyone who saw any of the videos I upload with the 'audio dropouts',  the 'vanishing record takes',  Sonar closing prematurely, without warning.... crazy stuff huh?! 
I am absolutely certain that it was Plugin Alliance plugins. Though, I was only using 1 while testing, (so that I could get a sound), it was enough to cause these issues. I'm quite sure I ran a test without any plugins at all at one point, and still had an issue, but it was probably after a running a previous project that had a PA plugin. In which case, after these issues, I would have had to reboot, and probably didn't.  I truly did not expect this plugin would have been causing these issues.
 
So, here's the story:
I had been going close to insane with these 'mystery' errors and issues and realized I had to get on with recording, so I went and got an ilok3 and downloaded and installed Pro Tools 12.  Reluctantly.
So, I go and start recording with PT, and wouldn't you know it,  AAE (Avid Audio Engine) dropouts, after a bit of time.  And, then, after an audio dropout, I record, and I get the 'vanishing' clip thing. WTFFFFF  I'm thinking???   So, I think, HD, SSD drive??  I've already gone through all that stuff. And I have a powerful, stable, system.
       I go on line and I visit Pro Tools forums and I discover after googling "AAE error 6 was encountered" that other PT users that had this error, were using Plugin Alliance, Brainworx plugins. (AAX); and many said that after removing the PA plugins, their errors went away.
 
These projects I have been testing in Sonar have had one common variable.  A plug-in called Bx_MegaDual  guitar amp simulator plugin.  (an awesome repro of a Mesa Dual Rectifier, by the way)
 
Turns out, on the PA website, in their known issues section, they mention their Pro Tools' AAX plugins could be causing 'AAE error 6 was encountered' errors. (which of course, stops the playback engine)
No mention of VST2 or VST3.
That got me wondering...
So I load up Sonar, and add a handful of other plugins, TH3, BT, Isotope, etc.  but zero Plugin Alliance, and wouldn't you know....
I couldn't get Sonar to even hiccup.  Sonar ran beautifully smoothly.. no problems saving files, or any of these issues I was having.
I have like 25 of their plugins, so I was pretty bummed.  But, having gone to their website only days ago and seeing nothing about updates, did I discover this morning that they had added updates to most every plugin!  They must have fixed this issue and released the fixes in the last few days.
If you look at item 13 in the screenshot below, you will see it mentions Sonar.  It mentions quite a few other DAWS too.  Something went pretty wrong here!
    Brainworx, and Plugin-Alliance plugins are truly awesome.  Something glitched here, maybe Window updates.. who knows.  But, for me, updating all these plugins did the trick.

I tried out a handful of these new PA versions and Sonar works perfectly with them now. Even the projects that i couldn't use work again now, perfectly.   I am so happy to have this resolved, (again, my apologies, thinking it was Sonar).  These issues have lasted for me since last May and have dogged me since.  Now I feel quite confident that I can get back to making and recording music again!!
 
I think I will update to Sonar 10/2017 later this week.
 
Thank you!
Bob E
 
" />

Congrats for getting the problem solved and posting what was causing this!

Not sure if I am able to put [Solved] in the thread title.  I thought I did, but it was only on the individual post.
I can't seem to find a way to add to the thread title.
 

Great news!