Skip to main content
B
BigPines
Participating Frequently
December 29, 2016
Question

Audition 2015.2 Mac Will Not Export Sidechain Compression (Audio Ducking) FX

  • December 29, 2016
  • 4 replies
  • 1051 views

I have the sidechain compression set up on a 9 track audio project. One track is the voiceover and it controls the compression FX on the other 8 channels. When I play the audio in Audition, it works flawlessly. When I try to export the audio, the compression is not present. The audio sounds just like the pre-FX audio. Seems like a bug to me. Any ideas would be appreciated.

      4 replies

      R
      RoyceJennings
      Participating Frequently
      September 29, 2025

      Somehow still a problem 9 years later.  I just want to export a single side-chain compressed track without any other tracks.  Why is this so hard, or not obvious?  All I can think of is recording desktop audio while soloing and playing the track.... Does anyone have a solution?

      christiann7972413
      christiann7972413
      Participant
      July 5, 2020

      Also be sure that the track that you are sending to your sidechain compressor is not the same bus that you're exporting your mix through, I had this problem sending dialog from my Dialog bus to the Music bus but what I had to do is send my dialog straight from my original dialog track to a music sub bus and keep my master buses clean to export through, this way the processing might not fully make it to the export even though you may hear the sidechain compression in the project

      SteveG_AudioMasters_
      Community Expert
      SteveG_AudioMasters_Community Expert
      Community Expert
      July 5, 2020

      This post is getting on for four years old. Why are you replying to it?

      B
      BigPinesAuthor
      Participating Frequently
      December 30, 2016

      Thanks for nothing guys. This forum turned out to be as worthless to me as Audition - equally a complete waste of time.

      In case anyone else runs across this thread and is having a similar problem, this does NOT appear to be a bug. I installed OS X 10.12.2 on a VM and completely patched it so I was running the very latest up-to-the-minute Apple OS (as of today anyway). No doubt tomorrow when Apple releases 10.12.3, this forum will blame all reported issues with Adobe's software on Apple's lack of backward compatibility and the customer running an antiquated OS but I digress...

      I then installed the very latest Audition 2017.0.1 build 10.0.1.8. It works exactly the same as it did in my 'ancient' 3 year-old OS.

      It is obvious to me this is operator error. I must simply not understand how to use this tool. In the future, real assistance would be preferred over the rabid Adobe Defense Brigade coming out and proclaiming it is all the fault of the OS and Adobe is God and can do no wrong.

      I'll move on to Ableton Live. I know I can do what I want there. I was just trying to use Adobe's "easy" built-in workflow. *rolleyes*

      ryclark
      ryclark
      Participating Frequently
      December 30, 2016

      You said it was a bug in your OP. You were very quick to blame the software. So, unfortunately, we proceeded along those lines with our answers.

      "It is obvious to me this is operator error. I must simply not understand how to use this tool. In the future, real assistance would be preferred"

      Maybe if you had said that originally and asked for operational assistance then maybe our answers would have been different.

        Bob Howes
        Bob Howes
        Inspiring
        December 30, 2016

        Added to that, there WAS a known bug in 2015.2 which has since been fixed so it was pretty easy to assume that was the issue.

        Best of luck with Ableton--I use it myself for MIDI but (and maybe it's just me) don't get on at all with the GUI for any work with wave files.

        Anyway, sorry if you feel this conversation was useless but we did our best with the information provided.

          Bob Howes
          Bob Howes
          Inspiring
          December 29, 2016

          I believe I recall a reported bug in version 2015.3 and before that caused this effect.  I'm pretty sure you find it's been fixed if you upgrade to a newer version--the latest is CC 2017.

          B
          BigPinesAuthor
          Participating Frequently
          December 29, 2016

          Thank you for your response. I have updated to the latest available which is 2015.2.1 (v9.2.1.19) on Mac. The problem still exists. When I use File -> Export -> Multitrack Mixdown -> Entire Session... and then under "Mixdown Options" I select all tracks, I end up getting what sounds like the original tracks with no FX applied to them. I am editing 7.1 film audio. I would like to combine the voiceover track with the center channel as one mono file and all other channels exported with their effects in their own mono file. This will ultimately be encoded into DTS multichannel audio. If I export the Master track as mono, I get all the tracks combined together even if I only solo one of the tracks. This doesn't seem correct to me either. If I use Multitrack -> Export to Premiere Pro... and choose "Export each track as stem" I end up getting mono wavs with the same results. Am I doing something wrong? By the way, this project was created from within Adobe Premiere using the Edit -> Edit in Adobe Audition option. It doesn't seem like it should matter but I figure I should mention it just in case.

          Terms & ConditionsAccessibility statement
          Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices