Search the Community

Showing results for tags 'components'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Company news
    • General announcements
  • ftrack Studio (main app)
    • General discussion
    • Feature requests
    • API
    • Help
    • Actions and Widgets
    • ftrack Go
  • ftrack Review
    • General discussion
    • Feature requests
    • Help
  • Connect and plugins
    • General discussion
    • Connect package releases
    • Feature requests
    • Help
    • Connect plugins releases
  • Advisory Forum
  • Tech preview
    • API
    • New integrations
    • Studio overview
    • ftrack Review


There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 5 results

  1. Is it possible to choose the root directory on a per project basis? We have a studio with multiple file storages paths, and we want some projects to go on one file storage and other projects to go on a different file storage. For example: City1 - Storage1 - Storage2 City2 -Storage1 -Storage2 If I want to work on Project1 in City1, Storage1 and City2, Storage1, but I want to work on Project2 in City1, Storage2 and City2, Storage2. What's the best way to do this?
  2. Philip

    Sharing Components

    HI Just wondered, is it possible to share components between asset versions? I'm pretty sure I was doing this and it was working, however, I'm noticing now that its not working and I'm questioning my a sanity as to whether it ever was. If I create a Component (unmanaged location) on a AssetVersion all is good, but if I try to add the same Component to another AssetVersion, it simply transfers it. sourceAssetVersion = session.get("AssetVersion","cf0e384c-606d-4bc1-9fdd-b7983562bc32") destAssetVersion = session.get("AssetVersion","d9fdddf7-d27d-45ec-8bfb-1c95ecf97afa") destAssetVersion['components'].append(sourceAssetVersion['components'][0]) session.commit() Is this normal behaviour? thanks Phil
  3. Hi I am trying to register a component, and I am getting the following error: Failed to register components with location <Location("ftrack.server", 3a372bde-05bc-11e4-8908-20c9d081909b)> due to error: Server reported error: IntegrityError((IntegrityError) (1062, "Duplicate entry 'ee47fa1c-13d3-11e3-93e0-f23c91dfaa16-scene_01_025_Compositing-03' for key 'asset_Asset.typeid_key'") 'INSERT INTO asset (id, name, context_id, taskid, type_id) VALUES (%s, %s, %s, %s, %s)' (u'fac36b79-29c7-42e4-8933-afa820bf0754', 'scene_01_025_Compositing', '0311ec39-7af3-48e1-8509-c8b3b0916c86', None, 'ee47fa1c-13d3-11e3-93e0-f23c91dfaa16')) Transferred component data that may require cleanup: [(<dynamic ftrack FileComponent object 1850849152>, 'f6ecce05-3213-4f40-b1f1-e9b31b3b10c9')] The trouble is I'm not quite sure what exactly, the error is telling me. It seems that there is a duplication of data, where that is not allowed. The entry seems to be the combination of the component name and its potential ID, being added to the key asset_Asset.typeid_key, which confuses me, because I thought components were added to the AssetVersion and not the asset directly. Can somebody help explain what this error is telling me. thanks Phil
  4. Hey ftrack, I saw that this had been brought up in an old post but I didn't any much movement on it so I thought I would re-post the request. It would be great to have the option to match the ftrack published version with the actual version of the file or at least have the option to enter a version number manually as a fallback. If you're also publishing multiple components, it would be great to have a check in there to make sure that all your filenames share the same version number. I know this is possible thru the API and building a custom publisher, but thats not really an option for our small studio at the moment. I would like to see this feature added to ftrack-connect as I'm sure many other people would. -ak
  5. Hi all: Been working on ftrack 3ds max integration for our studio for the past few months, so finally getting into actions/events/etc. Just to get this place started, here's an Action I made that I have no idea how everyone else on ftrack works without; the ability to download all Components at once from an AssetVersion. Ideally, I'd like to be able to integrate a Tkinter/Qt UI for choosing the file directory to save files to, but right now that doesn't seem to work, and I can't figure out why (since nothing gets piped to stderr/stdout when I execute a simple Tkinter fileDialog.askDirectory()) Actually, ideally I'd love to be able to zip the components on the server and generate a download link to that, but I can't figure out how to get boto (S3) to do that. So for now I just multithread the downloads. You will need to modify this action to suit your needs (Since you obviously won't have a frostburnS3Accessor class, which really is just a subclass of ftrack.S3Accessor with a few additional methods such as getting the resolved URL of a key on S3. Just replace all of that with whatever type of Accessor that your studio is using) Hope this helps get the ball rolling in here!