Participant

Audio Channel Mapping doesn't work - Premiere Pro 26.0.2

Forum|Forum|14 days ago
April 1, 2026
2 replies
45 views

I commonly record R3D footage with 4 audio channels, and then before editing in the project panel, I isolate channels 3 and 4 (which contain the lav or boom feeds) by right clicking a clip and selecting “modify-->audio channels”. In 26.0.2, this feature has no factor, the audio I hear is always from source channel 1 and 2 (built in scratch mics), I never hear anything from Channels 3 or 4. This is true with new empty projects created within PP26 and with projects migrated forward from PP25.

I luckily noticed this early on during a big project, reverted back to PP25.6.4 and where this is not an issue (I can hear all audio channels as expected, and remap the source clips channels when I want to).

Mac Studio M4Max 64gb running Sequoia.

T

ThibaultD

Inspiring

EDIT : Bug already reported :

How to check the bug :

Create a project in PrPro 2026.x.x. Import RED RAW clips with 4 audio channels. Put in a sequence and observe that audio mapping is wrong :

Channel 3 is now channel 2
Channel 4 is now channel 3
Channel 2 is now channel 4 (or channel 1 is now channel 4, can’t confirm that)

Alternatively :

Create a project in PrPro 2025.x.x. Import RED RAW clips with 4 audio channels. Put in a sequence. Check that all audio channel are correctly mapped (it should be).

Save the project and open it with PrPro 2026.x.x : you can observe the bug :

Channel 3 is now channel 2
Channel 4 is now channel 3

Another way :

Create a project in PrPro 2025.x.x. Import RED RAW clips with 4 audio channels. Put in a sequence. Check that all audio channel are correctly mapped (it should be). Export an XML of this timeline.

Now you can notice :

Import this XML in PrPro 2025.x.x → No Bug
Import this XML in PrPro 2026.x.x → BUG

Spec :

Windows 10

Premiere Pro 2026.0.x

R

Rach McIntire

Community Manager

Hi @default0yuznc78rivt,

Thanks for flagging this. This is a known bug in 26.0.2, and the team is actively working on a fix. I'll update this thread as soon as there is more information.

Sorry for the frustration, and thanks for your patience in the meantime.