Jed Frechette

Members
  • Content Count

    2
  • Joined

  • Last visited

  1. We see similar behavior on an ftrackapp.com hosted instance. In our case though the timer starts at -30, counts down to 0, resets to -60, counts down to 0, resets to -60, ... When stopped via the Web UI reports a negative value for the timelog. Using utcnow to set the start time after starting the timer works, but that seems like an awfully janky workaround, for a function that should just work.
  2. Any updates on this work? Looking at the py3 branch on Bitbucket there haven't been any commits for 3 months and I was hoping we might hear more at SIGGRAPH, but I didn't see anything. Currently the ftrack-api is the major blocker preventing us from completing adoption of Python 3 so I'd love to get some hints about when we might expect a stable release that supports it. Thanks,