Add validator in folder creation when provided resolution does not match existing one.

[antirotor]

Is there an existing issue for this?

• I have searched the existing issues.

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

This PR #1255 added ability to override the resolution settings. But that needs to be done in the settings. You can either not-override or select the override.

There should be third mode - "use source resolution" and that will override the resolution using resolution data coming directly from the source. It might be that this cannot be implemented in ayon-core and must be done in hosts themselves and if so, we should think how to combine functionality so it doesn't live in two places.

User story:
Artist wants to use whatever resolution is on the input. For example in Nuke, you want to use whatever is set on Read to be used on Write.

How would you imagine the implementation of the feature?

When option on Choose Explicit Resolution is set to use source resolution, that one should be used. Maybe unified collector collecting instance source resolution can be used.

Maybe we should also change the plugin name because using source resolution is sort of implicit override?

Are there any labels you wish to add?

• I have added the relevant labels to the enhancement request.

Describe alternatives you've considered:

No response

Additional context:

No response

[BigRoy]

I'm so lost here. Isn't using the source resolution the default behavior? I can throw whatever into tray publisher or from any DCC at any resolution (regardless of how my shot or task is set up) and have it output the resolution I want. (I might need to disable an optional resolution validation, but still)

So what's different here?

Or... is this PURELY about editorial and not related to anything else?

[antirotor]

Or... is this PURELY about editorial and not related to anything else?

not sure if purely but yes

[antirotor]

But it is actually good point - aren't we now just handling the resolution on so many places?

[rdelillo]

TBH I'm also quite confused about the requested work here.

I mean I understand the proposal about adding a "use source resolution" entry in the resolution override implemented with #1255. But that sounds like a heavy change across all of our publishers.

Because looking back at the original request, client only mentions "editorial publish" and especially Hiero saying that it already works in Flame. The only thing I can think of is the Source Resolution parameter that allows to create the Shot product using the hero track clip source resolution.

But this feature already exists in both Hiero, Flame and Resolve.
Is it what the Client is talking about ?

in Flame:

in Hiero/Nuke Studio:

This thing is only exposed at "Creator" time, so one thing we could definitely do is expose it as well in the shot product instance within the publish tab. But is that the request ?

[JoseCovaOS]

Hi guys, trying to shed some light on this topic as it's a request from us (Orca).

So the issue the editorial department is facing is that they want to be able to set the ftrack attributes Resolution Width and Resolution Height of the Shot they create when publishing a plate to be the resolution of that plate (the main one, other plates shouldn't be considered).

This is because in some projects, we've had to deliver some EXR's to the same resolution as it's shot main plate. What we were doing right now is:

• Manually change this value in ftrack (shot level).
• Ask the comper to run Nuke action set resolution.
• Comper renders (we've also disabled the validator for resolution so it doesn't fail).

It would be good if we could have a project setting that if enabled, it would gather resolution from the plateMain and during Hiero publish, set these attributes to the created shot. Also, we would like to have a per instance override in case we do not need to do this for all the shots in a project but only to a few.

Hope my explanation helps.

[rdelillo]

Just confirming the work to be done via this issue:
We have some options in the Editorial DCCs (Resolve, Hiero and Flame) to create new shots with resolution set on the hero plate product. This is working however it could be improved in different way:

• currently this option is not exposed on the shot product instances in the Publish tab, it should.
• also if the targeted folder already exists with a different resolution, currently nothing will happens. It should trigger a validator with a suggested repair (set the shot resolution or disable source resolution)