• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
12

Have a central location for scripts & presets like the MediaCore is for plugins

Community Beginner ,
Nov 03, 2022 Nov 03, 2022

Copy link to clipboard

Copied

The MediaCore folder is pretty handy to keep plugins between versions when upgrading versions. But scripts & presets still need to be copied manually (which is quite annoying). 

 

If there's a location like MediaCore where all AE versions can pull plugins from, why shouldn't there be such a location for scripts & presets? My biggest pain point in upgrading is "all" the manual work involved, which feels strange since updating itself is real easy with the CC app. 

Idea Acknowledged
TOPICS
Workflow

Views

161

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Pinned Reply

Adobe Employee , Nov 03, 2022 Nov 03, 2022

Thanks @Paul van Sommeren and @davidarbor! The migration pain is very real, as I can personally attest from my days as a motion designer. I could see this being a possible alternative solution to the problem described here in regard to the current lack of migration. A central location for scripts and presets would solve this issue for those who utilize it.

 

Would you see your proposed central location as optional, as the MediaCore folder is, or would you expect it to be the default? Part of the

...
Status Acknowledged

Votes

Translate

Translate
3 Comments
Community Expert ,
Nov 03, 2022 Nov 03, 2022

Copy link to clipboard

Copied

As a regular user of the public beta, this is something I've taken for granted for quite some time now. I haven't had to migrate scripts in ages since that file path there never changes. Often, though, when I use the release version I have to do some sort update or script management, so big +1 from me.

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Nov 03, 2022 Nov 03, 2022

Copy link to clipboard

Copied

Thanks @Paul van Sommeren and @davidarbor! The migration pain is very real, as I can personally attest from my days as a motion designer. I could see this being a possible alternative solution to the problem described here in regard to the current lack of migration. A central location for scripts and presets would solve this issue for those who utilize it.

 

Would you see your proposed central location as optional, as the MediaCore folder is, or would you expect it to be the default? Part of the challenge around a feature like this is the shift in the existing paradigm, which can be confusing for some, and sensible defaults can either help or hinder the transition.

 

Thanks again for your input,

- John, After Effects Engineering Team 

Status Acknowledged

Votes

Translate

Translate

Report

Report
Community Expert ,
Nov 04, 2022 Nov 04, 2022

Copy link to clipboard

Copied

LATEST

You're right, any solution could be messy. I can count the number of people on one hand who have said they would prefer the existing paradigm over a global location, so I'm all for ripping the band-aid off and doing this quickly.

 

One way that might not be as disruptive is if a global location is the new default, but the current location still works just fine. This allows any dev that uses an installer for a script (which I'm sure are few and far between, but they do exist) to not have anything break. Then it also allows bigger names like Aescripts to update their installer app, throw up a nice big notification explaining this wonderful change, and give the user a pref to install all scripts to the new global location going forward. For bonus points, it might be neat if you all offered a feature to migrate scripts from the local to global folder (could be executed from "Preferences > General" or "Preferences > Scripting & Expressions", expose that in the API, then aescripts could offer the official migration option to their users.

 

Just spitballing, but I'd rather see a quick change than a painfully slow one.

Votes

Translate

Translate

Report

Report