Skip to main content
abdallahk57993923
abdallahk57993923
Participant
May 12, 2026
Answered

Clarification on a 26.x regression where setAudioChannelMapping no longer updates clip count and related properties are undefined.

  • May 12, 2026
  • 2 replies
  • 56 views

1. Is the audioChannelsType/audioClipsNumber regression on the 26.x bug tracker? ETA before the Sep 2026 ExtendScript sunset?
2. Is there an FCP XML schema element that forces a single-clip mono master on import for a
  multichannel source, or is the on-disk channel layout authoritative?
3. Is there a UXP roadmap item for ClipProjectItem.setAudioChannelMapping parity?

Note: I’m not really a programmer and I’m using AI. 

    Correct answer bbb_999

    Your AI is incorrect.

    I have just confirmed that setting audio channel mapping works correctly in the shipping version of PProPanel. 

    Please actually test issues, before requesting help with them.

     

    2 replies

    bbb_999
    Community Manager
    bbb_999Community Manager
    Community Manager
    May 13, 2026

    > Is the audioChannelsType/audioClipsNumber regression on the 26.x bug tracker? 

    What is the actual issue, to which you’re referring?

    >ETA before the Sep 2026 ExtendScript sunset?

    ?! No sunset / end-of-life dates have been set for either ExtendScript, or CEP, in Premiere.

    > Is there an FCP XML schema element that forces a single-clip mono master
    > on import for a multichannel source, or is the on-disk channel layout authoritative?

    Premiere supports Apple’s FCP XML specification, version 1.4 (which corresponds to Final Cut version 7.0.3). Regardless of what a referencing XML file contains, Premiere’s API offers audio channel configuration for projectItems. [Any such reconfiguration not affect already-existent trackItems, created from that projectItem; the new config will be applied in subsequently-created trackItems.]

    >Is there a UXP roadmap item for ClipProjectItem.setAudioChannelMapping parity?

    We continue our work to bring UXP API to functional parity, with what was possible via ExtendScript; this includes audio channel mapping. 
     

    abdallahk57993923
    abdallahk57993923Author
    Participant
    May 13, 2026

    Thanks. (again this is AI response)
     

    Regarding the actual issue: in Premiere Pro 26.0.2 on Windows 11, ProjectItem.setAudioChannelMapping appears to fail silently. I tested this with a minimal reproduction using a freshly imported multichannel .wav file, with no sequence references involved, so trackItem staleness should not be a factor.

    var m = clip.getAudioChannelMapping;  // property, not a function call
    m.audioChannelsType = 0;              // Mono
    m.audioClipsNumber = 1;
    m.setMappingForChannel(0, 2);         // source channel 3
    clip.setAudioChannelMapping(m);

    After executing this code, m.audioChannelsType and m.audioClipsNumber read back as undefined. Direct property assignments are ignored, and setAudioChannelMapping completes without throwing an error, but the ProjectItem itself remains unchanged. 

    K
    Community Manager
    Kevin-MonahanCommunity Manager
    Community Manager
    May 13, 2026

    Again, I let the team know, ​@abdallahk57993923. I hope we can get you an answer shortly.

     

    Thanks,
    Kevin

      K
      Community Manager
      Kevin-MonahanCommunity Manager
      Community Manager
      May 12, 2026

      Hi abdallahk,

      Thanks for the question. It's outside my area of expertise, though, so I'll let the product team know. I hope to get a response for you. Sorry for the trouble.


      Thanks,
      Kevin

      abdallahk57993923
      abdallahk57993923Author
      Participant
      May 13, 2026

      Thank you.

      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices