Skip to main content
alexandred28031804
alexandred28031804
Participant
March 20, 2026
Open for Voting

Inconsistent audio behavior in Source Monitor with multicam sequences (audio duplication / unintended mixdown)

  • March 20, 2026
  • 5 replies
  • 40 views

Since at least Premiere Pro 2023 (still present in 2026), the Source Monitor does not correctly reflect the actual audio structure of multi-cameras sequences when external audio sources are used.

 

Context:

The issue occurs with a multicam sequence built from:

  • Two camera angles (camera audio disabled or ignored)

  • Two external mono audio sources (MIC1 and MIC2)

  • Synchronization performed using In points (clap)

Inside the multi-camera sequence (timeline), the audio behaves correctly :

  • MIC1 and MIC2 are properly separated

  • Each microphone is on its own track

  • Playback is correct

 

Expected behavior :

When opening the multi-camera sequence (or a derived target sequence) in the Source Monitor:

  • Audio tracks should remain distinct (MIC1 different from MIC2)

  • Waveforms should reflect the actual content of each track

  • Inserting into another sequence should preserve separate audio tracks without duplication or mixdown

Observed behavior, in Source Monitor :

  • All audio waveforms become identical

  • Only one audio source (e.g. MIC2) is effectively used across all tracks

  • Inserting into a sequence results in duplicated audio instead of separate tracks

This behavior is inconsistent with the same sequence when opened in the timeline, where audio remains correct.

 

Additional notes :

  • The issue persists after:

    1. Recreating the multi-camera sequence from scratch

    2. Verifying audio channel mapping

    3. Using mono and standard tracks

  • The problem appears to be related to how Premiere interprets a multicam sequence as a source clip

  • It behaves like an unintended mixdown or remapping inside the Source Monitor

Impact :

  • Prevents proper multi-camera logging (derushing) with multi-track audio

  • Breaks professional interview workflows using multiple microphones

  • Forces inefficient workarounds (copying from timeline, disabling audio, etc.)

  • Results in significant time loss

Comparison:

In Avid Media Composer, audio and video inserted from a source (clip or sequence) preserve :

  • Track structure

  • Channel separation

The Source Monitor reflects the actual content reliably.  

Conclusion:

In Adobe Premiere, the Source Monitor does not preserve the audio integrity of multi-camera sequences, leading to duplication or unintended mixdown of audio tracks. This is both a functional issue and a significant UX problem for professional workflows.

 

    5 replies

    R Neil Haugen
    R Neil Haugen
    Legend
    March 20, 2026

    Yea, that’s because in Premiere the Source monitor is ... the Source monitor. Intended to show the ‘source’ property of things. It isn’t the same use functionality as Avid, and some things like that are troublesome.

     

    Especially as multicams sequences in Premiere are really a hybrid thing, sort of but not really a clip, sort of but not really a ‘normal’ sequence. With some unexpected behaviors due to their structure internally.

    Everyone's mileage always varies ...
      alexandred28031804
      alexandred28031804Author
      Participant
      March 21, 2026

      Thank you for the quick reply.

      Yes, that actually makes a lot of sense — the “sort of a clip, sort of a sequence” explanation matches quite well what I’ve been observing 🙂

      So if I understand correctly what you said : this behavior is essentially a consequence of how multicam sequences are internally structured in Premiere.

      That said also —from a practical editing perspective, this still leads to a rather problematic situation, because in the case described previously, the multicam behaves correctly once inserted into a sequence, but the Source Monitor can still display valid waveforms while remaining silent — which, admittedly, is not ideal when logging interviews based on audio 🙂

      What’s interesting here is that this kind of behavior does not seem to occur in the same way in other pro editing software.

      DaVinci Resolve, for example, handles multicam in a way that remains consistent with Avid (a logic one in fact):

      • Audio is always audible in the source viewer
      • Track separation is preserved
      • Monitoring remains predictable

      This suggests that this is less an inherent limitation of multicam workflows, and more a consequence of Premiere’s specific implementation.

      Final Cut Pro follows a different paradigm (roles instead of tracks), so it is a bit of a different discussion. Anyway, I don’t use this software since… Can’t remember when ! Perhaps 2021...

      From your experience, would you consider this an intentional design trade-off in Premiere, or something that could realistically be improved?

      And, to add (without making an already “sort of clip, sort of sequence” object even more complex 😄), I have also observed:

      • Flat waveforms in the Source Monitor while audio is actually audible
      • As well as a counterintuitive audio channel mapping behavior when creating the multicam

      These points seem to point in the same direction: some difficulty achieving fully consistent behavior in Source Monitor audio monitoring.

      In its current state, the Source Monitor becomes somewhat unreliable for multicam workflows involving multiple audio sources — even when everything is correctly set up.

      R Neil Haugen
      R Neil Haugen
      Legend
      March 21, 2026

      Yea, it’s simply a difference in how the design teams thought through the front-to-back actions. Each app is different.

      This wasn’t a big problem while we still had the Reference monitor available in Premiere, as you could open a sequence in the Reference monitor, a different one in the Program monitor ... or link them together. But they decided not that many were actually using the Reference monitor ... and sadly to me, I was! ... and removed the code for it a version back.

      Multicams in Premiere simply need a ton of work at this time ... they can be made to work for most circumstances, but not for some clearly. And don’t work nearly as well nor obviously as say Plural Eyes did.

      And like a ton of other things, I’ll be bringing this up with the devs in Vegas at NAB again next month ... as I have for what, a decade now?

      Everyone's mileage always varies ...
        Terms & ConditionsAccessibility statement
        Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices