Editorial plugins: Plugins without hosts filters

[iLLiCiTiT]

Changelog Description

Editorial plugins have 2 variants now. One plugin variant has old filters and the order has just families filter with very targeted families filtering to just one family.

Additional info

The goal is that hosts that do want to actually use any logic from the plugins should add the family to instance. That way the host is in charge if logic from core will be triggered instead of core knowing it. That way any change in existing integrations or new editorial host should not need to change core.

This is first step, second step would be to add the families in the host integrations and last step will be to remove the old plugins, that will require to bump compatible versions in package.py.

Affected hosts

• Flame Chore: Use new editorial families ayon-flame#142
• Hiero Chore: Use new editorial families ayon-hiero#159
• Resolve Chore: Use new editorial families ayon-resolve#109
• Traypublisher Chore: Use new editorial families ayon-traypublisher#181

---

Changes in plugins

CollectOtioReview

• renamed to CollectOTIOReviewTrack
• added one plugin with family "otio.review.track"
• kept old for backwards compatibility
• 'otioClip' is NOT automatically used if there is "review" in families !!!
• 'otioReviewClips' can be pre-filled -> host integration can fill it to use otioClip !!!

CollectOtioRanges

• added one plugin with family "otio.clip.ranges"
• kept old for backwards compatibility

CollectOtioSubsetResources

• renamed to CollectOTIOProductResources
• added one plugin with family "otio.clip.resources"
• kept old for backwards compatibility

ExtractOTIOFile

• added one plugin with family "otio.timeline.workfile"
• kept old for backwards compatibility

ExtractOTIOReview and ExtractOTIOTrimmingVideo

• both just removed hosts and changed families to "otio.trim.review" "otio.trim.video"
• the families are added by CollectOTIOProductResources

Testing notes:

Nothing should change with this PR.

Someone should look at the new families and make sure it makes sense.

The way how host integration tells core what to use for track review changed too.

We should try each host in this combinations:

• core develop & host develop - to validate everything works
• core PR & host develop - a debug log in each old plugin will be visible at the start
• core develop & host PR - nothing that can be visualy validated
• core PR & host PR - a debug log should not be visible

[rdelillo]

I've tested it all, and all combinaison in Flame. It works great including trimming and review.

Just added some additional debug logs.
Also see my comment regarding the remaning review family usage in collect_otio_review.

[iLLiCiTiT]

Logic of CollectOTIOReviewTrack was changed to be different from original CollectOtioReview. It does not auto-use otioClip for review if review track is not set and there is "review" family in families, instead the host can pre-fill "otioReviewClips" to use it.

[BigRoy]

Change to more explicit families name I think is a good improvement.

I wish we could clean up the backwards compatibility some day though. 🗡️ Because that'd make this much prettier.

[BigRoy]

Code-wise looks OK to me. Needs more testing across various integrations for editorial + also testing for backwards compatibility there.

[iLLiCiTiT]

@rdelillo could you find time to test some of the other hosts too?

[rdelillo]

Update, all good for Resolve as well. The debug log when when plugins are skipped helps a lot.