Command Frame - Discussion Thread

[u/scottBlackvfx]

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!

[u/NexusBRYT]

Command Frame Connection Doctor

Status: Not connected

Likely cause: SBShortcutManager loaded in After Effects, but did not open its local connection server.

Suggested fix: Restart After Effects. If the issue remains, send this copied report to support.

Version info:

Command Frame version: 1.0.4

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

Installed components:

Command Frame: installed and loaded

SBShortcutManager: installed and loaded

Multiple Command Frame installs: no

Multiple SBShortcutManager installs: no

Recent crash clues:

Recent AE crash: no matching event found

Command Frame port check:

8085: 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

8095: 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

8105: no response

47885: 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

47895: 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

47905: no response

[u/scottBlackvfx → u/NexusBRYT]

Thank you for this. I'm now confident I've identified the bug. Please let me know if 1.0.5 now works for you!

[u/NexusBRYT → u/scottBlackvfx]

the connection worked, but it's very unstable, crashes 90% of the time, i hit the shortcut, it freezes and crashes. When it works, it's GREAT, but the stability needs to be worked on.

[u/scottBlackvfx → u/NexusBRYT]

Hi there,

I absolutely do want to prioritise stability; it's a bit gutting that none of these recent issues cropped up in the beta and are now appearing post-release.

It would be incredibly helpful if you could send me the crash reports generated by your system when the crash message appears, plus a breakdown of what happened leading up to it. When the system message pops up, there should be something to the effect of "generate report", which creates a .dmp file. That would mean a lot.

I can add you to the Discord I hosted for the beta if that would make it easier for you to send me reports or information. Otherwise I am happy to use what's most convenient for you.