Search the Community
Showing results for tags 'locations'.
Found 4 results
Hi, I added a new location and structure plugin to ftrack, to be able to save assets in our own folder structure. It works fine if I publish assets from python, however the nuke plugin seems to ignore the new location. I registered the location with the highest priority, but the assets still get published to the ftrack locations. I can't even see the location in the Import Asset dialog. Are these locations hardcoded, or did I miss something?
Hi All, I'm new to the forum and relatively new to ftrack, so please bear with me in case I'm missing the obvious here. We are looking to complete a couple of simple tasks. A] To move the ftrack file storage (assets, compressed video, reference assets) to a local file server / network drive. B] Store our master assets locally and link these to tasks / shots / asset builds in ftrack. I have ftrack connect installed so I can add a storage scenario - but this doesn't seem to do anything! I also noticed that in the ftrack settings 'Connect Location' shows as legacy. Does this mean it is going to be phased out? Or its it going to be replaced by something else? I'm a little confused with how to actually start saving files across different locations, and a lot of the documentation seems to contradict itself. Any help would be appreciated, I'm probably missing something really simple here! Best. M
It would be an excellent feature of ftrack-connect to offer a UI for registering your workstation as a location in ftrack. That way when you publish using ftrack-connect, your component paths will be managed. I assume you might also want to add a preference in the ftrack web interface that would allow or disallow this functionality from connected ftrack-connect users.
Hi I am struggeling to find existing components using a sepcific location. There is this nice getComponent () function but it takes a componentID (which I don't have). I want to know basically all components assigned to a known location. Thanks for any pointers Chris PS @ftrack-team: locations and components are very confusing for a ftrack beginners. The documenation is a good starting point. But it would be great if you could extend it, especially how to find components when they have been already created