Skip to main content
Participant
December 6, 2017
Answered

Multitrack Export Mixdown in Audtion CC 2018 build 11.0.0.199

  • December 6, 2017
  • 2 replies
  • 706 views

I have a mid-sized session with about 40 five minute wave tracks and 26 bus tracks with effects like mastering and multiband compressors on the bus tracks.  The Multitrack Export mixdown of the entire session is producing nothing but a noisy, static sounding file that has a different duration than my session.  There are no sounds from the session, just some random noises that has a blockish wave form.

I installed the previous version, CC 2017.1.1 build 10.1.1.11 and the exact same session exports perfectly fine with the Multitrack export mixdown in the 2017 version of Audition.  It seems to just be broken in the 2018 version.  The session was created in the 2018 version.  In addition, bouncing the bus tracks in CC 2018 works on some tracks but not all.

Any advice as to why this works in the 2017 version but not the 2018 version?

    This topic has been closed for replies.
    Correct answer SteveG_AudioMasters_

    Unfortunately it is a known bug - and the devs are currently working on a fix for it. When it's been thoroughly tested it will be released, but we don't have a date for this yet.

    2 replies

    Deian Gerallt
    Participant
    January 17, 2018

    I'm having same problems. Looks like I need to put the old version on. Money back?

    ryclark
    Participating Frequently
    January 23, 2018

    Update CC2018 v.11.0.1 now available.

    SteveG_AudioMasters_
    Community Expert
    SteveG_AudioMasters_Community ExpertCorrect answer
    Community Expert
    December 6, 2017

    Unfortunately it is a known bug - and the devs are currently working on a fix for it. When it's been thoroughly tested it will be released, but we don't have a date for this yet.

    Participant
    December 6, 2017

    Thanks.  Is there a place where this bug can be tracked?

    SteveG_AudioMasters_
    Community Expert
    Community Expert
    December 7, 2017

    No, I'm afraid there isn't. It's one of a number of issues with the present release being attended to. Whilst I know that this is in progress, I have no idea at all when the fix will be released - and anyway I'm under an NDA so even if I knew, I couldn't tell you!

    I'm afraid that you'll either have to be patient, or if it's causing a production issue, you can revert to the previous release easily using the CC app.