Skip to main content
Inspiring
Oct 20, 2026 10:03 PM UTC
In Development

Multichannel export with Loudness effect causes incorrect audio routing

PP 26.5.2 (Build 5)

 

Sequence is simple 12 channel track ident (tone blips A1-> A16)

 

Exporting to 12 channel WAV:

 

1. with no Loudness effect

 

Tracks pass through as expected

 

2. with Loudness effect (doesn’t seem to matter how the sequence tracks are assigned)

 

Instead of tracks appearing as per sequence they are routed sequence -> file as follows:

 

1 -> 1

2 - NONE

3 - NONE

4 -> 2

5-> 3

6 - NONE

7 - NONE

8 -> 4

9-> 5

10 - NONE

11 - NONE

12 ->6

 

https://drive.google.com/file/d/1s9Cul4PYWLcckKiIHcpKnHPh93eOYaFV - sample sequence and export presets. 

 

    3 replies

    trevora3Author
    Inspiring
    Oct 21, 2026 7:00 AM UTC

    Thanks for responding 

    This is win11 at work, but behaviour is same on MBP M2 max - which is where this test sequence was created

    Working mono, discrete etc has same result.

    Behaviour I expect is for the relevant tracks to be processed and only processed for loudness. Tracks should not be shuffled or muted (I *would* like that as a separate option for audio when exporting.

     

    We deliver A1-6 5.1 mix, A7-8 2.0 mix then 2x 2.0 stems on A9-12.

    I want to normalise loudness (EBU -23LU) on 2.0 mix on 7&8 *only* 

    I simplified to a 16 Ch adaptive to report the issue.

     

    Previous report around same setting (different issue) . Indicates testing of this is not thorough enough.

     

    https://community.adobe.com/bug-reports-728/multichannel-loudness-normalisation-on-greater-than-4-channel-sequences-ignores-process-checkbox-1332263

    Translate
    Amy the Stuv
    Community Manager
    Community Manager
    Oct 21, 2026 5:12 PM UTC

    ​@trevora3 Thanks for sharing the project details and the related report. We’ve tested the supplied media and sequence in both Premiere Pro and AME with the supplied export preset. In the exports we reviewed, the source-to-output channel order stayed intact, and the Loudness report showed only channels 7–8 being processed as intended by the preset. We haven’t reproduced the routing change described in your report yet either.

    To help us match the conditions of the export where you observed the issue, could you help us confirm a few details?

    • Which application produced the affected export: Premiere Pro’s Export workflow, or Send to/Queue in Adobe Media Encoder? Please include the AME versions/builds.
    • In the sequence used for the affected export, what were the tracks settings? 12-channel Multichannel with Adaptive tracks? Could you please share the track-to-master channel assignments?
    • How was the source clip interpreted under Modify > Audio Channels? For example, was it set to Adaptive, 12 channels, one audio clip?
    • For the affected render, could you share the output WAV and its Loudness report XML, plus a matching export with Loudness disabled? 
    • Since the source has 16 mono streams and the export has 12 channels, how should source streams 13–16 be handled in this delivery? Currently they are ignored and the clip is interpreted with just 12 channels, but was this intentional?

    A short screen recording of the sequence audio setup and export settings is also helpful. I have DM’d you a private upload link for any additional material to help us identify the cause of this issue. 

    Translate
    Amy the Stuv
    Community Manager
    Community Manager
    Oct 20, 2026 10:27 PM UTC

    Hello ​@trevora3,

    Welcome to the Premiere Forums and thank you for posting with a sample project and sequence! To confirm, are you intending to send Source Channels 1 and 2 to Stream 1, etc? If you want this to export as discrete audio have you tried setting this section to Mono and adding up to 12 channels?

    Loudness Setting Changed to Mono in Export Mode

     

    Out of curiosity, could we gather your system specs for this report as well? 

    • Operating System: Specify Windows or macOS, along with the version.
    • Chip (Mac Only): Specify which M-series Chip or CPU/GPU combo.
    • GPU and Driver (Windows only): Please let us know your video card and driver version. We recommend updating to the most recent version; for NVIDIA users, we strongly recommend the Studio version of the driver.

    I may be misunderstanding the intention. Would you mind explaining the desired outcome?

    Hoping to help,

    Amy

    Translate