keyframe

Members
  • Content Count

    20
  • Joined

  • Last visited

  • Days Won

    1

keyframe last won the day on November 1 2017

keyframe had the most liked content!

About keyframe

  • Rank
    Member

Profile Information

  • Gender
    Male
  • Location
    Toronto
  1. Heya everyone, Wondering if anyone has seen this particular error come up when attempting to initialize a new ftrack_api.session()? import ftrack_api s = ftrack_api.Session() >>> Exception in thread Thread-1: Traceback (most recent call last): File "/usr/lib64/python2.7/threading.py", line 812, in __bootstrap_inner self.run() File "/usr/lib64/python2.7/threading.py", line 765, in run self.__target(*self.__args, **self.__kwargs) File "/tools/python2.7/3rd_party/ftrack_api/event/hub.py", line 203, in connect details=error_details EventHubConnectionError: Failed to connect to event server at https://<company_name>.ftrackapp.com with error: "[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:579)". If anyone has any insight, i'd appreciate a nudge in the right direction. Gene
  2. Heya Johan Yeah, this is the field that Greg and I are speaking about (we work in the same place in case it wasn't obvious!). Basically, the issue is that producers still maintain a communication chain over email regardless of whether feedback is entered into FTrack or not. The challenge at the moment is that in order to present a coherent outward facing message to client with a list of caveats for a posting or a list of items that we have addressed requires a separate email thread. We're hoping that being able to include that (or an additional field, if you want to keep the review landing page uncluttered) will allow for a single email thread for the entire posting. Formatting this paragraph would also be quite key... or perhaps there is a different facility for this purpose which we aren't seeing? Best, G
  3. Is it possible to include the text in the description field in the invite email that gets sent to client? One of the producers was concerned about being unable to keep a non-ftrack communication thread open with an external client along with the review session. We're hoping that including text in the description would afford the external producer an email thread to reply to that contains our internal comments about the posting. Is this possible? G
  4. On the subject of review sessions, A comment we've heard several times was that the review session was seen as 'too complex' for some clients (the majority of the work we do is in advertising, and sometimes our client's clients just need to 'see the videos quickly'). We would love a simplified 'here are all the posted videos on one page' type option. Also, a mobile friendly review page version is highly sought after -- at the moment we use frame.io for external review for this reason, which makes the value proposition of ftrack lower overall :\ G
  5. Are there other repercussions to changing the workday length that I might not be thinking of? if I set the workday length to 1 hour, will anything else untoward happen other then the 1d unit in timesheets? I'd love to RFE the reminder emails minimum option... reason being is that artist are leery of logging a day of less then 8 hours, even though they might only be working on a tasked job for 2 of those numbers. They instead end up filling in an 8 hour day on a 2 hour task in lieu of anything else, which makes it difficult to distinguish a non-profitable job from a sales deficiency... There is a certain "big-brotherness" to these warning emails and timesheets in general, and we all know that usartists can be a sensitive lot Thoughts? G
  6. It seems that ftrack wants to send reminders when a user has logged less then 8 hours(i'm assuming this is the quantity specificied in the workday length field). Is it possible to set the minimum time required to send a reminder without affecting the 'workday length -> hours' exchange rate? G
  7. Thanks Bjorn. Way to sell the appraoch! G
  8. @Remus Avram: Thank you Remus, we ended up following your breadcrumb and creating a dedicated API user to filter through the events. Works like a charm, but quite disappointing that it requires a license. Thanks again for the offer to help. It's much appreciated. Cheers, G
  9. I can't seem to figure out how to query for the username that created a project. Any insight? G
  10. Heya everyone, I'm attempting to prevent users from renaming entities in an action subscribed to the ftrack.update event. In doing so, I set off another ftrack.update event, which calls the action, which sets off another ftrack.update event. Any clues would be most appreciated. G
  11. Thanks for the feedback Eric, This is the path that I ended up taking, but, imo, it results in fairly poor UX. the asset gets created, the 'green' notification fires', then a 'red' notification fires, and then the user is asked to refresh their browser. If there's a vote being held anywhere, please put me down for a smoother UX option. Cheers, G
  12. Heya Mattias, Thanks for the hint regarding the ftrack.create_project_action_identifier. It works perfectly for our needs. Any chance that such a facility exists for other entity types such as shot and sequence? The closest I've been able to get thus far is listening for ftrack.update events and retroactively removing 'badly named' entities using session.delete(pooly_named_entity) session.commit() Ideally, these entities would be prevented from being created in the first place. G
  13. Hoping someone can clue me in, How would I find the 'default schema' out of: schemas = session.query('ProjectSchema').all() Best, G
  14. Thanks for the link. It's just what we were looking for. G
  15. Heya everyone, Apologies for the rudimentary question. Is it possible to enforce a naming convention for projects at creation time? Ideally i'm hoping to use something like this as a filter: re_valid_project_name = re.compile(r'^[0-9a-z_-]+\_\d{6}$') For a brief time, I thought maybe http://ftrack.rtd.ftrack.com/en/3.5.0/developing/events/list.html#ftrack-validate would be what i'm after, but it seems that this event isn't published to the python api. Any thoughts would be greatly appreciated. Cheers, G ps: running 3.5.9 on a local deployment, in case it matters.