Multitrack Mixdown problem - extraneous noise

[Domus84]

Hi guys,

I have a medium-large multi track session that I'm trying to bounce to a 96khz/24bit wav in order to start mastering it. When I play the session in Audition, all sounds well, but when I export as a Multitrack Mixdown, there is a high-volume repeating stuttering sound throughout most of the track.

So far I've tried:

deleting all instances of Full Reverb, other reverbs, and echo effects

exporting at 44.1/16

transferring entire project to a different HDD (and an SSD)

reinstalling Audition

Wondering what to do next?

Also to note: until about a week ago (maybe even before the recent update??) I could export the whole session no problems, including 3 instances of Full Reverb, etc.

Thanks for your time 🙂

Pete

update: I have identified the problem: keyframe automation of the Amplify effect and the Stereo Expander effect. Have worked around these effects in another audio program, but fairly annoyed at having lost over a week to this problem (due to having to bounce various parts of the track in dozens of permutations and combinations over and over)

[SteveG_AudioMasters_]

One thing you might want to try is pre-rendering (aka 'locking') tracks with intensive effects on them before doing your mixdown. This will pre-process the track, and potentially reduce the chances of these things happening.

[ryclark]

keyframe automation of the Amplify effect

Not quite sure why you would want to apply keyframe automation to the Amplify effect when you already have a couple of different ways of automating the Track volume control?

[Trevor_Asq]

Almost certainly unrelated but I get a very similar effect in PPro with multitrack - I have submixes feeding the main mix out of 1&2 with the FX/DX/MX submixes feeding 3-8.

i can see the issue on the metering in PPro (needle movement where there should be silence).

my workaround is to quit & restart PPro before export. Usually fixes it. Seems to be less frequent now I’ve stopped using single & multiband compression on the master bus - use the tube version instead.

[MonoxideWorks]

I would like to add that I'm experiencing similar problems with my exports. I've handled 2 full length feature film exports in 5.1 surround sound the past 3 weeks; and everytime we have "heavy" track effects like Convolution Reverb or Chorus and automate certain parameters, I end up with a file with high frequency stuttering. I'm quite certain now that this is a bug in the latest Audition CC 2018 update, as several users have experienced the issue already. I've used similar effects in the past with no problems at all. Yes, the exports took way longer then - and they are indeed very much faster now in the 2018 update - but this export error is going to be a problem. The odd part is when I Pre-Render the track, bounce the selected track to a new track or bounce the selected clips to a new track - I get the SAME problem. The only way that worked for me is to move the Track Effects into Clip Effects, bounce them at 100% wet (as for Reverb) and then just mix in the bounced wet signal. Can someone else confirm the bug please? Thank you.

[Domus84]

Yes, MonoxideWorks, my thoughts exactly. It seems like a bug since the recent update, as the problem was not present until then. Realtime playback is fine, just export/bounce has the problem. Thanks for the suggested work-around. Hoping someone from Adobe has a comment here.

[ryclark]

They will possibly only comment if you have actually reported the problem as a bug. Otherwise how are they to know as this is a U2U forum. However the developers do occasionally take a peak at what is going on here.

[Latte Brothers]

OK.  I got the same problem.  Have isolated it to two tracks where I've added keyframes to fade / apply effects in the track.  This used to be a great way of making a vamp wet while the tag is dry,or whatever effect on the track that needs adjusting. 

So, I saved the project as a "Test," and removed all keyframes from the track's effects, and the noise went away.  Bummer!  Spent months getting these tracks sounding sweet.  Workaround is just too time consuming to consider.

Adobe needs to fix this fast.

[ryclark]

They are working on various bug fixes for CC2018 we are led to believe. in the mean time the advice is to revert to CC2017 which can be done from the Creative Cloud desktop app.