Jump to content

Components paths quick question


Recommended Posts

Hi,

 

I am publishing a components from a Windows workstation. I have something like : \\EIGHT-JOB6\job6\FILM....

The Flame is a Linux workstation. Obviously, \\EIGHT-JOB6\job6\FILM... doesn't exist. But /mnt/job6...

So when people watching components on a linux workstation, all path are wrong.

There is something to manage this (without to duplicate components paths) ?

 

Thank you,

Damien

Link to post
Share on other sites

To publish, we use custom python like :

asset = assetOrShot.createAsset(name=assetName, assetType=assetType, task=task)version = asset.createVersion(comment=comment, taskid=taskId)version.set('version', versionPath.versionNumber)version.createComponent(name=filePath.componentName, path=filePath.absolutePath)asset.publish()

Currently we didn't manage any location. So this is the default one i think.

 

Could you give some more information on how you publish; our Connect publisher or custom tools? What location are you using, custom ones or built in?

Link to post
Share on other sites

Hi Deex,

 

When you use version.createComponent without passing in your own location it will default to the ftrack unamanged location. When adding components to this location the file paths are saved as is and will be wrong on another OS if it is not the same mount point. 

 

To solve this you could use the ftrack Connect location which is a managed location so any data here will be copied to this location. It is only available in the legacy api at the moment. The connect location uses the disks configured in System Settings > Advanced > Disks. On the projects you have some settings (under Storage) to set the disk and which folder the project should be saved in. That allows you to do cross-platform publishing. 

 

Or you could setup your own location with different disk accessor mount points per OS. Here is a tutorial for locations:

http://ftrack.rtd.ftrack.com/en/latest/developing/locations/tutorial.html

 

This will then require you to make your location plugin available in the different integrations.

 

We are working on easier configuration for locations. The idea being that you can configure publish locations more easily through the ftrack UI.

Link to post
Share on other sites

Thank for your answer Mattias.

I will work on this.

 

Hi Deex,

 

When you use version.createComponent without passing in your own location it will default to the ftrack unamanged location. When adding components to this location the file paths are saved as is and will be wrong on another OS if it is not the same mount point. 

 

To solve this you could use the ftrack Connect location which is a managed location so any data here will be copied to this location. It is only available in the legacy api at the moment. The connect location uses the disks configured in System Settings > Advanced > Disks. On the projects you have some settings (under Storage) to set the disk and which folder the project should be saved in. That allows you to do cross-platform publishing. 

 

Or you could setup your own location with different disk accessor mount points per OS. Here is a tutorial for locations:

http://ftrack.rtd.ftrack.com/en/latest/developing/locations/tutorial.html

 

This will then require you to make your location plugin available in the different integrations.

 

We are working on easier configuration for locations. The idea being that you can configure publish locations more easily through the ftrack UI.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...