Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AY-7009_Make Resolve shot publisher support subfolder hierarchy #39

Open
ynbot opened this issue Oct 21, 2024 · 0 comments
Open

AY-7009_Make Resolve shot publisher support subfolder hierarchy #39

ynbot opened this issue Oct 21, 2024 · 0 comments
Assignees
Labels
sponsored This is directly sponsored by a client or community member

Comments

@ynbot
Copy link
Contributor

ynbot commented Oct 21, 2024

Please describe the enhancement you have in mind and explain what the current shortcomings are?

We would like to be able to publish shot with deeper path hierarchy than what is supported by current Create Publishable Clip creator in Resolve (more detail on the Discord link).

Currently supported /shots/episode/sequence/renamed_shot
Not yet supported /shots/sub_shots/[sub_sub_shots...]*/episode/sequence/renamed_shot

We would need to tweak ayon-resolve so that deeper paths are supported. This implies work on the Shot parent hierarchy and/or folder entries.

How would you imagine the implementation of the enhancemenent?

No response

Describe alternatives you've considered:

No response

Additional context:

link to discussion on Discord
(might be a private channel)

This issue was automatically created from Clickup ticket AY-7009

@ynbot ynbot added sponsored This is directly sponsored by a client or community member type: enhancement Improvement of existing functionality or minor addition labels Oct 21, 2024
@dee-ynput dee-ynput removed the type: enhancement Improvement of existing functionality or minor addition label Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sponsored This is directly sponsored by a client or community member
Projects
None yet
Development

No branches or pull requests

3 participants