Good morning all. I really appreciate the support from the community here! I managed to make some headway with my system in a very good way but I still don't know what's causing the crashes.
I've rebuilt my template many times to try to fix this; however, this time when I did it I tried something different. Instead of building it in one shot, I built in sections. This took some time.
- I built a template with 1 instance of each plugin (soft synths, effects, etc) the master template uses.
- I reloaded it at least 4 times to see if it would crash.
- I would wait after closing a project until the memory was completely released by the app to the system before loading the next project. It didn't crash.
- Then I would add the rest of the template section by section (winds, brass, synth, etc), saving each iteration as another file name and testing reloading 4 times. Of course, THIS time the full template worked in the end.
What this tells me is that its not directly related to function of a plugin nor the hardware of the system, but some zany combination in the previous projects or with how the plugins interacted with other. What were the updates since the last template build, Play 5->5.0.1 and Sonar's December release. Ok, so its possible they fixed a bug in one of those but I still tend to think its some screwy combination. Still odd that I had this issue with each template build for the last year or so. I just dealt with it at the time but the crashes became more frequent or I just got sick of seeing them.
So the good news I have a known good state that I can archive. If I get crashes in the future I can review what changed between this point in time and then. I also have many different versions of the file which could help in elimination. Glad it didn't come down to hardware device elimination and swapping video cards and usb devices (you'd be amazed at the screwball things I've seen a USB mouse due to a PC). However, I still don't know the cause.
The priority is a bit lower, but soon I will do the reverse with an existing file that has issues. Remove section by section until I get the file to load (saving each revision). If it never loads maybe it was an issue with one of the Play or Kontakt versions. Play 5 is great. but earlier versions were a bit iffy.
@dcumpian @pwalpwal
I know I've taken a seemingly resource inefficient route but I built a system with the power to handle it. I tested the system by taking one of my projects that have the CPU usage at about 90% using 55GB of memory space and let the file run in loops over a weekend. I listed to it for periods of time, and with right buffer, no pops, cracks or skips. I also was able to get excellent performance results with an i5, I just upgraded to the i7 for the really intense projects.
Bouncing to audio is what many due, and your right, a far more stable approach, but as I do mostly orchestral work the stereo field placement building the hall adds to element I need to create the works I make. I'm by no means a professional but I've followed the paths of Mike Verta and Blake Robinson and their templates indeed get this large and MIDI is not always bounced to audio.
I will keep everyone posted, but still encourage anyone with an idea of what would have caused that crash. It's rare that people have a crash without reproducing in safemode or a clear hardware issue, but if you do a modified approach to what I did it might help. And its what pretty much most people here said but mine was just lurking in a darker corner.