Search the Community

Showing results for tags 'publishing'.

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
  • Connect and plugins
    • General discussion
    • Connect package releases
    • Feature requests
    • Help
    • Connect plugins releases
  • Reviews
    • General discussion
    • Feature requests
    • Help
  • 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 7 results

  1. Hi there, I recently switched away from Ftrack to Shotgun because the publishing tools seems so broken and limited in Ftrack. Shotgun does it much better, but the program as a whole is terrible and a pain to use. Ftrack is far superior when it comes to ease of use - with the excepting of publishing. I quickly switched back to Ftrack and now have to figure out a solution to my issue. Both programs seem to have terrible documentation and I can't figure this out. We have a small studio and I am a VFX supervisor. We have a pipeline that works perfectly for a studio our size and I don't want to mess around with it too much. My issue is that Ftrack seems to be be very rigid when it comes to publishing files. It wants to create it's own file structure which in my opinion is a complete disaster. I'm really not sure how anyone works this way. I want the artists to be able to submit shots for review that retain the naming convention of the shot they submitted, and retain the path on our server to the shot. I want to open a group of shots submitted throughout the day in RV - launched from Ftrack and review, annotate and make notes from within RV (on the original shots) that then get transferred to the shot tasks for the artist to see. Pretty straightforward. What I don't want is for Ftrack to copy the shot to some other location on my server, place it in a folder within a folder within a folder within a folder within a folder and rename the file "". Before I ask how I can do this, I'm just wondering if someone can just give me a straight up answer if this is even possible. We've spent days trying to solve this. There are very few but broad and unhelpful documents about publishing, but otherwise the internet seems to be devoid of any useful help on this issue. Thank you so much for your help! cheers, Mike Ritchie
  2. In the Description field, in the info tab of the assetversion published, just the last line of the artist's comment is showing up This is what was submitted by the artist as comment
  3. Hey there, I am in the process of evaluating ftrack and have some questions regarding publishing. Quite possible that I am missing anything as I am having some trouble understanding the basic principles in ftrack (coming from shotgun). I am gonna first outline what I think is the default render/publishing workflow. Gone through that in afx and nuke but I guess the workflow is similar in maya. Here the procedure in nuke: Open nuke via ftrack-connect (correct context). Nuke script is saved in an (more or less) arbitrary location. Do your work Render to another arbitrary location Attach a ftrackpublish node to the write node and publish (or is the intended way to use the publisher via the ftrack menu and the ftrackpublish-node is legacy?). During the publish the nuke-script as well as the rendered-sequence will be copied to the fileserver. - Script and image-sequence will be placed side by side into the following structure (given that the task was tied to a shot): project/sequence/shot/scriptname/version/ - The name of the script will be generic (nuke-script.nk or something like that) and thereby the version/shot/sequence will be not saved explicitly to the files but implicit in the ftrack database as well as the file structure. If theses assumptions are correct, here are some questions: is there any way to access/parse the ftrack-context in nuke? I'd rather like to use a custom write node which is automatically populated with the correct render-path (built from the task/shot/sequence etc.) on our fileserver. This is especially true for renderings running on the farm. I don't want the artists to manually navigate to the appropriate location and enter the correct filename as this is one task which should be handled by ftrack imo. the same applies to the script itself. I'd like to force the artist to save the script on our file-server (in the correct location and name) which is - as opposed to local files - backed regularly is the publish-action itself customizable? As the components (rendered sequence and script) already are in their appropriate locations on the fileserver there would be no need for any copying. Instead I'd like to only register the components and create the versions on the ftrack-server. Guess that this could be done with a custom publisher but I'd really like to let the built-in do the heavy lifting and just modify it I am quite sure that everything is possible. Just trying to figure out how much effort it takes. Best, Julian
  4. Every time I try to publish a project from Premiere, AE, or Photoshop I get a publish failure message with this in the details: LocationError: Failed to transfer component <FileComponent(ff607b92-1ac7-4c88-946a-cb099f014095)> data to location <Location("studio.central-storage-location", b302db0b-4ffa-4bef-9bb0-1209b21ee317)> due to error: Operation makeContainer failed: [Errno 13] Permission denied: 'test_josh' Transferred component data that may require cleanup: [] I'm guessing I'm missing something, but I'm not sure what. Thanks for the help!
  5. Hi I am struggling to work out how to create a new AssetVersion in the new API. I think I have to do the following: Create an Asset -- parented to the shot Create an AssetVersion -- linking to the task and asset Create the Component. Unfortunately I'm getting an error, it seems to want a context_id on the Asset, but I don't know what to give it? I have the following code: location = session.query('Location where name is "ftrack.unmanaged"').first() task = session.query('Task where id is "d4564359-2944-49d4-93fa-b11909f19ff5"').first() shot = session.query('Shot where id is "bf127242-da0b-40aa-ac19-ca793f7590e0"').first() data = { 'parent': shot, 'name':"aAsset", 'type':'scene' } asset = session.create("Asset", {}) data = { "task": task, "asset": asset, "name": "Philip Test", "version": 99, } version = session.create("AssetVersion", data) component = version.create_component( path=r"P:\a_project\series_01\sequences\025\sq025_sh040\2d\publish\v009\040_Compositing.nk", data={ 'name': 'nuke_script' }, location=location ) session.commit() And I get the following error: Traceback (most recent call last): File "C:/Users/Philips/Documents/source_code/test_project/ftrack/", line 51, in <module> location=location File "L:\script_library\pipeline\libs\3rd_party\production\ftrack_api\entity\", line 47, in create_component return self.session.create_component(path, data=data, location=location) File "L:\script_library\pipeline\libs\3rd_party\production\ftrack_api\", line 1816, in create_component 'FileComponent', path, data, location File "L:\script_library\pipeline\libs\3rd_party\production\ftrack_api\", line 1887, in _create_component location.add_component(component, origin_location, recursive=False) File "L:\script_library\pipeline\libs\3rd_party\production\ftrack_api\entity\", line 77, in add_component [component], sources=source, recursive=recursive File "L:\script_library\pipeline\libs\3rd_party\production\ftrack_api\entity\", line 249, in add_components transferred=transferred ftrack_api.exception.LocationError: Failed to register components with location <UnmanagedLocation("ftrack.unmanaged", cb268ecc-8809-11e3-a7e2-20c9d081909b)> due to error: Server reported error: OperationalError((OperationalError) (1048, "Column 'context_id' cannot be null") 'INSERT INTO asset (id, name, context_id, taskid, type_id) VALUES (%s, %s, %s, %s, %s)' (u'6220bf4b-3d0f-45cf-aa6c-45106fd49396', None, None, None, None)) Transferred component data that may require cleanup: [(<dynamic ftrack FileComponent object 54489720>, 'P:\\a_project\\series_01\\sequences\\025\\sq025_sh040\\2d\\publish\\v009\\040_Compositing.nk')]
  6. Hi Just been reading the documentation in the following link: It seems to me that the documentation misses out the `"parent": asset_parent` from the dictionary used in the creation of the asset. It mentions gathering the asset_parent in the example above but then does nothing with the variable. thanks Phil
  7. 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