Leaderboard


Popular Content

Showing content with the highest reputation since 09/24/2016 in all areas

  1. 6 points
    We find the 'old' documentation invaluable for sharing and training internally. The new docs simply aren't suitable (at least not yet). We miss the ability to: Link to specific sub-sections. Access the docs offline. Navigate left and right through a topic. Link to the specific release documentation (as we are often behind latest by a few versions). Link directly to API reference (via intersphinx) from our API reference and then maintain context in surrounding docs. Please bring back the 'old' docs or at least keep updating them alongside the new ones until you can support all these features in the new docs.
  2. 4 points
    lorenzo.angeli

    ftrack_studio rez packages

    Hi all and Happy New Year ! With the experience built in the past years helping various offices setting up ftrack, I decided to wrap a rez repository where to collect all the needed bits and pieces to have ftrack_studio running as rez package. The repository can be accessed here http://git.efestolab.uk/rez/rez-ftrack for now while in development. (planning to move it later to bitbucket) The long time plan is to make this repo able to support all the needed platform and systems supported by ftrack , but at the moment I'm focusing mostly on linux. The installation is somehow tedious as the packages have to be installed in a certain order, I'm looking into a more automated system though, but is really not a priority. (check the readme to see the actual installation order) In order to make the default application work off the shelf , a custom package called ftrack_hook_override is provided, and original hooks are disabled. If you manage to install all, you can then run : $ rez-env ftrack_studio > $ ftrack_studio At the moment I'm matching the dependencies for the latest (2.7.3) version, and all the connector plugins are loaded by default (this might change later , to allow more dynamic settings). If you have any questions or issues please let me know ! L. P.s At the moment you need to have already available the basic packages such as qt, pyside and python installed as rez-packages. Please, bare in mind is currently in development, so things might be changing fast, and some packages might still be missing. If you think you can help , please do ! Below the resolution package for ftrack_studio 2.7.3 requested packages: ftrack_studio ~platform==linux (implicit) ~arch==x86_64 (implicit) ~os==Fedora-27 (implicit) resolved packages: appdirs-1.4.0 /home/efestolab/packages/appdirs/1.4.0/platform-linux/arch-x86_64/python-2.7 (local) arch-x86_64 /home/efestolab/packages/arch/x86_64 (local) arrow-0.10.0 /home/efestolab/packages/arrow/0.10.0/platform-linux/arch-x86_64/python-2.7 (local) backports_ssl_match_hostname-3.5.0.1 /home/efestolab/packages/backports_ssl_match_hostname/3.5.0.1/platform-linux/arch-x86_64/python-2.7 (local) chardet-3.0.4 /home/efestolab/packages/chardet/3.0.4/platform-linux/arch-x86_64/python-2.7 (local) clique-1.5.0 /home/efestolab/packages/clique/1.5.0/platform-linux/arch-x86_64/python-2.7 (local) ftrack_connect-1.1.2 /home/efestolab/packages/ftrack_connect/1.1.2/platform-linux/arch-x86_64/python-2.7 (local) ftrack_connect_foundry-1.1.0 /home/efestolab/packages/ftrack_connect_foundry/1.1.0/platform-linux/arch-x86_64/python-2.7 (local) ftrack_connect_hieroplayer-1.2.0 /home/efestolab/packages/ftrack_connect_hieroplayer/1.2.0/platform-linux/arch-x86_64/python-2.7 (local) ftrack_connect_legacy_plugins-1.1.0 /home/efestolab/packages/ftrack_connect_legacy_plugins/1.1.0/platform-linux/arch-x86_64/python-2.7 (local) ftrack_connect_maya-1.1.1 /home/efestolab/packages/ftrack_connect_maya/1.1.1/platform-linux/arch-x86_64/python-2.7 (local) ftrack_connect_nuke-1.1.2 /home/efestolab/packages/ftrack_connect_nuke/1.1.2/platform-linux/arch-x86_64/python-2.7 (local) ftrack_connect_nuke_studio-1.1.1 /home/efestolab/packages/ftrack_connect_nuke_studio/1.1.1/platform-linux/arch-x86_64/python-2.7 (local) ftrack_connect_rv-3.7 /home/efestolab/packages/ftrack_connect_rv/3.7/platform-linux/arch-x86_64/python-2.7 (local) ftrack_hook_overrides-0.0.1 /home/efestolab/packages/ftrack_hook_overrides/0.0.1/platform-linux/arch-x86_64/python-2.7 (local) ftrack_location_compatibility-0.3.2 /home/efestolab/packages/ftrack_location_compatibility/0.3.2/platform-linux/arch-x86_64/python-2.7 (local) ftrack_python_api-1.3.3 /home/efestolab/packages/ftrack_python_api/1.3.3/platform-linux/arch-x86_64/python-2.7 (local) ftrack_python_legacy_api-3.6.2 /home/efestolab/packages/ftrack_python_legacy_api/3.6.2/platform-linux/arch-x86_64/python-2.7 (local) ftrack_studio-2.7.3 /home/efestolab/packages/ftrack_studio/2.7.3/platform-linux/arch-x86_64/python-2.7 (local) idna-2.6 /home/efestolab/packages/idna/2.6/platform-linux/arch-x86_64/python-2.7 (local) lucidity-1.5.0 /home/efestolab/packages/lucidity/1.5.0/platform-linux/arch-x86_64/python-2.7 (local) os-Fedora-27 /home/efestolab/packages/os/Fedora-27 (local) platform-linux /home/efestolab/packages/platform/linux (local) pyparsing-2.2.0 /home/efestolab/packages/pyparsing/2.2.0/platform-linux/arch-x86_64/python-2.7 (local) pyside-1.2.2 /mnt/zeus/storage/rez/packages/rez-base/pyside/1.2.2 python-2.7.14 /mnt/zeus/storage/rez/packages/rez-base/python/2.7.14/platform-linux/arch-x86_64/os-Fedora-27 python_certifi-2017.11.05 /home/efestolab/packages/python_certifi/2017.11.05/platform-linux/arch-x86_64/python-2.7 (local) python_dateutil-2.6.1 /home/efestolab/packages/python_dateutil/2.6.1/platform-linux/arch-x86_64/python-2.7 (local) qt-4.8.6 /mnt/zeus/storage/rez/packages/rez-base/qt/4.8.6 qtext-0.2.0 /home/efestolab/packages/qtext/0.2.0/platform-linux/arch-x86_64/python-2.7 (local) qtpy-0.3.4 /home/efestolab/packages/qtpy/0.3.4/platform-linux/arch-x86_64/python-2.7 (local) requests-2.18.4 /home/efestolab/packages/requests/2.18.4/platform-linux/arch-x86_64/python-2.7 (local) riffle-0.3.0 /home/efestolab/packages/riffle/0.3.0/platform-linux/arch-x86_64/python-2.7 (local) shiboken-1.2.2 /mnt/zeus/storage/rez/packages/rez-base/shiboken/1.2.2 six-1.11.0 /home/efestolab/packages/six/1.11.0/platform-linux/arch-x86_64/python-2.7 (local) urllib3-1.22 /home/efestolab/packages/urllib3/1.22/platform-linux/arch-x86_64/python-2.7 (local) websocket_client-0.46.0 /home/efestolab/packages/websocket_client/0.46.0/platform-linux/arch-x86_64/python-2.7 (local)
  3. 3 points
    Mattias Lagergren

    Sync users with LDAP

    We've put this on our internal roadmap and aim to have something ready ~early in the new year.
  4. 2 points
    katalina-w

    Deleting import mappings

    Hi, is it possible to delete saved import column mappings? I can't figure it out if so. Kat
  5. 2 points
    Probably a big ask from a technical perspective but an incredibly useful feature in Review would be to wipe between two loaded versions in Ftrack Web Player. If wiping isn't possible, even a key press to quickly switch from version A to version B during playback would be helpful.
  6. 2 points
    Lorenzo Angeli

    2D/3D Asset Library

    Although not web based, one option I can think of would be : 1) have a project to act as library, 2) one action which allows to re migrate the assets to/from a given project . (could be a reworked version of this example: https://bitbucket.org/ftrack/ftrack-recipes/pull-requests/4) This could be extended to keep reference (as metadata or custom attribute) on where the asset originally comes from (as project when publishing back). 3) a pyside based browser (so can be used as widget in maya, nuke and any other qt based application) to act as library browser. Although requires some work, seems doable. L.
  7. 2 points
    We've been waiting on this for a while now. Do you have an expected date of when this will happen?
  8. 2 points
    Mattias Lagergren

    Upgrading MariaDB to use JSON

    Yes, we plan to upgrade to MariaDB 10.X but I do not have any dates on this yet. The JSON functionality is interesting and something to consider
  9. 2 points
    Mattias Lagergren

    Attach file in new note

    There is an article here on how to attach file to a note in the ftrack-python-api: http://ftrack-python-api.rtd.ftrack.com/en/stable/example/note.html#attachments
  10. 2 points
    ewokninja

    Time Zone Support

    Being part of a company that has users in multiple time zones it would be very convenient to be able to specify a time zone for any date/time field.
  11. 2 points
    Cool, thanks for your feedback Mattias. The more i think about this concept the more it makes sense for me and is super appealing. In a large project Producers or Lead artist don't necessarily need to assign all tasks to a specific user. The freedom of saying for example these are alle the 3D modelling tasks and i assign them to the 3D modelers group seems very nice. These tasks then appear under the 'available task' column in the my task view for everyone in this group and if a 3D modeler drags a task to another column 'in progress' for example it gets assigned to him/her directly and disappears from the 'available task column for everyone else. So they just work through the pile as they like.
  12. 2 points
    Mattias Lagergren

    ftrack Browser tabs

    Hey Erik, this is something that we're considering for the future. It could very useful if you have a lot of tabs open for different projects.
  13. 2 points
    Eric Hermelin

    Exporting Links

    Hi Ozen, hope you are well! It is possible to using a advanced query filter to filter on linked entities, below are a few examples, it is however a bit fiddly to update these query filters if you wish to iterate over a few different shots / asset builds, so it might be worth writing a tool using the api to export the information in bulk Using a Shot Query filter, show only shots that have a incoming link to a asset builds named "Monkey" incoming_links.from.name = 'Monkey' Using a Asset Build Query filter, display all asset builds used for a specific shot outgoing_links.to.name = 'SHOT_NAME' cheers Eric
  14. 2 points
    I was able to reproduce this issue and we're looking into a fix
  15. 2 points
    Lucas Correia

    Time logging

    Hi Chris, It should be possible to use an event listener to automate starting a timer for a user when a task's status is set in progress. The reason that we don't do this automatically is that there can be several situations where you do not want the timer started automatically, and it is hard to know when this is. An event listener is a small python script that can be used to subscribe to changes in ftrack and perform custom logic such as updating a status, starting a external process or triggering a user interface. Here are some useful resources for setting up an event listener: * Developer hub with introduction to the API * How to subscribe with the API * Information about the update event * Example event listeners If you are not interested in logging time, but rather want to see how long a particular task has been in a certain state you can look at querying `Event` objects using the API. There is a snippet with some examples here. You probably want to query for action=change.status.task and parent_id=the task's id. Regards, Lucas
  16. 2 points
    If there was a way for the event to return the hostname or ip of the browser from which an action is called you could at least verify on which machine the action is called. This doesn't solve the multiple instances on one machine issue, but for users logged in on multiple workstations you could at least filter out your custom hooks so only those available on that machine are discovered.
  17. 2 points
    Willem Zwarthoed

    Component 'duplicate entry'

    Ok, so the issue was with these lines: shot["custom_attributes"] = shot_data["custom_attributes"] shot["metadata"] = shot_data["metadata"] which doesn't work anymore, at least with ftrack 3.5.9 and API version 1.0.4. All credits to Eric Hermelin from ftrack support for figuring it out and providing the solution: for key, value in shot_data["custom_attributes"].items(): shot['custom_attributes'][key] = value for key, value in shot_data["metadata"].items(): shot['metadata'][key] = value Everything is working fine again now. Thanks Eric and Matthias for resolving this quickly!
  18. 2 points
    You are trying to create an assignment where i think you should be creating an allocation, no?
  19. 2 points
    Hey @Remus Avram Is this what you are looking for? https://forum.ftrack.com/topic/895-filter-by-component-name/
  20. 2 points
    We have asked for this also. It is essential to be able to track every change, especially in case bad data enters the system. With a proper audit model we would have a chance of getting back to a good state without losing data through a restore from older backup. Note that even the API does not provide sufficient granularity at present and still uses old data types making it harder to relate to actual data. We are also interested in there being a facility for giving the reason for a change - e.g. why the status was changed. A sort of special linked note / metadata attached to the change event.
  21. 2 points
    Hi @mark.fin , we have the same issue. What we need is a lock system for the Ftrack entities and attributes. Please have a look at this discussion http://forum.ftrack.com/index.php?/topic/788-lock-system-for-entity-attribute/ . Until this is implemented, we are using an Ftrack action which works pretty nice for us. How the action works: - it listen for all the events - ones an event match the conditions, we process it. Example: we allow production to create an asset and update the name as long as the status is not changed. Ones the status is changed, we mark it (set a key in metadata). If the production renames it now, the action detects that the asset is marked and rename it back to the previous name and let the user know why he/she can't do it.
  22. 2 points
    tokejepsen

    DJV Viewer

    I have recently updated the DJV View action to be more flexible in other pipelines; https://github.com/tokejepsen/ftrack-hooks/tree/master/djv_plugin You can now specify what files are available for the user to choose from.
  23. 2 points
    instinct-vfx

    Archive projects

    I'd like to add my vote here. The db is ever growing. We have not even really started publishing assets and versions in our main business lines and the db is getting pretty clunky already.
  24. 2 points
    postmodern

    Houdini plugin

    Hello, All! I finished Base ftrack-connect-houdini plugin functions. Now Houdini can work with Scene, Geometry, Camera Assets (Publish, Import, Management). Feedback it please! Repository: https://bitbucket.org/postmodern_dev/ftrack-connect-houdini Help: http://ftrack-connect-houdini.readthedocs.io/en/latest/ Release Notes: http://ftrack-connect-houdini.readthedocs.io/en/latest/release/release_notes.html Video: https://vimeo.com/194510458 Thanks!
  25. 2 points
    Remus Avram

    Custom keyboard shortcuts

    Thank you, Mattias! Shortcuts keyboard are really useful for repetitive tasks.
  26. 2 points
    +1 A dedicated section on introspection in the docs would be useful. Some more explicit examples: # List entity types available to session >>> print sorted(session.types.keys()) [u'Appointment', u'Asset', u'AssetBuild', u'AssetType', u'AssetVersion', u'AssetVersionLink', u'AssetVersionList', u'BacklogGroup', u'Component', u'ComponentLocation', u'ContainerComponent', u'Context', u'Conversation', u'CustomAttributeConfiguration', u'CustomAttributeType', u'CustomAttributeValue', u'Disk', u'EntitySetting', u'Episode', u'Event', u'Feed', u'FileComponent', u'Folder', u'Group', u'Information', u'Job', u'JobComponent', u'List', u'ListCategory', u'Location', u'Membership', u'Message', u'Metadata', u'Milestone', u'Note', u'NoteCategory', u'NoteComponent', u'ObjectType', u'Participant', u'Priority', u'Project', u'ProjectSchema', u'ProjectSchemaOverride', u'Queue', u'Recipient', u'Resource', u'ReviewSession', u'ReviewSessionInvitee', u'ReviewSessionObject', u'ReviewSessionObjectStatus', u'Schema', u'SchemaStatus', u'SchemaType', u'Scope', u'Sequence', u'SequenceComponent', u'Setting', u'Shot', u'State', u'Status', u'Task', u'TaskTypeSchema', u'Taskgroup', u'Timelog', u'Timer', u'Type', u'TypedContext', u'TypedContextLink', u'TypedContextList', u'User', u'WorkflowSchema'] # Retrieve the class that represents a particular type by key. >>> entity_type_cls = session.types.get("Shot") >>> print entity_type_cls <dynamic ftrack class 'Shot'> # Examine attributes available on that entity type. >>> print sorted(entity_type_cls.attributes.keys()) [u'_link', u'allocations', u'appointments', u'assets', u'assignments', u'bid', u'children', u'context_type', u'custom_attributes', u'description', u'end_date', u'id', u'incoming_links', u'link', u'lists', u'metadata', u'name', u'notes', u'object_type', u'object_type_id', u'outgoing_links', u'parent', u'parent_id', u'priority', u'priority_id', u'project', u'project_id', u'scopes', u'sort', u'start_date', u'status', u'status_id', u'thumbnail', u'thumbnail_id', u'timelogs', u'type', u'type_id'] # Examine a specific attribute by key. >>> status_attribute = entity_type_cls.attributes.get("status") >>> print status_attribute <ftrack_api.attribute.ReferenceAttribute(status) object at 73957712> # Check whether that attribute is mutable etc. >>> print status_attribute.mutable True
  27. 2 points
    postmodern

    Houdini plugin

    Hi guys, We use Ftrack in studio and love it, but our main package is Houdini. Now we use a very simple integration with Houdini software without assetManagment and I need a standard plugin integration as Maya and Nuke has. I'm not a professional programmer, but have some TD experience with main VFX programs. I start my own Houdini integration as branch of ftrack nuke and maya plugin. For now it has basic functionality and can publish and import limited data, but I'm working on it. Installing and developing simply the same as ftrack team maya and nuke open source packages. It open for everyone and if somebody want to help, please welcome! If Ftrack Team have some throats, or even working prototype, it will be cool to be a part. Repository: https://bitbucket.org/postmodern_dev/ftrack-connect-houdini Help: http://ftrack-connect-houdini.readthedocs.io/en/latest/ P.s. I hope, I don't violate any rights. Thanks!
  28. 1 point
    Lorenzo Angeli

    build_ext

    Glad to hear @Konstantin Maslyuk ! The branch still requires some tweaks and details, but should soon get to master. More news and info on the branch itself L.
  29. 1 point
    Hi @Alican you cannot use the location.get_url(component) as path for the component as is relative to the server, path requires to be a local path to your file system. What you might be after, if I'm getting it right , is an event which collect the data which might have been manually uploaded and then transfer them first to you local disk , before being re uploaded as reviewable. For this to work , you need to have a listener running which will intercept the update event for components and use that to move the data from the ftrack.server to the local storage. Something along these lines should work (https://bitbucket.org/snippets/ftrack/ynxGp4) Hope it helps. L.
  30. 1 point
    JPrydz

    Nothing happens after clicking 'Actions'

    Hi Alican, Are you experiencing an empty box for actions or no box at all? When you look at others, where it works, are you in the same project and same context? Regards, Johan
  31. 1 point
    Heya, i was wondering if there are any plans already to make the python api both 2.x and 3.x compatible? We are using the api in some of our server applications and would like to move towards python 3. Cheers, Thorsten
  32. 1 point
    JPrydz

    Download all

    Hi there, At the moment you have to download them one by one. But we have a feature request for a solution to download all items at once. Regards, Johan
  33. 1 point
    cschnell

    Ftrack local installation

    Hi, regarding this page http://ftrack.rtd.ftrack.com/en/backlog-scaling-ftrack-documentation-story/administering/managing_local_installation/server_requirements.html Ftrack runs well on Centos 6. Are also later versions of Centos supported? Thanks
  34. 1 point
    Hi Tim, Sorry for the confusion on this - you're correct, the id is wrong when accessed from the sidebar. To work around this you can do the following: if '_' in entityId realId, junk = entityId.split('_') As for the entityType - this is old style entity type from the backend. Instead of using 'task' you would want to use 'TypedContext' on the session: session.get('TypedContext', realId)
  35. 1 point
    Hey, Question. Is there an option to prevent the renaming of a task, shot, sequence etc... after creation? Currently our studio uses a workflow that stores our assets based on the names within a project hierarchy, and if producers/artists can rename that hierarchy at any point, then that will cause a discrepancy between the file system and ftrack. Obviously we could convert to storing the data via IDs so that how the data is stored is irrespective of hierarchy, but that's less than ideal for our current way of working. The most ideal solution, which would be great if it's available, is the ability to renaming anything that hasn't had an asset save against it (linked to it). But once an asset has been associated, anything in the hierarchy can't be renamed (or at least not without super use privileges and a significant warning that this will break things). Thanks, Mark
  36. 1 point
    I think you can speed this up greatly by collecting all the selected id's first and then querying for "id in ()" to get a collection instead of "id is " -- Erik
  37. 1 point
    Hi Remus, this should be related to: https://forum.ftrack.com/topic/598-manage-roles/ We're working on a fix here: https://bitbucket.org/ftrack/ftrack-python-api/pull-requests/186/backlog-collections-are-not-merged/diff
  38. 1 point
    Note that newer versions of Sphinx support this mocking directly via the autodoc_mock_imports setting. http://www.sphinx-doc.org/en/stable/ext/autodoc.html#confval-autodoc_mock_imports
  39. 1 point
    Thanks, I will report these issues as bugs
  40. 1 point
    Hi Tobi, it is currently not possible to do this but we have an accepted item on our trello board roadmap: https://trello.com/c/hjeU0hHW/30-cross-project-task-user-overview
  41. 1 point
    Hi, We have just released a new version of ftrack-connect 0.6.2 (https://www.ftrack.com/portfolio/connect). This is a major release as all ftrack connect plugins have been updated to no longer use our legacy API and instead use the new API. This change will improve performance across the board, as well as lead to a quicker development cycle. In addition, we are including our new Beta plugins for Maya and Nuke built around the open source project, Pyblish (http://ftrack-connect-documentation.rtd.ftrack.com/en/0.1.12/). Backwards compatibility with the old location plugins and actions are achieved through the ftrack-location-compatibility plugin (https://bitbucket.org/ftrack/ftrack-location-compatibility). While old locations and actions will continue to function, we highly recommend that you start looking at migrating your plugins and locations, please have a look at the migration documentation for more information (http://ftrack-connect.rtd.ftrack.com/en/latest/release/migration.html) For more information on what has changed please refer to each updated package: ftrack connect 1.0.1 ftrack connect cinema 4d 0.1.3 ftrack connect hieroplayer 1.1.5 ftrack connect legacy plugins 1.0.0 ftrack connect maya 1.0.0 ftrack connect nuke 1.0.1 ftrack connect nuke studio 1.0.0 ftrack connect rv 3.6 ftrack python legacy api 3.6.0 We hope you enjoy the release. Please let us know if you have any questions or feedback. cheers Eric
  42. 1 point
    Lucas Correia

    AssetBuild Custom Attributes

    Thanks for following up. For future reference, the server version 3.5 requires ftrack-python-api 1.0.4 or higher. Version 1.0.3 will be unable to use custom attributes properly (what ionav experienced) and versions prior to 1.0.3 will fail to initialise the session with a ServerCompatibilityError. For more information, see the migration notes. We are still polishing a few things before we will start to roll out ftrack 3.5 to hosted sites and will be in contact before then.
  43. 1 point
    If this is important for you, I think your best option would be to use the layout system: http://ftrack.rtd.ftrack.com/en/stable/administering/managing_layouts.html Note that this is quite advanced but give you a lot of freedom. To make them slightly easier to manage (if you add new custom attributes) you could automate the generation of them.
  44. 1 point
    Remus Avram

    Share Views using roles

    Hi, is it possible to share a view with a group of people which has a specific role? In this case, when the role is added to the user, then he/she automatically gets the View shared.
  45. 1 point
    Tilt

    moving TimeLogs

    worked like a charm!
  46. 1 point
    Mattias Lagergren

    Nuke Publish error new API

    On top of my mind; does the write node that you try to make a reviewable from have an input? The publisher uses the first input of the write node to generate the web reviewable. If that is not the issue, could you click "Open log directory" and send the ftrack_connect_pipeline.log file to support@ftrack.com and have this forum thread as reference.
  47. 1 point
    Mattias Lagergren

    New publish tools

    Hi @sridharank, I'm glad to see that you're trying out the new integrations. For the error; you need to either setup your own custom location or configure a centralised storage scenario: http://ftrack.rtd.ftrack.com/en/stable/administering/configure_storage_scenario.html
  48. 1 point
    Mattias Lagergren

    Custom keyboard shortcuts

    I'm afraid it is not possible to change them but I can create a feature request for you!
  49. 1 point
    Remus Avram

    Store the event data

    Hi Mattias, thanks for asking! For the moment we are working at this. The plan is to have a second DB (not touching the Ftrack DB as we would like to update Ftrack Server easily), an action which get all the ftrack events and spool them to the custom DB, and an daemon which get from the custom DB and manage the data. It would be easier if the Ftrack log the events (json format) in a DB or a log file and in the Ftrack configuration set the max days to keep the data. By default should be 0 days if the studious don't use the data.
  50. 1 point
    tokejepsen

    Time logging

    Being able to change the time log for other people as a supervisor or coordinator would be good.