I moved the set of audio clips to track 2 and it works fine there. It's only on track 1 where it fails to play after 18 minutes.
So it has nothing to do with my system. It's set up for performance use and has more than enough resources.
 
I created a new project and copied the clips to it and had the same trouble so there's something screwy with track 1 in X2, it seems.
 
Normally I kept each clip on it's own track and record them to tape individually. Putting them all on one track was meant to speed up the recording process.
 
I'm not going to try exporting the project or mixing it down to see if that works because I have no need for that in this case.
 
Next time I'll just put them all on track 2 and file a bug report, I guess.
 
 
Thanks for the ideas,
 
Steve

I believe there is a 2 GB limit for the file size for normal wave files. However, Sonar also supports Wav64, which has a much higher limit, and it automatically switches to Wav64 once the 2 GB limit for Wav has been reached. So theoretically the time limit from Sonar is more likely to be determined by your disk size than anything else.

If you are getting a stop at an earlier point in time a setting or device driver on your computer is causing the issues as others have mentioned.

Peace,

Tunes

Well, I took some time to check this out on my DAW. WIN 7 64 and Sonar X2.

Even though I have one project that goes for 12 plus minutes made up of forty midi and 20 audio tracks, I wanted to test Sonar's time limit.
I made a new project with just 1 audio track; enable record and left it to record for 48 minutes. Never timed out. The file was 1.02 gigs when done.

Based on your last analysis I might now think you have a corrupt Template. As stated, my test was done on Track one.

My current album project runs for well over 100 minutes with about 17 different songs on it and it plays back without a problem

I have recorded live 45 minute sessions with 8 channels without any problems.

So I guess I can surmise from all 15 responses that the answer to my question is NO!
 
I suspected a bug when it happened and I'm still bugged by it, so BUG it is!
A very strange bug, but still a bug, no less.
 
A bug by any other name might be a feature but I certainly didn't request it.
 
 
We need a bug smiley for posts like this. Would that require a bug request?
 
 
.

I'd call support because that's pretty annoying and IMO unacceptable for a pro audio platform. What about people who do film work or want to work with live sets? I'm sure there is a solution out there. Cheers.

@jersey - do you have all 100min in one project??

Dat be what he say, fo-sure.
 
I will attempt a fresh new project and see what happens. This one was hijacked from a previous project and resaved which may be part of the problem.

swamptooth


@jersey - do you have all 100min in one project??

Sorry - did you mean me? If so, then yes in as much as I import my final(?) mixdowns into an album project, each song on its own track and spaced out on the timeline where I can set appropriate gaps/seques/fades etc.