Predubs/Premixes

Typically includes

1. Example Predub types – there are many possible subdivisions (varies by project – maintain project layout)
   1. Dialogue
   2. ADR (principal and adds)
   3. Group ADR a.k.a. Crowd, Walla
   4. Backgrounds/Ambiences
      1. Air/Winds
      2. Bugs/Birds
      3. Crowd/Walla
      4. City
   5. Foley
      1. Footsteps
      2. Props
      3. Cloth
   6. Effects
      1. Cars
      2. Helicopters
      3. Guns
      4. Special Effects Weapons
      5. On-Screen hard effects (e.g. doors)
   7. Sound Design

General Notes and Recommendations

• If predubs are recorded out to use as a source for the stems (e.g. as in a long-form console mix), they should be archived.
• If the predubs are virtual (e.g. as in an “in-the-box” mix), they are generally not recorded out separately, but are part of the mix sessions. The mix sessions should be archived.
• If virtual predubs are recorded out or rendered, all plug ins and automation should be running and the resultant tracks should have the results baked in.

Formatting Recommendations

• Predubs are generally divided up into “food groups” e.g. Dialogue, Backgrounds, Foley, Effects, which are further divided into their constituent parts.
• For example, Effects are usually divided into multiple predubs by the type or use of the effects e.g. Cars, Guns, Doors….. The division is at the discretion of the mix team, and should be preserved in the archive and detailed in the READ ME.
• Predubs are usually in the native audio configuration for the project, but can vary depending on the project workflow. They should always be archived in the configuration they were created.
• Predubs are generally delivered in various workstation sessions by the type of predub rather than all in one large session. The division is determined by the mix team. Each session should be clearly labeled and detailed in the READ ME.