Q100581: How to create an audio mixdown in Avid prior to exporting an AAF for Flix 6
Audio often severely impacts the filesize of the AAF exported out of Avid for publishes back to Flix, causing longer publish times and increasing the chance of failures linked to internet speed, bandwidth restrictions and similar.
Mixing down the audio reduces the AAF size by 20% to 80% depending on the Avid project. This article will give a step by step on how to achieve this.
Below are the steps to take in order to generate an audio mixdown in Avid before exporting the AAF for Flix.
- Go to Timeline > Mixdown > Audio > Multiple Mixes...
- Select all the audio tracks you want to be included in the mixdown, like in the screenshot below:
- Make sure you tick the box to create a new sequence, and name it.
NOTE: Not ticking this box will generate an audio mixdown and add the single audio track containing it to the Bin. You will then have to add this to the sequence as an additional step.
- Click on Mix.
Following these steps, a new sequence will be created with the audio mixed down as a single track. This new sequence can then be exported as an AAF for Flix.
You can choose to use the usual export settings, however we recommend unticking the “Add Audio Mixdown to” box, as it is redundant after creating your own mixdown.
For information on how to set Flix up with Avid, and how to send sequences to and from editorial, please refer to our online documentation Flix for Editorial.
If you are struggling with publishing back to Flix from Avid, please open a support ticket and include the following information:
- A screenshot of the Avid AAF export settings used.
- A description of the issue.
- The “Effects & New Clips” behaviour chosen for the editorial import in Flix.
- The Flix Server Logs from all Servers downloaded promptly after reproducing the issue. If you are unsure on how to retrieve these, you can refer to our online documentation Logs.
For more information on how to open a support ticket, please refer to this article: Q100064: How to raise a support ticket.
We're sorry to hear thatPlease tell us why