Audio Engine Crashes... Get message about potential disk space but that is not it...

I have a Windows 10 machine with an I7 processor and 16GB Ram and when I record more than 2 tracks at once it crashes and says the audio engine has stopped.  It says I may be out of disk space, but I have 1TB Free...  I need to record 10 tracks at once minimum and potentially up to 16 for live band applications.
 
I was able to capture the audio with a program called capture and it did not crash and recorded all 16 tracks.
 
I then imported the tracks to Sonar and the audio engine stopped after 15-20 seconds.
 
I thought it might be my system so I downloaded Presonus One 3 producer for free trial and it imported the 16 tracks and allowed mastering flawlessly. 
 
I have used sonar since the Cakewalk days... the very early cakewalk days and would hate to give up on it, but it was driving me crazy yesterday.
 
Any ideas what to check for?  I was using a digital desk Presonus 16.0.2 to get the audio via firewire to the computer.  Again it all worked flawlessly with One 3.
 
Thanks in advance for your help!

Have you ever run Sonar successfully with your current setup?  What is your setup? (Specifically, the Sonar version and audio interface).
 
What is the exact message you're seeing?  Does it actually say "out of disk space" or is it "out of memory"?

pwalpwal

bpapettas  It says I may be out of disk space, but I have 1TB Free...

Yes, I saw that.  But sometimes people are going from memory when they describe the problem, and get a detail wrong.  I just want to confirm, since the "out of memory" message is very common.

I am running Sonar Platinum and have the Ipswitch build.  I am using a PreSonus 16.0.2 connected via firewire.  I have recorded less tracks at once without a problem.  2-4 tracks.  I needed to record my band live and that is when the audio engine stopped working and gave me the dialogue box that my hard disk "may" be out of hard drive space, but it clearly is not.
 
I tried importing the raw audio tracks since I was able to record those with Capture and it would only play for about 15-20 seconds before doing the same thing.
 
Really frustrated with it.  Other DAW's seem to work fine. 

Don´t want to be rude to the prevoius post,
but an i7 maschine with 16 Gb Ram .. there´s nothing competing internetwise..
 
pull the FW cable, install ASIO4all and run SONAR with it and see if it performs ok.
Then you´ll know where the problem is.
 
FW was never really working well on Windows machines..

I have 2 questions 
Win 10 clean install ?
Do you have a system partition which has less than
20 % disk space ?

Pragi

submarin
 
 
FW was never really working well on Windows machines..

Hello,
that´s not true,
I´m have my Focusrite saffire pro 40 running flawless since 5 years .
There are countless other forum member here running this interface ....
regards
 
 
 

My old Saffire Pro 26IO is coming up to 9 years old without a single problem in that time.
And submarin, please do not suggest installing ASIO4ALL as a solution - it's a band aid at best!

Pragi

submarin
 
 
FW was never really working well on Windows machines..

Hello,
that´s not true,
I´m have my Focusrite saffire pro 40 running flawless since 5 years .
There are countless other forum member here running this interface ....

I have to agree with Pragi.  I've used 3 different FW interfaces in 7 years, and all were rock solid.  I always installed a TI chipset FW card (desktops, of course).  I can see laptop users who buy off the shelf maybe thinking it's a problem.  For them it's always a roll of the dice if you're going to get a decent FW controller.  And if you don't, you can't buy an adapter because it won't fix the problem.

My device works equally well using firewire or USB.

Generally, Asio for all is not a great idea if you can avoid it.

Are you still having the issue?

Have you run Resplendant's latency monitor? Free tool that gives a measure of assurance about your set up.

If you can take the time to call cakewalk support, they might run down the issue faster with you on the phone. It certainly shouldn't be as you describe. None of us would still use Sonar if that were the case for us.

Ok, you tried it, if I could read I'd be dangerous ... :-)

Ran into this issue before. In my case, it was caused by trying to record too many tracks at once using multiple Lanes, take after take. For example, if we performed three or four takes of a song using 16 tracks, each take placed onto its own lane per track, Sonar or the system can't handle it, so we get this error.
 
There's something Sonar is trying to do with ALL take Lanes of ALL tracks at once, and it simply can't handle doing this.
 
Our workaround, whether this will help your case or not, was to create a whole new project for each Take vs. using Take Lanes.