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-973_Resolve: auto OTIO timeline reviewing workflow #34

Open
ynbot opened this issue Oct 1, 2024 · 1 comment
Open

AY-973_Resolve: auto OTIO timeline reviewing workflow #34

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

Comments

@ynbot
Copy link
Contributor

ynbot commented Oct 1, 2024

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

From client:
Create Resolve auto timelines for review based on Ftrack lists. (Plate, latest version -x, latest version, both review and main.) From any context really, most probably through ftrack as an action, launch a resolve session that automatically creates a timeline, imports every plates in the list, import
latest version, import x versions before latest (to be configured or as a post script on request). This needs to be done for all representations present in versions (so we can be fast in reviewing let's say dnxhds instead of exrs if we just need to check the movs.)

How would you imagine the implementation of the feature?

No response

Describe alternatives you've considered:

No response

Additional context:

()
(might be a private channel)

This issue was automatically created from Clickup ticket AY-973

@ynbot ynbot added sponsored This is directly sponsored by a client or community member type: feature Adding something new and exciting to the product labels Oct 1, 2024
@mkolar mkolar removed the type: feature Adding something new and exciting to the product label Nov 5, 2024
@jakubjezek001
Copy link
Member

The issue was originally waiting for implementation of ynput/ayon-core#44. Now we have to design the other phase of the feature. Optimally it would be great if all the actions would be driven from AYON and not from FTRACK but since we are not supporting Lists in AYON https://github.com/ynput/AYON-Epics/issues/55.

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

4 participants