Jump to content

Search the Community

Showing results for tags 'publish'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • 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
    • Connect 2.0 beta
    • New integrations

Categories

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests

Found 6 results

  1. I'm just starting with Ftrack and AE, but I have a critical question (for my needs) I created a new comp, and I published that comp. The thing is that if I go to where the comp is published as a render and AE project, the rendered file is name "main.mov" and the AE project is named "after-effect-project.ae". Is there any way to make it so is named after the comp? Or is there any way to change this? Any help is greatly appreciate it. Thanks!
  2. Hi, I am currently trying to automatically get web-playable movies when publishing the sequnces of frames. I'd like to discuss whether it's an optimal way of doing this and to ask some questions. I am registering for "ftrack.location.component-added" event, get the location and the component, check if a component's "system_type" is "sequence", ask the location to provide a file system path to frames, create a movie from these frames and fire up the "ftrack.connect.publish.make-web-playable" event providing the version id and the movie file path. The movie is generated fine, the event is published but nothing new is added to my version, the movie is not there. If I try to publish these frames together with this movie manually (by selecting the movie as web-playable in the ftrack connect), everything works as expected. Any suggestions? Thank you. Regards, Andriy
  3. 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 "movie.mov". 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
  4. Hello folks, I'm trying to write a snippet to publish a file and link it to specific task and can't get it to work - is the TypedContextLink right way to do it? I've been doing quite some trial and error and getting error messages I don't quite understand ... could you point me in the right direction, please? Cheers!! import os import ftrack_api import ftrack_api.symbol #INIT SESSION session = ftrack_api.Session( server_url=server_url, api_key=api_key, api_user=api_user ) file_path = 'C:/Users/vit.sedlacek/test.mov' asset_name = "aaaW" asset_type = session.query( 'AssetType where name is "Upload"' ).one() ##------------------------------------------------------ ##musim dostat task a pak task ID project = session.query('Project where name is _PIPELINE').one() sqs = session.query('Task where project.id is "{0}"'.format(project['id'])) #sqs.first()['name'] taskID = sqs.first()['id'] task = session.get('Task', taskID) shot = task['parent'] shot2 = session.get( 'Shot', shot['id'] ) asset = session.create('Asset', { 'name': asset_name, 'type': asset_type, 'parent': shot }) asset_version = session.create('AssetVersion', { 'asset':asset, 'task': shot, 'version': 110 }) session.create('TypedContextLink', { 'from': asset_version, 'to': task }) component = asset_version.create_component( path=file_path, data={ 'name': asset_name }, location=session.get('Location', ftrack_api.symbol.SERVER_LOCATION_ID) ) asset_version.encode_media( component ) session.commit()
  5. Is there a smart way to upload in batch versions in ftrack through ftrack-connect or the browser UI? or is it just possible to publish one version at the time? And if I need to download the the component from the browser UI, is there a way to batch download multiple versions at the same time? Thanks, Luigi
  6. Hey everyone! For a while now we have been working on improved / refreshed integrations in Nuke and Maya. We’re now happy to announce the first technical preview of these tools. First out is revamped publishing tools in Nuke and Maya. At the moment we will have a limited set of workflows: Maya: Geometry, Scene and Camera Nuke: Image sequence/Render, Camera Today we will be releasing the Maya publish tool as version 0.1.0. At the moment there are several limitations of the publish tool and it should be seen as a preview of what is coming. Neither design, nor features represents what will be in the final version. Again, this is a technical preview and is not production ready. The installation process is also rather technical and requires knowledge terminal, python and git. Installation instructions can be found here: https://bitbucket.org/ftrack/ftrack-connect-maya-publish https://bitbucket.org/ftrack/ftrack-connect-nuke-publish First draft of the documentation can be found here: http://ftrack-connect-documentation.rtd.ftrack.com/en/stable/index.html We are very interested in your feedback! Especially in regards to general workflow; selecting a "publish action", multi-select items to publish, et.c. But also from a developer/TD perspective. What more requirements do you have to make it easier for you to hook in extend/enhance these tools.
×
×
  • Create New...