How to add frameStart and frameEnd to template keys?

RdMaple · 19 February 2024 09:41

I want use frameStart and frameEnd in wokefile template,so i need add this task attributes to template key,how can do this?

mustafa_jafar · 6 March 2024 19:27

This question was asked before somewhere on forums, discord or GH… I can’t remember… But, Here’s what I still remember:

One can wonder which frame range to add to the template keys that will be used later to generate the work-file name…
Should we use the frame range in the asset info on AYON server ?
Or, Should we use the actual frame range used inside the work-file ?

So, it’s not advisable to use frame start and end in file names as it’s not guaranteed to have the exact same frame range in the work-file. Therefore, we should use the work-file as the source of truth.

Maybe @BigRoy has a word on that.

Also for reference, I hit the same idea you described in your post but in a different situation when I was implementing Update Houdini Vars on context change | AYON Docs. Introduced in OpenPype PR #5651.

I ended up making the following function to add assetData to template keys.
assetData are computed from the current running DCC session.

github.com

ynput/ayon-core/blob/7bf7780dd6f2c0990954102dc2cc46e3800f3584/client/ayon_core/hosts/houdini/api/lib.py#L830-L866


      
          def get_current_context_template_data_with_asset_data():
              """
              TODOs:
                  Support both 'assetData' and 'folderData' in future.
              """
          
          
    context = get_current_context()
              project_name = context["project_name"]
              asset_name = context["folder_path"]
              task_name = context["task_name"]
              host_name = get_current_host_name()
          
          
    anatomy = Anatomy(project_name)
              project_doc = get_project(project_name)
              asset_doc = get_asset_by_name(project_name, asset_name)
          
          
    # get context specific vars
              asset_data = asset_doc["data"]
          
          
    # compute `frameStartHandle` and `frameEndHandle`

This file has been truncated. show original

mustafa_jafar · 6 March 2024 19:31

I had tweaked your post title a little if you don’t mind.
Feel free to change the title if you think it’s not relevant.

RdMaple · 15 March 2024 01:50

Many Thanks,I will take a look at this!

RdMaple · 2 April 2024 05:26

Hello, mustafa ! What I need to do like the image?

mustafa_jafar · 2 April 2024 07:54

As far as I know, you can setup your work file name templates in project settings.
Find available template keys here.

Then you can tell AYON to use your name templates in your studio settings or project settings.

Studio Settings	Project Settings
image.png2130×1132 186 KB	image.png2130×813 88.8 KB

If I got you correctly, then the only way would be to add these specific houdini env vars to the available template keys here so that you can use them in your work file naming templates.

tbh, I’m not sure about how to technically implement such a feature.

Also, this should be discussed from pipeline management wise because allowing more keys can have negative effect as your work file name may tell false info about your work file. e.g. adding frame start and frame end to template keys can give false info if the work file contains different frame range.

Maybe @iLLiCiT can tell us more.

RdMaple · 2 April 2024 08:01

Thank you, now I understand!