we recently got our studio subscription and want to switch to AYON tools where possible.
So right now, our plan is to get rid of our internal delivery/transcoding system and use
the AYON batch delivery tool in combination with the slater.
So far, I got the delivery tool up and running with a few questions remaining, but the slater does not work yet or I do not know how to configure that addon properly:
Delivery Tool
Is there a way to modify the name of the newly created delivery product via anatomy templates?
It looks like the name “deliveryProcessXXXTranscodingYYY” is hardcoded right now.
Slater
Possibly a bug / not implemented yet, but the slater does not take the pixel aspect of the source representation into account and therefore produces a different scaled slate with aspect ratio 1 that does not match visually with the appending sequence (if aspect ratio is 2 for example)
Slater
Is there a way to get version data / attributes and use it in the slater fields?
For example, we have two separate fields on the version, clientSubmissionComment (Text) and clientSubmissionIntent (Select) that we modify/set during review or in a list to prepare for delivery.
But it seems not possible to use any version data except for the comment in the slater yet.
Delivery Tool / Slater
We use nuke templates for transcoding and sometimes we get
a specific slate preset (nuke group) delivered by the client that we need to use.
Is it possible to have this slate / a custom frame prepended to the sequence during the transcoding process already?
It looks like the nuke script does not render frames outside the given frame range for now
and even I got it to work, there might be more issues following during the publish process.
(Which cold be solved with a custom plugin)
It would also mean that I need to find a way “fill” the data in the custom slate,
but that is how we have been transcoding until now and it should not be a problem to adapt our current python framework to do so with AYON during transcoding.
Any help or advice is greatly appreciated,
thanks!
Product name template: this one is hard coded. Please make a request on Feedback portal to make it configurable in Product name profiles setting ayon+settings://core/tools/creator/product_name_profiles
Yes, this is the expected behavior. I won’t call it a bug or not implemented feature but this was the original feature request.
It’s worth mentioning that the original use case here is in editorial publishing where shot, task, and published representation have the same info.
I submitted an issue for it.
I believe you are referring to the available template keys in the slate. in this section Supported Template Keys in a Slate layout on user docs, you can find the supported keys.
In Job definitions below Transcoding preset in batch delivery addon, you can select to have the output with thumbnail and slate.
Yes, I meant the product name template. I will submit a request as suggested.
Thanks for submitting the issue. I will keep an eye on future updates.
Yes exactly. Unfortunately, there is no (source) version entity data available right now.
Maybe I can figure out a way to write a custom data collector/extractor and use
custom tokens to get the data we need.
A first test seems very promising using srcVersionEntity from instance.data[“offloadedProcessingData”] and update instance.data[“customData”],
so at least the data is available during slate generation.
I might create a request for src version attributes as well,
so it is also included in the preview for the slate generation and also not depending on customData.
Yes, that’s what I tested - but I was referring to a custom slate frame that is generated in Nuke and prepended to the representation files - not to the extract slate frame (with the slater) itself.
The reason is that we can continue using our existing Nuke slate group until the AYON slater meets our needs and can eventually replace the custom solution.
But it does not seem to be supported right now, so I will try to figure out how to solve this
using custom plugins where possible.
