Trigger location based on asset type?

[Andriy Pogribniy]

How can I setup file publishing to different locations based on type?
For example, I want one location for 'Render', another for 'Audio' and standard location for everything else.

[Lorenzo Angeli]

Hi @Andriy Pogribniy

There are various way you can archive this .

The first is to write what I'd call a proxy location.
Such an object would have as input a set of destination locations and the methods such as add_component, remove_component , get_component_availability, etc...
would contain the logic to define where the data would be saved depending on the rules you decide.

Another option would be to customise connect publisher widget to allow a location selector.
if you want to take inspiration , there's an old PR on bitbucket which implements it, but should be ported over the new publisher plugin.
https://bitbucket.org/ftrack/ftrack-connect/pull-requests/281

hope it helps.
L.

[Andriy Pogribniy]

So the location description itself has no mechanism to trigger itself or not, based on type of request?
What's the reason of having several locations, if I can't switch them interactively or automate their selection
without mumbo-jumbo?

[Lorenzo Angeli]

Hi @Andriy Pogribniy
ftrack supports any number of locations a the same time but locations by default do not contain any logic on what goes where ,unless you customise the location itself or the tool that uses them as described above.

The session by default will pick up the one with higher priority and use that but you can always change (when using api) the destination location at publish time without any problem. 

You can find more information on how location works also in the api documentation.
Hope it helps.
L.
 

[Andriy Pogribniy]

Speaking short, there's no working solution to do that. OK