Leaderboard


Popular Content

Showing content with the highest reputation since 09/22/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
    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
  8. 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
  9. 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.
  10. 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.
  11. 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
  12. 2 points
    I was able to reproduce this issue and we're looking into a fix
  13. 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
  14. 2 points
    You are trying to create an assignment where i think you should be creating an allocation, no?
  15. 2 points
    Hey @Remus Avram Is this what you are looking for? https://forum.ftrack.com/topic/895-filter-by-component-name/
  16. 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.
  17. 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.
  18. 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.
  19. 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.
  20. 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!
  21. 2 points
    Remus Avram

    Custom keyboard shortcuts

    Thank you, Mattias! Shortcuts keyboard are really useful for repetitive tasks.
  22. 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
  23. 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!
  24. 1 point
    John Su

    Component path shows up red

    Thanks Lorenzo, it works after launching ftrack connect(don't know it has to be with connect before). Is there anyway I can get it work without ftrack-connect? We've wrapped all the publish/actions launcher entrace so except for this we don't need ftrack-connect. It would be great if there's a way we can do it without ftrack-connect. Cheers.
  25. 1 point
    JPrydz

    Custom link fields for entities

    Hi John, You can also add your vote on our roadmap: https://trello.com/c/hz4agtYK/65-new-custom-attributes-link-entities-type Regards, Johan
  26. 1 point
    Erik

    Duplicate Schema

    Still wan't this
  27. 1 point
    Hi Remus, Correct, right now there is now export on that report. But your suggestions have been noted, so let's see if either a choice for report will be added. or maybe the filter solution mentioned initially. /Johan
  28. 1 point
    You can meet the ftrack team in Barcelona on November 30 (Friday) and December 1 (Saturday) for b'Ars. We'll be available for demos and to answer your questions all day at a dedicated stand. We'll also have ftrack users Twin Pines presenting to share how they use ftrack for Episodic TV and Films. For more information and to schedule a meeting with the ftrack team: https://www.ftrack.com/en/2018/10/ftrack-bars-barcelona-2018.html
  29. 1 point
    Hi Remus, Thank you for your question. This is not possible currently. I believe this is due to that the Assignee field is a multi-value field (that you can have multiple assignees). There is a feature request ticket however on this so will add you to it. Thanks, Mattias
  30. 1 point
    >>> for object_type in session.query("select id, name from ObjectType"): >>> print object_type["id"], object_type["name"] 4be63b64-5010-42fb-bf1f-428af9d638f0 Asset Build 01decdd1-51cb-11e3-9d5b-20c9d0831e59 Milestone bad911de-3bd6-47b9-8b46-3476e237cb36 Shot 11c137c0-ee7e-4f9c-91c5-8c77cec22b2c Task ...
  31. 1 point
    Mattias Lagergren

    Time logging

    Thank you for reporting, I was not aware of this and at the moment we've restricted time-logging to task and this sounds like a bug.
  32. 1 point
    Thank you for this feedback - I will raise it as a feature request with the team.
  33. 1 point
    Afaik this is not documented. The ftrack-python-api hides this in convenience method and the user never has to understand this part, but for the javascript API things are more hands-on. I will raise this question with the team.
  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
    Hi Emi, Thanks for the feedback! Currently it is only possible to mark new note as completable, but not a note written by a client when transferring it. I agree that this would be a very useful feature and will bring it forward to the team. Thanks, Lucas
  36. 1 point
    Hi and welcome to the forum. The Collection object that you get can be accessed much like a list: for note_component in some_note['note_components']: ... some_note['note_components'][0] et.c
  37. 1 point
    Ozen

    Workday Length start and end time

    Hello, We noticed that when we create tasks the end time defaults to 12:01am. Would it be possible in Scheduling -> Setting to also pre-set the workday start and end time? This way any tasks would automatically start at that specific time and end at the end time? Thank you, Ozen
  38. 1 point
    We are also surprised at the change to the documentation, especially as it also removes the versioned docs. Versioned docs are important to us as we may run several releases behind latest for stability and we can't have users constantly confused by references to features they don't have access to. Similarly, offline docs is nice to have. Finally, there seem to be no release notes in the new docs!
  39. 1 point
    tokejepsen

    Hours in My Tasks

    Hey, Got a request to have hours on the My Tasks page. https://imgur.com/a/fzmDM
  40. 1 point
    tokejepsen

    Incoming links

    I can see why linking asset builds to a shot might be helpful. Let's walk through how I imagine that to work out, and let me know if I'm misunderstanding something. You have an assetbuild called "characterA" where you have a "rigging" task. From the "rigging" task you publish a Maya scene with a rig in it. You then link the assetbuild "characterA" to shot "sh0010". An animator opens an "animation" task on shot "sh0010". Now the asset importer would list all the assets on the assetbuild "characterA", because it is linked to the shot, and the animator would need to choose which asset (assetversion) to import. In a more advanced pipeline you would be able to "build" the shot by importing all the assets needed. We work from the "animation" task launched, finding the assetbuild "characterA", and then we need to assume what assets we want to import. This workflow could definitely work, but it would be very prone to production mistakes. What asset should the animator import if there are different versions of the rig? This kind of information is usually something a supervisor or coordinator would know. The animator would probably ask, but that doesn't really get us to a very optimized workflow, because we could just skip the linking and the animator would just import the rig asset directly from the "characterA" assetbuild by asking. Another problem with this workflow is when it comes to exporting Nuke scripts from NukeStudio. Here we end up with a lot of assets (one per shot usually) which the compositor needs to filter through to get the Nuke script asset for their shot. The ideal workflow is that the supervisor or coordinator can link/setup a shot, and the users get all the assets needed for the shot. If we go down the case from above, but with the feature of being able to link assetversions to shots, here is how I imagine it going. You have an assetbuild called "characterA" where you have a "rigging" task. From the "rigging" task you publish a Maya scene with a rig in it to an asset called "rig" with a version of 1, hence referred to as "rig_v1", with a "main" component. We now link "rig_v1" to shot "sh0010". An animator opens an "animation" task on shot "sh0010". Now the asset importer would list all the assetversions linked to the shot. In this case we only have the assetversion "rig_v1". The animator imports "rig_v1" without the need to ask anyone in the production about which assets should be used in the shot. This scales up nicely because the decision about which assets to use in the scene has already been made for the animator, so you could essentially have a "Import all linked assetversions" button. Linking assetversions to shots/tasks also works well when exporting Nuke scripts from NukeStudio because the compositor does not need to filter through all the other export assets but only gets the list of linked assetversions in importer, or the pipeline can easily make that assumption when hitting a "Setup script" button. There are some areas where this workflow falls a bit short; components and updating. If a studio utilizes different components than for example "main", it'll be difficult to assume what to import if there is a "Import All Linked Assetversions". This can however be overcome by just bringing all components or the studio making its own "Import All Linked Assetversions". When publishing a new assetversion, the already linked shots/tasks would have the old assetversions still linked. You would easily traverse the dependency graph and update the links, or leave it and let the asset management part of ftrack-connect handle updating. You would only really need to import all the linked assetversions once, but in the "Import All Linked Assetversions" there could also be a follow up "Scan for newer versions". Phew! That was quite a post I hope it makes sense, or at least some of it.
  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
    Mattias Lagergren

    Filter by Component Name

    Hi Toke, yes - this can be done using the advanced api filtering from the UI: http://ftrack.rtd.ftrack.com/en/stable/using/filtering.html#filtering-using-api-like-queries With something like: components any (name is "foo")
  43. 1 point
    Have been able to get any further with this?
  44. 1 point
    Mattias Lagergren

    Nuke Publish error new API

    Hi, I'm glad to see that you've been trying out the tech preview of our new integrations! For production use we still recommend focusing on the current set of integrations found under the "ftrack" menu. As for the error you're seeing, 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
  45. 1 point
    Yes, this will most likely be added, but I do not have any dates for it at the moment. We're more and more relying on the API ourselves when building the application so down the line things like this should be available. A problem at the moment is that the underlying model is quite complex - both to understand and to get right. Either we will need to simplify it or come up with good helper methods. This is the main reason why it is not there already.
  46. 1 point
    I'm actually working on this issue right now :-)
  47. 1 point
    This got sneakily implemented This is great, thanks for this!
  48. 1 point
    Tobi

    PDF / Excel Export

    Hi, we're using the Export function to create a list of the current shot/task statuses. Unfortunately the layout of the PDF can't really be changed by the user. Specifically we'd like to increase the size of the thumbnail in those lists. A dropdown menu to switch between small/medium/large image sizes would be a nice addition to the export function. Of course larger images would reduce the number of items per page. Also we noticed that there is a small bug with (custom?) attributes of the type "Number". Although the field is a non-decimal number (which is shown correctly within ftrack) the numbers are shown as decimal in the exported PDF. So 5 turns into 5.0 for example. Regarding the Excel export it would be nice to have the same layout for the excel sheet as for the PDF. Then the user could change the layout the way he wants. At the moment the excel file does not include thumbnails. I assume that's because the excel files are created via a parsed csv file? Kind regards, Tobi
  49. 1 point
    Sorry, I thought you were launching the action from command line. Try adding your action to FTRACK_EVENT_PLUGIN_PATH instead? This code works for me. import ftrack_api class TestAction(object): identifier = "test_action" label = "Test Action" def __init__(self, session): super(TestAction, self).__init__() self.session = session def register(self): self.session.event_hub.subscribe('topic=ftrack.action.discover and source.user.username={0}'.format(self.session.api_user), self.discover) self.session.event_hub.subscribe('topic=ftrack.action.launch and source.user.username={0} and data.actionIdentifier={1}'.format(self.session.api_user, self.identifier), self.launch) def discover(self, event): items = [{'label': self.label, 'actionIdentifier': self.identifier}] return {'items': items} def launch(self, event): print "Launching the App" return { 'success': True, 'message': 'Action launched successfully.' } def register(session, **kw): if not isinstance(session, ftrack_api.Session): return action = TestAction(session) action.register()
  50. 1 point
    It would be great to be able to publish a Web Playable version though the Adobe CC Ftrack Connect plugins. Right now you can publish a Web Playable version through the Publish window directly in Ftrack Connect, but it would be great to see this feature incorporated into the Adobe CC apps. A few of our guys are located off-site and don't have access to our centralized storage, so they can't currently use Ftrack Connect.