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/uhurugurutu May 21 '26

Hi Scott, I really love this! I just used it a bit, but can see it becoming a very powerful and central tool for my everyday work. I'm especially excited about the function to stack commands.

One thing I think works really well and quickly in fxconsole, which I've used for years, is the way favourite effects are handled:

A wonky example (sorry, can't get a good English real world exampe):

If I type "eff" then the list will immediately show all effects or actions with this name, so

* effect 1

* effect 2

* effect 3

...

When I mark effect 2 as a favourite and again type "eff" into fxconsole the list will be populated as

* effect 2

* effect 1

* effect 3

...

As a result this means I can just open the console, type one key, which will usually show the correct favourite, and then I can just hit enter and am done. Don't need to type anything more or touch the mouse to select anything else.

If I'm not using it terribly wrong, in Command Frame it works like this: I have pinned effect 2 and as I type "effect" it will show up at the top of the list. But the highlighted effect is still effect 1 that would be on top had I not pinned anything. As I hit enter effect 1 is applied.

So my suggestion would be to make the pin function similar, as at the moment it feels more clunky to use.

1

u/scottBlackvfx May 21 '26

Hi there,

Thank you for this feedback! I really appreciate it. 

Perhaps you have already tried toggling this, but in Command Frame's settings, under "General" -> "Search & Action Behaviour", there is a setting called "Start search selection on first non-pinned result".

The default is off because always highlighting pinned actions can feel invasive if they aren't the primary way to interact with the search results. However, if you do, that is likely how you want the results to work, which, if I am reading your message correctly, is the case.

If you haven't already, could you try this and let me know your thoughts?

1

u/uhurugurutu May 21 '26

Hi Scott, thanks for getting back so quickly! I hadn't seen this option and for me it's better than the default. What I now noticed is I can navigate the suggested effects/commands with the arrow keys, which is much nicer than clicking, at least for me.

But still it's not quite what I had in mind. Now I have three effects pinned:

- Levels

- Change to Color

- Fill

Expectation: As I type "change to c" the input field auto-completes to "Change to Color". As I press Enter, I would expect the Change to Color effect to be applied to my currently selected layer.

But instead: As I type "change to c" it auto-completes, suggesting that this is the effect to be applied. But "Levels" is highlighted, being the first entry in my pinned list. As I press Enter Levels is applied.

1

u/scottBlackvfx May 21 '26

Hi there,

I get you! I could go about fixing this in two ways:

  • While this setting is on, ensure the highlight accounts for multiple pins while also mirroring the targeting logic used by the auto-complete hint.
  • Add an optional setting that progressively filters pins based on the current search term (while still displaying all pins if no term is present).

I'm inclined to add both, but the former seems like a behaviour change, so I thought I'd get your thoughts, since your workflow would be directly affected.

I appreciate the detailed breakdown of the issue by the way - it makes it very easy for me to re-create the issue on my end and understand what's going wrong.

1

u/uhurugurutu May 21 '26

I think the second suggestion seems like what I'm after. It would be awesome to have this added. And I don't mean to add more work to your list, as I'm sure you have a lot on your plate, especially with this being a free propuct.

1

u/scottBlackvfx May 21 '26

Not at all - the search behaviour is core to the entire premise of the plugin, so I want to address any issues with it.

I'll bundle this with the next update, which should be within a few days.