That_Guy

For the next person W/ multicore DAW and having issues, who stubles across this post... I hope this info help you on your journey. LatencyMon reveals: " DCP Routines that belong to a driver running in your system appear to be exciting too long." It has execution times that spiked while scanning USB, But the failure got a lot worse when scanning ntoskrnl .exe Motherboard is a KGPE - D16 and has the latest bios and firmware. However, I just saw it has SATA 2 and USB 2 slots. I suspect the plugins were trying to move atleast 200-300Mb/s of data, But the SATA 2 hard drives peak at 300mb/s max, under best circumstances. USB2 Peaks @ 480Mb/s under best circumstances. But the data was getting pulled from Multiple USB drives on Multiple hubs and SATA 2 drives... = Epic Fail. Of course the CPUS would spike... = Audio drop out. Rather than accept a sinking feeling in my guts that I need to spend a few thousand on a new DAW... Im going to buy a SATA 3 PCIe card (Doubles speed of current hard drives) and a USB 3 PCI card (10x faster than USB2) to upgrade data transit speeds, try to cut ALL usb hubs out by investing in a "big" drive, instead of multiple USB driver... grab a little bit more bandwidth. I also hope to be able to record 4-6 live VST tracks as I write/record, then render/freeze them as I stack tracks? Also just remember: Driver updates are our friends.

I have a dual socket, AMD Opteron 6274, 32 core system running at 2.20Ghz 56 Gigs of memory. *8Gb dedicated to each processor = 40Gb usable. 512GB SSD "C" drive Sometimes Plugins have been installed on "C" drive, other times installed on other SSD Drives to prevent bottle necks. I've tried all the tricks here. + Multiple sound cards/Multiple driver configs +Multiple soundcards in multiple re-installs of windows. With and without updates. Audio drop out happens when I try play back of: 2 midi tracks, from one instance of: Kontact 6 (In pic) (Also tried Kontakt 7) through 3 "loaded" plug ins using less than 207 Mb of ram. Kontakt has been set to use 1 core -> 16 cores. Nothing resolves this. Does using protools or other software help those of us, with similar issues? I've had this issue for years. Just started recording again. This is unbelievably frustrating.