Participant

Question

Audition cc Multitrack display choppy/lag/stutter, help please

Forum|Forum|9 years ago
May 13, 2017
4 replies
7875 views

I just moved to a new PC from an Imac (2013) and am noticing very bad choppy/stutter/lag/latency/ when moving clips around in multitrack. (I have all snapping turned off. There is about a half second between moving my mouse to where the clip should go to the clip actually ending up there. Same thing when trimming tracks. Very frustrating. My new computer should be able to handle anything audition can throw at it. (i7 7700k cpu, gtx 1080 gpu, 64 gb ram (32gb allotted to audition). Is there a setting somewhere I am missing or what?

This topic has been closed for replies.

LaSalamander

Inspiring

BadBoYeed, upstreamstudios, check this out and let me know where you have a problem: Re: Why so sluggish?

U

upstreamstudios

Participant

Apologies, guys. I'm not even sure I have the EXACT same problem. They seem to be the same, however my google search terms were "adobe audition plugins choppy". And this thread was pretty much the only thing that came up that seemed pertinent. I would not have thought to search for anything to do with assets because this is not an intensive project at all.

I'm working in a project that has less than 10 audio files, longest running file is about 15 minutes, the rest are between 2 and 10. There are under 100 clips made from these files. If I open up a new multitrack session (this is in the 2017 version, mind you), with NO files added, and one plugin open, I find that it still gets choppy when I try to make changes in realtime. Not as bad as with this 10 file project, but enough that I wouldn't be able to make effective changes while listening if I were to have anything to listen to. I don't have as much ram as BadBoYeed, only 16 GB, of which 11 is dedicated to Audition. When I run the 2015 version, things tend to go pretty smoothly (although I have not pushed that to its limits). In a recent project I abandoned Audition (except for denoising) in favor of my main DAW Logic Pro. That was in 2 single hour projects which both had between 150 and 200 tracks each. Not even a clue how many clips there were. Definitely on the edge of being too much for my system, but things ran smoothly. But when I try to make adjustments too quickly in Audition (playing back even with no files), I get a beach ball.

If you are a professional, you might want to reconsider having your apps automatically update, as updates often introduce glitches and could potentially render your workstation unusable. Especially if you're like me and have a custom built workstation. I am still running Yosemite on a hackintosh. If I could upgrade past version 2017 I would have done so last year. And I'm stuck with Yosemite because my video card is incompatible with the newer OSes.

Now, this could have something to do with my video card, but all things seem to indicate that it's running fine. It's running the most recent reliable updates. The card has 3GB of memory, it's an nvidia GTX 660. A few months ago, I had to spend some time getting the card functional again because I noticed that media encoder wasn't utilizing the CUDA cores. So it "could" be the video card, but I doubt it is.

Looking over your thread, I'm wondering if Audition is having trouble with multi threading, because that would be consistent with my symptoms. My hardware monitor will only show the CPU usage as a whole, and not the separate processors. I'm curious to see if my version of Audition leans heavily on one core or not, but I'm not sure if I'll be able to figure that one out. If I can find a monitor app that can give me that info, I will let you all know.

But I will mention again, this problem doesn't seem to occur (for me) in Audition 2015. 2015, that bygone era when Apple was only just beginning to undermine Adobe's compatibility...

ryclark

Participating Frequently

upstreamstudios wrote
If you are a professional, you might want to reconsider having your apps automatically update, as updates often introduce glitches and could potentially render your workstation unusable.

Yes I agree that this is generally the best philosophy. However with most Adobe software updated using the Creative Cloud desktop app you can go back and re-install previous versions if the update does give new problems rendering your current work unusable. Also it is best not to do it in the middle of a project. But because I am often replying to posts on the Audition forum I do have virtually all previous versions installed since AA3 and available to test or compare operations.

U

upstreamstudios

Participant

I'm not sure about a real fix (I'm currently using Audition 2017, hoping to upgrade soon and see if it helps), but I've been seeing some improvements after lowering the I/O buffer size. Go to preferences>audio hardware and adjust it there. I had been using a buffer of 1024, but lowering to 256 seemed to help a lot. Not perfect, and I'm a little reluctant to lower the buffer more, but I can now adjust my plugins during playback with minimal glitchiness. Before, the whole app would freeze but continue playing

SteveG_AudioMasters_

Community Expert

This is a two-years-old thread and the OP hasn't responded...

U

upstreamstudios

Participant

The OP was the only person who ever posted, and this was never answered or figured out. And since I had the exact same problem and couldn't figure out a solution for a while (been using Audition 2015 because it doesn't seem to be effected), I thought I would share this information. Not sure what the problem really is, but it'd be nice if some unresolved issues got some attention. I'm not the only person trying to work with this, and not being able to use a DAW in real time is a drag

B

BadBoYeedAuthor

Participant

The above worked for a little while, but after a few hours in a multitrack project, the problem returned. Mixed down the file i was working on and started new multitrack and problem went away again. this is not a good workflow...please help

B

BadBoYeedAuthor

Participant

I believe the problem has been solved. Switching project to 32 float bit depth as opposed to 16 which is what it was.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.