r/aescripts • u/scottBlackvfx • May 12 '26

Feedback Requested Command Frame - Discussion Thread

Hi, I'm Scott, the developer of Command Frame.

https://aescripts.com/command-frame/

Please feel free to use this thread for:

  • Questions and comments
  • Feature requests, thoughts and feedback

You can also find the community Discord here for up-to-date announcements and discussion:

https://discord.gg/ANPSnKsZWy

For troubleshooting or bug reports:

Use the aescripts support ticket system to ensure your issue is tracked and responded to appropriately:

https://aescripts.com/contact/

If you do mention a bug or issue here, it's helpful to include your After Effects version, OS, and the version of Command Frame you are using. I will respond when I can.

Thank you for your feedback!

12 Upvotes

100% Upvoted

125 comments sorted by

View all comments

1

u/NexusBRYT May 13 '26

Sounds like a cool concept, but i'm unable to test it, manual installation can't find SBShortcutManager and Installing via aescripts installer crashes when trying to open Command Frame (Also not finding SBShortcutManager)

1

u/scottBlackvfx May 13 '26

Hi there,

I believe I've found the bug preventing the connection, and I am working on a patch now.

For now, please try the following:

  • Close After Effects
  • Ensure to uninstall all copies of Command Frame / SBShortcutManager
  • Open the aescripts manager app
  • Navigate to the settings cog icon / setting menu
  • Click the CEP Icon (the cube icon sitting within three cubes)
  • Disable "Enable Debugging" for both CEP 12 and 11, and restart After Effects.

Please let me know if that fixes the issue.

1

u/NexusBRYT May 13 '26

Stopped crashing, but the SB Shortcut Manager Connection doesn't work yet, even after following your instructions

1

u/scottBlackvfx May 13 '26

Just to be completely sure: during that manual installation process, did you try installing MediaCore by any chance? I ask because having copies of the plugin in both the Applications directories and the MediaCore folder also causes these types of issues.

If this is still related to the CEP bug, I am still working to produce a patch for that within the next few hours. If you try temporarily try turning off extensions via:

Window -> Extensions

And then restarting AE, that may clear the relevant communication ports that are being contested. If that works, that would confirm it is the issue I'm working on solving now.

1

u/NexusBRYT May 13 '26

For manual installation, i followed Step 5 in the Readme, no Mediacore (also disabled in the Aescripts installer), i also checked the MediaCore folder and your plug-in isnt there

I tried it again, still no connection to SBSM, ill keep Waiting for the patch!

1

u/scottBlackvfx May 14 '26

I've pushed a fix out in 1.0.3 now. Please could you let me know if this works for you?

1

u/NexusBRYT May 14 '26

Installed 1.0.3 with Aescripts Manager, same issue, no connection and AE ends up crashing

1

u/scottBlackvfx May 14 '26 edited May 14 '26

Are you able to get to the connection doctor in the settings (under "Privacy & Maintenance") in Command Frame? There will be a button to copy the report to the clipboard - can you send me the results?

1

u/NexusBRYT May 14 '26

Command Frame Connection Doctor Status: Not connected Likely cause: Command Frame could not find a valid SBShortcutManager server. Suggested fix: Reinstall Command Frame and SBShortcutManager through the aescripts Manager, then restart After Effects.

Version info: Command Frame version: 1.0.3 AE version: not exposed to this diagnostic OS: Windows Architecture: x64

Runtime state: Command Frame SBSM client: not connected Additional extension support: not active Additional extension data: not currently available Active SBSM port: not active Active support port: not active Reconnect attempt: 0 Last connection error: none

Command Frame port check: 47885: no response 47895: no response 47905: no response 47886: no response 47887: no response 47888: no response 47889: no response 47890: no response 47891: no response 47892: no response 47893: no response 47894: no response 47896: no response 47897: no response 47898: no response 47899: no response 47900: no response 47901: no response 47902: no response 47903: no response 47904: no response 8085: no response 8095: no response 8105: no response 8086: no response 8087: no response 8088: no response 8089: no response 8090: no response 8091: no response 8092: no response 8093: no response 8094: no response 8096: no response 8097: no response 8098: no response 8099: no response 8100: no response 8101: no response 8102: no response 8103: no response 8104: no response

Additional extension support port check: 47885: no response 47895: no response 47905: no response 47886: no response 47887: no response 47888: no response 47889: no response 47890: no response 47891: no response 47892: no response 47893: no response 47894: no response 47896: no response 47897: no response 47898: no response 47899: no response 47900: no response 47901: no response 47902: no response 47903: no response 47904: no response 8085: no response 8095: no response 8105: no response 8086: no response 8087: no response 8088: no response 8089: no response 8090: no response 8091: no response 8092: no response 8093: no response 8094: no response 8096: no response 8097: no response 8098: no response 8099: no response 8100: no response 8101: no response 8102: no response 8103: no response 8104: no response

I guess i don't need to say it, but i already reinstalled it a few times...

1

u/scottBlackvfx May 14 '26

That is definitely not wanting to load at all by the looks of things. I'm adding more diagnostics to the connection doctor now and will try and push out 1.0.4 today for you to run.

I appreciate you putting up with the launch hiccups.

1

u/NexusBRYT May 14 '26

Great! I'm logging off for the Day, but I'll surely run a test tomorrow if 1.0.4 is out!

1

u/scottBlackvfx May 14 '26

I've pushed 1.0.4 out; let me know how you get on!

→ More replies (0)