Tracks cutting out from master

[jeremyo49343666]

Greetings!

I have searched far and wide on these forums for this issue that I am having, and could not find anything that quite described my predicament.

I am running Audition CC 2017

I have multiple tracks at the same time running, and while I have some tracks rendering, I start doing other parts of already pre-rendered tracks. Some tracks just cut out completely during playback, while others continue to play. Both of these are already rendered. The master does not meter the track that is cutting out when it cuts out, so something is keeping it from sending to the master. When I stop and play again, the track plays for a few seconds, but cuts out again, this happens on different tracks, not just a specific one, and it's across different file types including mp3, wav, and aiff.

I also have to mention, when everything is completely rendered this happens as well. Not just during rendering of other tracks that I am not using at the time.

I've cleaned my media cache on an empty workspace. I have uninstalled and reinstalled audition. The problem still continues.

Are there any suggestions as to what steps to take next? Thanks!

[ryclark · Accepted solution]

Where are all the audio files that you are playing back in the Multitrack session stored? Are they (and your Audition Temp folders) all on your system hard drive or do you have a separate hard drive for audio file storage and Temp folders?

By the way it matters not what format the audio files were originally when they are opened in Audition they are all converted to .wav files since that is Audition's native audio file format.

[jeremyo49343666]

Audio Files are on the system hard drive, an SSD. I have the media cache as an external conventional hard drive. Is it not able to recall or play those files fast enough? Is that what the issue is?

Thanks for the heads up about conversion to .wav files.

[Bob Howes]

jeremyo49343666  wrote

Audio Files are on the system hard drive, an SSD. I have the media cache as an external conventional hard drive. Is it not able to recall or play those files fast enough? Is that what the issue is?

Thanks for the heads up about conversion to .wav files.

That's probably a pretty good guess.  FYI, I also work pretty often with external HDDs and the most recent purchase was a USB3 device.  The performance for this sort of stuff was noticeable better.

The other thought I have is that, if you're purely mixing/editing, it's worth increasing the buffer size/latency.  Unlike when tracking, you don't need to worry about high latency and may give you a performance boost on many track/complicated effects.

[Chris27656191fjh4]

I'm quite late coming into this conversation, its been a few years with this issue and the problem has always plagued me but today working on a track, it was that bad that all the tracks would cut out meaning that it was impossible for me to record anything as I had no guide to preview from. I tried media cache and saving the files to the same drive, i tried exporting the entire session to a new session. (this one actually made the problem worse), i updated drivers, windows, I pre rendered all  94 tracks for a 2nd time, cleared more space on the harddrive, closed unuused programs. None of it worked. The culprit for me was in the effects rack and specifically in reverb based effects and you have to go beyond switching the effects rack off, and click on the effect. Once I went to the effect and physically switched off each effect, everything played and recorded perfectly. I have no solution for the editing/mixing stage, other than just hitting the spacebar again when it cuts out and or doing multiple mixdowns as you go, but this at least allows you to lay stuff down. It seems to be a bug Adobe have never got around to solving. 

[SteveG_AudioMasters_]

What is far from obvious about the effects rack is that just having an effect in it - even if it's muted or with the 'power' switched off (?) - uses up processing power, as the effect is running in the rack, even though it's not processing anything. I think you're right about nobody getting around to fixing any of this - the whole effects processing thing needs revisiting, including what happens with clips and automation, etc. I think it's overdue for an overhaul...