Better frame sequence handle workflow

[johhnry]

Is there an existing issue for this?

• I have searched the existing issues and added correct labels.

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

This was discussed on the forum: https://community.ynput.io/t/publishing-plates-with-handle-and-start-end-frame/1910

Right now, when publishing a plate/pointcache/vdbcache/online or render product, it uses the CollectSequenceFrameData pyblish plugin. The issue is that it's not very clear what it does when it's enabled or not.

If publishing a 991-1111 png sequence for a shot that is 1001-1101 (start/end frame) and 10-10 (handles):

• Collect Original Sequence Frame Data enabled -> 991-1111 (duration 121 frames with 0-0 handles)
• Collect Original Sequence Frame Data disabled -> 1001-1100 (duration 101 frames with 10-10 handles)

We should have more control of what start/end frame, handle number it takes.

Suggested implementation?

@BigRoy talked about having the following combo box choices:

I have actually always wanted to make that an ENUM instead so that it could be labeled Frame Range* and have multiple methods like:

• Use frame range from image sequence or media timecode
• Use context entity frame range (folder or task)
• Set explicit frame range values (This could then expose a start, end, handle start, handle end number attribute for you to manually set if needed.)

The question is: if there's more files than the target frame sequence start/end rame, what does it do?

Describe alternatives you've considered:

No response