All Activity

This stream auto-updates     

  1. Today
  2. Yesterday
  3. Hello Hopefully a really simple question but I just can't seem to figure this out by myself. What does 'Normal' mean? What is this type of sorting useful for? Thanks in advance! J
  4. Invited! Regards, Johan
  5. Last week
  6. A potential workaround would be to group by Assignee or Status, this way only the tasks and links show up in your export without the parent objects.
  7. Just gonna +1 on this as this is still the case with PDF exports. Needs to be simpler visually and compact information, no need for overarching folders or shots when you can find this info within the name or link.
  8. Can you please invite pedro.zuneda4@gmail.com as well?
  9. Lorenzo Angeli

    2.2.1

    Download 2.2.1 What's new Fixed: Tasks are marked as duplicated if the same clip name is present on multiple tracks. Fixed: Tasks generate empty unwanted components. Changed: Replace simple EDL export with OpenTimelineIO edl export (older EDL exporter remains available). New: Thumbnails are published also to parent entity. How to install stop ftrack-connect-package remove previous nuke studio plugin from : <ftrack-connect-package>/resource/connect-standard-plugins/ download and uncompress the new version in : <ftrack-connect-package>/resource/connect-standard-plugins/ restart ftrack-connect-package
  10. Hi @Mattias Lagergren is there any update regarding this? If not, is there any workaround for the moment? Like would it be possible to create an action which the user triggers on a ftrack object to subscribe to it? As an example, an animation supervisor would like to subscribe to all the animation tasks from a show in order to receive a notification for each version published linked to the animation task.
  11. Lorenzo Angeli

    0.1.0

    Windows Download 0.1.0 Linux Download 0.1.0 Osx Download 0.1.0 Documentation Changes since last version fixed: User settings crashes under osx and windows platform. fixed: Perforce password is not properly set. fixed: Workspaces breaks if contains spaces. new: Admin role for action gets checked against perforce roles too. new: User's workspace is created on first run if not already available. new: Init documentation. Requirement Accessible Helix Server What to expect to work Storage setup User preferences setup Publish Versioning Aim for testing Publish from any application Import/Update version through connect's asset management system Known Issues and limitations None known atm
  12. Earlier
  13. Thanks Johan! I'll give it a go!
  14. Hi Francois, This sounds strange. And I can't seem to reproduce what you mention. Or maybe I have misunderstood. Could you provide us with some screenshots on what it looks like when you set it up? Regards, Johan
  15. Hi Konstantin, Thanks for the valuable feedback. I have added your comment to the feature request. Regards, Johan
  16. Hi, I think I may have stepped on a unwanted behaviour about versions status : when creating a new version, its status is the first of the selected status in system Settings → Schemas → My_Schema → Version. If you reorder the statuses (System Settings → Statuses) and move an another status used in your schema one top of the first one used and then save, the status of new versions will change accordingly. This is not true for tasks that are always created with the Not ready status (or so I believe). As a result, this is not intuitive at all for versions. It could be handy to be able to explicitly chose which status is the default one, for tasks and for versions.
  17. I do not see a mention of task's tracked time breakdown here. When i see a negative "+/- hours" on particular task i want to see who is responsible for that and when that happen. Assignee would be changed and task would be done in time but polishing took too long. Popup window on task's "Worked hours" value would be nice.
  18. I'd like to report here , for other users which might find similar issues, the root cause which has been resolved through the internal ticketing system. Here the full reply from our developer: we are looking now on how to properly fix this for an upcoming api release.
  19. Hi @tweak-wtf sadly there's no easy way for us to replicate this issue. We'll be looking though, to improve the error logging in the api to present a more complete report. Let us know if you have any progress on this. Cheers. L.
  20. Thank you for your answer and for reporting it to the development team. I hope they'll be able to fix it soon, this a feature we would really appreciate to use!
  21. Hi Francois, Sorry for late update. Yes, the way this works today is that you will see time for the account, independent of the project. This is not really expected behaviour, so I have reported it to development. Regards, Johan
  22. Hey @Lorenzo Angeli the output of sys.executable is: /prod/softprod/apps/maya/2018/linux/bin/maya.bin I've also printed the used python version if that's of any any use: 2.7.11 (default, Dec 21 2015, 14:39:44) [GCC 4.4.7 20120313 (Red Hat 4.4.7-11) I have already shortly touched base with the pyblish developers on gitter. They pointed out to me that the actual key gets quoted. So if you have a look at my first stacktrace in this thread you see the KeyError is on '"storage_scenario"' but i guess it should rather be 'storage_scenario'. So that KeyError is actually raised when I want to print the ServerError which is handled in the __str__ method of exception.py. I think that is also the reason why I get ServerError: <unprintable ServerError object> in my last stacktrace. I don't know for sure but I think if I would manage to print the actual ServerError that would already be really helpful.
  23. Hi @instinct-vfx, glad to hear! Please feel free to report any issue or notes about your experience with them. Cheers. L.
  24. Hi @tweak-wtf , thanks for reporting back , and good idea to raise the overall logging level ! Sadly though, I cannot see anything in the errors that would help pin point the root cause. As the error seems to be happening from within the plugin only, and not from a plain shell or plain maya, I'd suggest have the pyblishs developers involved. If you get any further information coming out from them, please feel free to report here so we can cross examine the results. As last thing , could you please check what interpreter pyblish is using adding at the beginning of your script: import sys print sys.executable In the meanwhile we'll keep looking on potential causes on our side. L.
  25. Update: I just wrapped my connection call in try/catch block and printed the stacktrace... maybe that is also helping?! Call to connect to API: session = None try: session = ftrack_api.Session( server_url = FTRACK_SERVER, api_key = FTRACK_API_KEY, api_user = getpass.getuser(), ) except Exception as e: self.log.debug("Session: {}".format(session)) self.log.debug(traceback.format_exc(e)) Stacktrace: // pyblish.CollectFTrackInfo : Traceback (most recent call last): File "<string>", line 35, in process File "/prod/softprod/libs/ftrack_api/session.py", line 224, in __init__ self._server_information = self._fetch_server_information() File "/prod/softprod/libs/ftrack_api/session.py", line 1317, in _fetch_server_information result = self._call([{'action': 'query_server_information'}]) File "/prod/softprod/libs/ftrack_api/session.py", line 1619, in _call raise ftrack_api.exception.ServerError(error_message) ServerError: <unprintable ServerError object> //
  26. Hi @Lorenzo Angeli thanks for responding. Sure... I also sent an eMail with some insights to support so I'll just summarize what I wrote in that eMail. Currently I'm trying to build a 3D pipeline based on pyblish also integrating the published files with ftrack. For that I need to connect to ftrack API from a pyblish plugin. The error was popping up 2 days ago. Before that everything was working as normal. I talked to our SysAdmin and he told me that he didn't change anything about the network settings. The error only happens when trying to establish a connection from that pyblish plugin... Trying to connect from just a standard python interpreter ran from the terminal works. I went ahead and added some lines that log some variables to a file to the session.py in the ftrack_api python package in order to see what's going on. The output that I'm getting is the following: Trying to connect from terminal... ############# DATA ########## [{"action": "query_server_information"}] ############# RESULT ########## [{u'storage_scenario': {u'data': {}, u'scenario': u'ftrack.automatic'}, u'version': u'4.1.5.4750', u'is_timezone_support_enabled': False, u'schema_hash': u'450f452f8addcd23370a8a90f8156c4a'}] Trying to connect from pyblish plugin... ############# DATA ########## [{"action": "query_server_information"}] ############# RESULT ########## [{u'storage_scenario': {u'data': {}, u'scenario': u'ftrack.automatic'}, u'version': u'4.1.5.4750', u'is_timezone_support_enabled': False, u'schema_hash': u'450f452f8addcd23370a8a90f8156c4a'}] Trying to connect from Maya Script Editor... ############# DATA ########## [{"action": "query_server_information"}] ############# RESULT ########## [{u'storage_scenario': {u'data': {}, u'scenario': u'ftrack.automatic'}, u'version': u'4.1.5.4750', u'is_timezone_support_enabled': False, u'schema_hash': u'450f452f8addcd23370a8a90f8156c4a'}] Note that DATA logs the data being POSTed to the api server and RESULT logs the result returned from that POST. From that log I can't see any difference between the 3 different contexts from which I try to connect to the API. I think the problem has something to do with the execution from within the pyblish plugin but I don't understand why the error just appeared basically out of nowhere. I'm afraid that this is also something that is quite hard to reproduce for you?! Thanks for your answer!
  27. @tweak-wtf could you please try with a simple standalone python script rather than from within maya to see if you can replicate ? Thanks !
  28. Hi @tweak-wtf sorry to see you are having problems. The error seems to be coming from a wrong deserialization of the server response (json) relative to the storage scenario. This could be caused by a variety of things related to the network itself (proxy, firewall etc....) Could you please check if any of these changes have been put in place before this error have started happening ? I've trying to replicate it with you same version of the ftrack-python-api without success so far. Looking forward to hear more from you ! In the meanwhile we'll keep looking for other potential reasons. L.
  29. Hi, Thanks for the update. Regarding tasks: Task is the leaf object, so no object can be created on tasks. Regards, Johan
  1. Load more activity