Loss of sound on a single track. Any ideas?

[Jimibrix]

During bouncing guitars, I'm noticing one track will cut out here and there while the other is fine. When I go back and check, the source track is complete... It seems to be at random however, it's consistent with regards to the source track at the time of bounce. It doesn't go back and forth. Also, when bouncing three or four, same thing, but it's isolated to one singe source track, regardless of whether I'm bouncing two or four. It doesn't seem to happen when I bounce a single. So I can't figure out why I'm getting drops like this. Any ideas? It's never happened before today. If it was my system i would think I'd lose all sound at the same time, not just a single channel. Running PT10.2 on W7/64 using Digidesign 003 fader system. Any ideas would be appreciated. Additional note, all other tracks are deactivated during this bounce.

[Chris Lambrechts]

is the drop consistent ? As in when you bounce it twice - does it occur exactly at the same point in time ?

Always a good idea to trash prefs and do a permissions repair (if you on OSX) in these type of scenarios.

Or - another idea : create a new session and import everything from the troublesome one.

Look for an elimination process / keep plugins in mind. For example - if the suspect track has plugins on it - does it occur when you remove the plugins ... things like that.

Hope you're able to pin it down quickly. It's definitely not 'normal'

Chris

[Jimibrix]

At random points, never the same place twice. The only plugin running is iZotope Alloy 2 which has never given me problem before.... Going to deactivate them and see. Thanks.

[sunburst79]

Odd issue. The track bussed anywhere or have any automation enabled? If it wasn't random I would suspect perhaps something was getting automated down stream.

What happens if you duplicate the track. Does it play back. With or without the plugs?

[albee1952]

What is your buffer setting? For bounce to Disk, I usually push that to 1024 as sometimes, the lower buffers will choke on a large session.

[Jimibrix]

I rebooted, deactivated the Alloy2 plugin, and it seems to have 'fixed' itself. I'm going to uninstall the iZotope and reinstall it. Thanks for all of your help. That's why I love this forum!

[Jimibrix]

Oh I wasn't bouncing to disk, although I do that exact thing as well. I was bouncing two mono guitar tracks down to one stereo track with them panned far left and far right, just to free some memory. I don't like going over 70%. Once I go over 48 tracks I like to see where I can condense to bring it all back down. The plugins eat lots of 'brains'! I can record endlessly, but the last thing I want is to have to master 100 tracks. While I bounced my mono guitars to the stereo track one side was randomly cutting out as I bounced... Reasons unknown.

Let me ask if you don't mind. I have my RAM and drive meter gadget pinned to my lower left side of the screen so that I am able to monitor them at all times. What percentage of disc usage and RAM usage puts me in the danger zone? 70%? 77%? Anyone know?

[Jimibrix]

I keep my processors at 6 out of 8, minimum latency settings box checked and set to 'Maximum', cache to 4Gb and plug-in streaming buffer on level 8. H/W buffer size I change depending upon what I'm doing. Highest at 1024 for mixing, mastering and bouncing to disk, and lower for recording and bouncing track to track. My optimize for streaming box remains unchecked.

[Jimibrix]

If anything I'm doing looks unhealthy let me know. I have 12Gb RAM installed. The two harddrives 1Tb each.

[albee1952]

Still curious on your buffer setting. Amp sims, as a whole, are serious cpu hogs. Sometimes, instead of using Bounce to Disk, it works better to simply bus to a new audio track and record