Mix Sessions

Typically includes

1. For “in-the-box) projects or partially “in-the-box” projects
   1. Dialogue mix session
   2. Music mix session
   3. Backgrounds/Ambiences
   4. Foley mix session
   5. Effects mix session
   6. M&E mix session
   7. Any other type of mix session created for the project
2. If some or all of the mix is a long-form console project, add
   1. Board specifics: model, firmware/software version
   2. Board input/output routing setup. Photos files helpful.
   3. Board automation files, clearly labeled as to what mix pass they refer
3. Audio Configurations (native and downmix sessions)
   1. Immersive
   2. 7.1
   3. 5.1
   4. Two-Track
4. Additional items
   1. I/O file (.pio or similar) for each session
   2. Renderer setup file (if applicable). Note type and version
   3. Plug-in list with versions (plug-ins are not delivered)

General Notes and Recommendations

• For projects utilizing an “in the box” workflow, the Mix Sessions represent the mix moves and processing done to create the final mix stems and M&E
• All volume, pan and other automation should be present in the sessions, including plug-in automation.
• All plug ins and their versions used should be noted. The plug-ins themselves are not included in the sessions.
• I/O files should always be included.
• Renderer setup files, noting renderer type and software version should be included for all immersive sessions.
• If a long-form console workflow was used, then specific information for the board used, setup and automation files should be archived.
• If a hybrid workflow was used (i.e. some aspect of the mix were done on a long-form console and some “in-the-box”, then the above specific information for the mix sessions must be included as well as the long-form console workflow information and files.

Formatting Recommendations

• The mix sessions may be individual by component (e.g. DX, MX, BG, Foley, FX), or combined (e.g. DX/MX, BG/Foley/FX) depending on the workflow used on the mix stage.
• Within each session, each track must be clearly labeled
• The audio files (“media”) used for each session should be in the project folder for that session using “save session copy in”, which will include only the audio files actually used in the session. Note that the only audio files required are those used in the movie. Do not include a library of sounds.
• No assumption should be made that the audio files will be backed up and available elsewhere later, they must be archived with the sessions.
• If the media was not delivered, the session should still be archived, but it will have limited future use.
• It is recommended to consolidate the sessions into flat files, but it is not required.
• The main Mix Sessions are generally in the native audio configuration mixed for the movie.
• In addition to the main Mix Sessions, downmix sessions to obtain lower audio configurations (e.g. Immersive to 5.1, 5.1 to Two-Track) should also be archived. In some cases these may be included in the main mix sessions, or may be their own sessions depending on workflow choices.
• If the sessions are immersive audio, each session should contain multiple bed tracks to match the intended audio configuration, with associated objects as created.