Skip to main content
Participating Frequently
Feb 12, 2025 3:37 AM UTC
Answered

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

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!

Bruce Bullis
Bruce BullisCorrect answer
Legend
Feb 13, 2025 2:03 PM UTC

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?

7 replies

Bruce Bullis
Bruce BullisCorrect answer
Legend
Feb 13, 2025 2:03 PM UTC

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?

Translate
Participating Frequently
Feb 13, 2025 2:12 PM UTC

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

Translate
Bruce Bullis
Legend
Feb 13, 2025 2:35 PM UTC

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.

Translate
Community Expert
Feb 13, 2025 8:17 AM UTC

did you try UXP Developer Tools instead?

It interacts better with the API

Translate
Participating Frequently
Feb 13, 2025 8:44 AM UTC

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.

Translate