Custom Thumbnail and h264 file location

Is it possible to change the location where the thumbnail and h264 transcoded media are saved, too?

Some DCCs really do not like having other files in the seq folder, so we usually try to keep the folder with plates, comps, mattes, and elements clean.

I have reviewed the Extract Thumbnail and Extract OIIO Transcode configurations and do not see anything obvious.

I would prefer to have the thumbnails and H. 264s go into the parent folder.
So instead of

.\publish\plate\plateMain\v002

thumbs and h264s could go in

.\publish\plate\plateMain

That folder would then hold a h264 and thumb of every version, which is also ok and preferred.

Thanks

Just to confirm I got it correctly, Do you want to save the published review representation in a different path from the other published plates representation?

Yes, that is right. And in this instance, the different path would be the same path, but one directory up. The root of the plateMain in this example.

It’s possible to mix and match template name profiles: ayon+settings://core/tools/publish/template_name_profiles where you can tell AYON to use anatomy template x with the product y.

But, I’m not sure if it’s possible to use anatomy template x for representation z within the product y.

Somehow I have a feeling this request overlaps a bit with the request from here where you want to heavily influence the output structure of the resulting representations.

Like Mustafa wondered, the AYON template customization possibilities are currently “per product” and not down to each individual representation. Which of course makes it hard to nudge them into individual folder structures in its current templating design.

Not to say that it never could, but I think some changes would be needed to get to supporting that. (Tagging @philippe-ynput for visibility)

However, I also want to bring up that it seems you’re heavily trying to design the “published” file structure for something to navigate through and I wonder why that is. The aim would be that one never or rarely would need to go those files in explorer - and instead work towards making the files accessible, from anywhere in the pipeline in the means that you need.

Which leaves me to the question: why do you need it structured that way?
Preferably getting to the previews is right at your fingertips, without ever needing to open an explorer and browse to a folder manually.

Also, AYON Web UI shows reviews in webplayer as outlined in Reviewables

In addition, AYON Server supports openassetio/USD URIs which can be used to retrieve data from AYON server without the need to care about the file structure at all. OpenAssetIO Beta Release Now Available - ASWF

It is true. I can tell a lot of development went into this specifically. My initial reason for this is that in the past, we have seen issues with some DCCs that would have a problem loading a sequence if there were other files in the folder, but that was an issue we had years ago, and it might be less of a problem these days, especially with these tools.

If it were an easy switch that could be flipped, I might consider doing it. However, since it seems more difficult and less necessary, I will continue with the current approach and see if we encounter any issues.

Thanks for the thoughtful responses!
Fred