Jump to content

Tim Edelmann

  • Content Count

  • Joined

  • Last visited

  • Days Won


Tim Edelmann last won the day on October 15 2018

Tim Edelmann had the most liked content!

About Tim Edelmann

  • Rank
    Advanced Member

Recent Profile Visitors

693 profile views
  1. I'd love to read that answer as well... We'd like to publish .exr image-sequences and have ftrack server (ours is self-hosted) encode it to an .mp4 for reviewing. Since we didn't find a description on how to do this, we thought of doing this on our own (via ffmpeg).
  2. Hey, I wanted to complete this thread, to halp anyone, who might stumble into this... To make sure ftrack understands files with different filenames AND different versions, we ended up manually naming the associated asset and omit the part where the files differ! example: if we want to publish a file called "my_awsome_file_v001.jpg" and "my_awsome_file_v002.jpg", the created asset gets the name "my_awsome_file". So both files are linked to this asset, which make ftrack understand, that these are both just different versions of the 'same' file.
  3. Hey Mattias, thanks for the quick answer! Am I correct, that its only concidered the same asset, when the name is equal? As I said, out filenames for rendering hold a version-string like 'v001', 'v002', etc. So each of our versions is treated as a new asset and no versions are shown. Is there a way to get around this, while still having these version-string inside the filenames? Thanks again Tim
  4. Good afternoon, we would like to use the Autodesk RV Player to review AssetVersions linked to a task. These are opened by launching the corresponding hook via web-ui on a selected task. "ftrack_rv_api.py", which comes with the ftrack-plugin for RV, loads two widgets from ftrack (images added as attachments). We noticed, that the 'versions' tab is not showing other versions, if the AssetVersions linked to the task, have different names. As soon as the names is equal and only the 'verion'-field for the AssetVersion differs, the version-field in the RV-widget works as exp
  5. ok. we found it. The error was in an other class and hard to find..(ignored whitespace and indentation, which was ignored by the python interpreter). It looks like, that errors, when happening in custom accessors and or structures, arent addressed properly by error-debug-log.
  6. What we tried so far... We are getting this error: ftrack_connect.ui.widget.publisher.Publisher - ERROR - Failed to publish: Failed to transfer component <FileComponent(ccfee77a-266c-4248-9431-bc573e7cc3f4)> data to location <Location("Infected_custom_location", 96865d31-ddb8-4ef9-bbde-79fdc5a7e8dd)> due to error: 'Session' object has no attribute '__getitem__' Transferred component data that may require cleanup: [] Traceback (most recent call last): File "c:\python27\lib\site-packages\ftrack_connect-1.1.3-py2.7.egg\ftrack_connect\ui\widget\publisher.py",
  7. Hey there again, its been a while since my last post.. We currently exploring, whats the best way to tell a project, thats all its files, components, asset versions are now stored somewhere else. The background for this is, that we want to be able to move a project after its creation. For this we could listen to "ftrack.api.session.configure-location" and configure a custom location. But how can access the storage scenario to setup new mount-points? Is it even possible to set the storage scenario via ftrack_api? thanks in advance
  8. ah.. ok thats good to know! I'm glad, this work around does the trick. thank you.
  9. any news on this? we also would like to use this functionality A question that is very close to this: We have multiple multi-selection, hierarchical custom attributes. One of them triggers ftrack.update when changing its values (and clicking somewhere outside), the others don't!?!? Can anybody explain this? This is confusing. Thanks in advance Tim
  10. Additional information: We noticed, that the ids look different and we don't know why?? normal ids look like this: '75b59aae-e1bb-11e7-ad88-7ab7a47c9dda' while the one retrieved here looks something like this: '75b59aae-e1bb-11e7-ad88-7ab7a47c9dda_48' this '_48' breaks it! PLUS: The 'entityType' given in 'event['data']['recordData']['entity']['entityType']' is not starting with a Capital letter, which breaks it too! So if we remove the '_48' and use 'TypedContext' instead of the given type, we're able to query the object.
  11. Hey everybody, while setting up a dynamic-enumerator-action, we noticed, that the information on the currently selected element doesn't help to retrieve an actual object. We always get 'None' as a result. This is the event, that comes in: { "topic": "ftrack.dynamic-enumerator", "source": { "id": "c73c09beff154613ba61300782bb836e", "user": { "username": "TEdelmann", "id": "75b59aae-e1bb-11e7-ad88-7ab7a47c9dda" } }, "target": "", "data": { "attributeName": "Briefing_Workflows_00_Maya_Config", "sorters": [], "filters": [
  12. yeah, adding a 'custom' date manually is a good idea. thanks a lot Tim
  13. Hey ftrackers, we recently tried to add notes to a task in a sorted order. We read a number of question from a json which looks like this: [ { "index": 1, "content": "Q1" }, { "index": 2, "content": "Q2" }, { "index": 3, "content": "Q3" }, { "index": 4, "content": "Q4" } ] ..and we would like these questions, to appear in the order given by index. But for some reason, we always get the order visible in attachment: ftrack_question_ordering.PNG Could this be the same problem we have with custom attributes being not sorted?
  14. Hey Mattias, thanks for getting back on this. Good to hear, that I'm not the only one running into this (so its not just my fault)..
  15. Hey, another thing we noticed: We use a custom attribute of type: dynamic enum which is hierarchical. If the project is selected and we change its values, no 'ftrack.update' gets triggered! On the other hand, if we select a folder (or any other object under project), changes to our custom attribute, do trigger 'ftrack.update'. Is this behavior wanted? For our workflow, it would be great, if the custom attribute changes trigger 'ftrack.update' no matter what is selected. thanks again
  • Create New...