Settings overrides at multiple levels - Asset, Sequence, Shot, Task or Workspace

General
,
1

Hi Dev team,

I have been exploring AYON since few weeks now, it’s been amazing so far, and potentially looking for an alternative to our existing SGTK based pipeline.

Our pipeline setup is significanly based on preferences(yml files on disk) for all the actions, similar to Settings in AYON, but we have them overridable at every context(AYON’s folder) throughout the valid path, e.g Studio level, Project level, Asset Type, Asset, Sequence, Shot, Task and Workspace(per user) which gives us great flexibility to experiment or have an explicit behaviour per Context, e.g for a Ride show, where default resolution is 4k but few Sequence could have 8k resolution or something else, or has a different FPS etc…

There could be multiple way to achieve this through setting up own startup scripts or publish plugins by replicating same type of mechanism in AYON as well, but since AYON has such a robust Settings module, I’m looking for utilising it to keep the sanity and harmony of the AYON.

Thank you,
Mahendra

2

This is implemented in AYON (and its predecessor OpenPype),

  • Each item in the heierarchy either it’s a folder or a task inherits its parent attributes.
  • Each item can have overrides. They are denoted in the table with bold font.
  • You can configurte AYON server and manage (extend/hide) entity attributes.

image
image2554×1274 222 KB

3

Thanks @mustafa_jafar, this is helpful for certain types of overrides - I can see those are Attributes defined by Scope of its availability, it’s really cool!

Is there any way to overrides Settings from other addons? For e.g. I want to have Burnins settings updated for certain Sequence without having to duplicate Bundle updating those specific settings from a Addon and assign it to the Sequence? This is not just for core add-on, but in general any Settings required by Addons.

Thank you,
Mahendra

4

Addon settings is a different story.

  • we have studio scope, which is the source where all project inherit from. color code: green.
    image
    image836×111 4.23 KB
  • we have project scope, which is project specific override. color code: orange.
    image
    image662×112 2.8 KB
  • We don’t have an entity specific override e.g. overriding settings per a specific shot or asset. Instead, we have profiles within many settings which are used to target a specific folder type or task type. profiles are very strong they can target specific products published from specific task types in specific hosts(DCCs).
    image
    image1436×304 15 KB

Find more info here Settings Categories.

5

Thanks for the explanation @mustafa_jafar

What would you recommend to have such overriding mechanism - is there any possibilities of having it in AYON, or I could extend the existing Settings mechanism using custom add-on or updating the existing one?

6

What would you recommend to have such overriding mechanism

Personally, it’s hard tell.
As far as I know, it’s a combination of studio and project overrides plus profiles mechanism to target specific products, folders, and tasks within the project.

is there any possibilities of having it in AYON

Feel free to share us your feedback here and opening a request is more than welcome.
https://ayon.featurebase.app/

7

Understood, thank you for explaining me the details, much appreciated!

Cheers!
Mahendra