Skip to main content
A
Alex _Phantom
Participating Frequently
February 12, 2025
Answered

Apple Silicon M1/M2/M3 compatibility with CEP for creating extensions

  • February 12, 2025
  • 2 replies
  • 755 views

I'm learning extension coding using extendscript. And I'm trying a very simple function of muting a sequence by pressing a button in the extension. 

1. I'm able to detect a sequence and get its info
2. However when I'm trying the mute function, it's saying that either
a. Tracked is locked (when it is not)
b. Track is already muted (when its not)

I'm trying to figure out if this is Apple silicon extendscript problem, or am I doing something completely wrong? Any help would be great!

    Correct answer Bruce Bullis

    PPro ExtendScript exhibits the same behavior, on MacIntel or MacARM. 

     

    For 2a and 2b, please post the failing ExtendScript code. The PProPanel sample successfully mutes tracks; does it work, on your system?

    2 replies

    Bruce Bullis
    Community Manager
    Bruce BullisCommunity ManagerCorrect answer
    Community Manager
    February 13, 2025

    PPro ExtendScript exhibits the same behavior, on MacIntel or MacARM. 

     

    For 2a and 2b, please post the failing ExtendScript code. The PProPanel sample successfully mutes tracks; does it work, on your system?

    A
    Alex _PhantomAuthor
    Participating Frequently
    February 13, 2025

    I just literally got it to work! Hoepfully its only issues with the code and not ARM chips.
    I think was using the wrong extendscript code between mute() and muted() lol. But i wasn't sure if it was me or a apple silicon issue that was comepletely wrong (totally new to coding here).
    If were to make a extension via CEP, whats the best way to do it on a M2 macbook pro lol? 
    My options were
    1. CEP 12, cause its the latest -  But i can't run PPro on rosetta, debug, and potential risk ARM issues?
    2. CEP 11, and work off PPrp 23.5 - But it's a bit outdated now and I want to code to reduce redundency on certain items

    Bruce Bullis
    Community Manager
    Bruce BullisCommunity Manager
    Community Manager
    February 13, 2025

    Again, there are zero differences in PPro's CEP+ExtendScript behavior, between MacARM and MacIntel. 

     

    >If were to make a extension via CEP, whats the best way to do it on a M2 macbook pro lol?

    The PProPanel readme provides thorough 'getting started' guidance. Broadly, we always recommend staying current; CEP12 on a MacARM system.

    C
    Community Expert
    Carlos ZiadeCommunity Expert
    Community Expert
    February 13, 2025

    did you try UXP Developer Tools instead?

    It interacts better with the API

    A
    Alex _PhantomAuthor
    Participating Frequently
    February 13, 2025

    I dont think CEP plugins have manifest.jsn file to attach to, only a manifest.html if im mistaken. Dont think CEP extensions work in UXP developer tool.

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