Hi, I am Joseph, currently I am slowly transferring my team to AYON from our previous workflow.
I am trying to setup a file system where the artist doesnt work on the server and only the publish file goes up to keep the server clean. That’s I find site sync addon fit in place.
However, while I am able to setup the pipeline and start using it for a project. We find out that the artist couldn’t select the published file on the server through AYON workfiles UI unless the site setting is set as studio on both active and remote site.
Am I missing something here? The current resource / documentation doesnt quite to be clear on these kind of stuff yet and most of the documentation in the old post doesnt work anymore.
This use case is missing a piece of information, are your artists working from studio or from home?
From Studio
You don’t need sitesync to achieve this. you only need to configure anatomy presets where you have a work root that points to a local or shared directory and publish root that points to shared storage.
Then in anatomy preset, use {root[work]} with work templates and {root[publish]} with publish templates.
It’s worth mentioning that using local work directories may cause some confusion with workfiles tool because there’s no guarantee that v002 of a workfile on machine A is the same one on machine B.
You can use a shared work directory separate from publish directory if you want to avoid such confusion.
Use cases can be studio specific. overtime, we collect them from client and community feedback then expand docs.
Our artist is working in the studio but we actually prefer to have the artist work on their local so that the server is not populated by the workfiles that the artist created on their preferences.
So what I am getting here is that in the anatomy preset. We could set the {root[work]} to the D drive and {root[publish]} to the server? Is it possible to have the publish root point to both local and shared storage at the same time?
Sorry if i sound confused here because AYON logic is very new and is quite different from the workflow that I am used to.
Thank you for open up my mind on the anatomy setup!
Is there a cleaner way to redirect the current on going project anatomy? As I have an understanding that it is not a good thing to change the project anatomy while the project is on going.
As for publish the file to both local and shared storage.
Say I have a file that I want to publish for delivery. Previously what we are doing is we have the published file copied to another folder as a temporary master file, so whenever the file is approved, our project coordinator can just collect the files from that folder without going through all the folders in the server.
Both location is at the same shared storage actually.
Site sync could be helpful in this case perhaps? Or there is other way of doing it?
It’s not recommended to change the anatomy on going projects.
However, changing the anatomy for publish templates may not break the pipeline as each published product version knows what template used at the time of publishing. so, you can have multiple products some with {root[work]} and others with {root{publish}}.
For delivery we have a dedicated addon for it AYON Batch Delivery which supports complex delivery and transcoding presets.
Alternatively, there’s a built-in simple functionality for delivery in desktop browser which only copies the selected product version to the delivery location specified in delivery template.