I know Ive seen this posted by others, heres my situation

I have a project
20 tracks, 6 busses
(Audio and Session Drummer 64 tracks)

It will [Dropout] around the 2:20:00  every time. I can make it vary a little by changinging the "Now/Start time"
No indications of any problems in the Control bar as far as Processor, Memory Usage, etc...

This is one of many similar projects but it only occurs on this project.


Any Ideas???  (On why just this project is effected)

Are you using any CPU intensive F/X...like Transient Shaper... that one gets me a lot.  Or maybe Perfect Space Reverb?

What is different about THIS project than your others?

No difference in FX that are inserted.  

It just started doing it all of a sudden, no reason as to why.

Kind of has me baffled

I gonna try a Save As and see if it doesnt change

If not, Ill try dragging all the clips to a new project and redo all the FX

Could you possible have interference from an external service that is running?  Sometimes updates of things like antivirus software and even some internal Windows services can alter their behavior due to periodic updates.

Maybe you can review your Windows patch history?  Take a look at services that are running and temporarily turn a few of the bigger ones that are not really needed during audio processing off?

Otherwise, can you drop your sample rate through completion of this project?  (Or at least until you get things sort of distilled down later on - less tracks and such).  I would think if you have completed the capture of most of your audio that dropping the sample rate wouldn't really hurt you (would it?).

Bob Bone

And, what about possibly looking at buffer size?

Bob Bone

OK  Found some sort of reasoning to it

The project has A LOT of slip edits 
The setting as far as recording took place in a large barn lined with smooth hard wood.  We picked up lots of bleed on the drum kit mics requiring the slip edits.  I also used Audio snap to grab the transients and convert to midi to replace the audio with a good clean drumkit eliminating all the bleed.

Im guessing all the slip edits and transient markers and editing was confusing and binding up the processing.

I went in and eliminated all the slip edits back to a single audio track and the problem vanished.

So long story short is to much was going on with editing at one time confusing the software?

Anyway I can proceed/continue editing my drums now LOL

Just wanted to share the info

Glad you got it sorted out and passed it along.

robert_e_bone


And, what about possibly looking at buffer size?

Bob Bone

Bob's right. You should check your Midi Buffer size (minimum of 500ms when you have a lot of midi going on). I know your problem is fixed, but maybe it's just because you spread some midi data out so your midi buffers could then handle the quick changes. To prevent problems in the future, do check your midi buffers. I think the default is 250.


Best,
Rob

Not sure what the buffers are set at as far as midi goes because I rarely use but with using session drummer more and more to get rid of bleed, maybe it is an issue.

There were probably close to a 1000 slip edits on the audio tracks with fades etc... going on to work out bleed so not sure but getting rid of the heavy edits did do the trick in getting rid of the one drop out occurring at that 2:20:00  time mark.

Since this Ive added 3 more midi tracks converting audio over and still havent had a prob.

I have other projects with a lot more going on with Session Drummer and they are fine

As for Background programs, EVERYTHING is killed outside of Sonar through msconfig and I dont see anything spiking on Task Manager or DPC lat 

One thing I am getting ready to do is jump from 8GB to 16GB of memory.  The I7/870 and 8 GB Mem seem to be doing great but for $75 why not do it for future expansions on builds of software and performance. 

Looking forward to see how it betters what I do-which is mainly barn/garage recording and fix ups for band demos