Lorenzo Angeli

Hi, I created ftrack-golang-api https://github.com/conducte/ftrack-golang-api !
Inspired by ftrack-javascript-api
Is anyone interested in it?
Currently EventHub is not implemeted and Entity's represented throught golang map (dictionary) what is a little bit verbose.
Basic usage of the api:
package main import ( "flag" "github.com/conducte/ftrack-golang-api/ftrack" "log" ) func main() { apiKey := flag.String("api_key", "", "Ftrack Api Key from Settings -> Api Keys") apiUser := flag.String("api_user", "", "Ftrack Api User username from enabled user") serverUrl := flag.String("server_url", "", "Ftrack Server Url server url eg https://ftrack.com") flag.Parse() // Construct Session from command line arguments session, err := ftrack.NewSession(ftrack.SessionConfig{ ApiKey: *apiKey, ApiUser: *apiUser, ServerUrl: *serverUrl, }) if err != nil { log.Fatal(err) } // Query single Task from server result, err := session.Query("select name, parent.project from Task limit 1") if err != nil { log.Fatal(err) } task := result.Data[0] log.Println("Task: ", task) }

I like the API but I'm not a huge fan of writing the queries as text, so I made something a while back using inspiration from SQLAlchemy.
As a very quick example, if the original code is this:
episode = session.query('Episode').first() task_link = session.query('select link from Task where (name not like "%task%" or name is "new") and parent.id is "{}" order by name descending'.format(episode['id'])).first() It would be constructed like this:
task_link = session.Task.where( or_(~entity.name.like('%task%'), name='new'), parent=session.Episode.first(), ).select(entity.link).sort(entity.name.desc()).first() It's able to do everything I've come across so far, if anyone is interested in using it the github page is here.

@Andrea Perisano I've been checking an on the upcoming release we are already set to use Python for unity api 2.0 .
Stay tuned for more info.
L.

OK. Thanks @Lorenzo Angeli.

@jen_at_floyd we are looking on adding your proposed fix (with few changes) to the api 2.0 branch.
If you want you can test this before cloning the repo , changing branch and installing it into a virtualenv.

This fix is likely to end up in the api 2.0 branch soon though, let us know in case you test.
Cheers.
L.

Glad to hear @Konstantin Maslyuk !
The branch still requires some tweaks and details, but should soon get to master.
More news and info on the branch itself
L.

Hi @jen_at_floyd, there's a patch already merged in connect to mitigate this and it'll be available in an upcoming version of connect.

Hi @Chandler there no boilerplate at the moment, but I'll try to find time new year to come up with one.
As you find out though, there was one once, and is the one I'll try to bring back to life or close to what that was at least.
Hope it helps.
L.

Hi @Alican
you cannot use the location.get_url(component) as path for the component as is relative to the server, path requires to be a local path to your file system.
What you might be after, if I'm getting it right , is an event which collect the data which might have been manually uploaded and then transfer them first to you local disk , before being re uploaded as reviewable. For this to work , you need to have a listener running which will intercept the update event for components and use that to move the data from the ftrack.server to the local storage. Something along these lines should work (https://bitbucket.org/snippets/ftrack/ynxGp4) 

Hope it helps.
L.


 

HI @Alican just gave it a go with default connect and actions and I can see them appearing on both Chrome instances I've open (application launchers).
May I ask where the actions are hosted ? On each ftrack-connect-package plugin folder (local to the user) , in a shared place and mapped through FTRACK_CONNECT_PLUGIN_PATH / FTRACK_EVENT_PLUGIN_PATH or are running as standalone event listeners ?
Also, to help us investigate, removing custom events and actions does still trigger your issue ?
Looking forward to hear more from you .
L.

Download 0.2.3
Originally written by Mike Datsik
What's new
* Ensure loads correctly under latest version of houdini (18.0)
* Update to latest QtExt to Fix QStringListModel compatibility for PySide2 5.9+.
* Update plugin built for pip 19+
* Update icon path
How to install
stop ftrack-connect-package
download and uncompress the new version in :
<ftrack-connect-package>/resource/connect-standard-plugins/ 
restart ftrack-connect-package

A small update for everyone listening here:
I've made the first steps for creating the Gantt-exporter.
It's not finished, but might be sufficient for some of you already:
https://github.com/TDArlt/ftrack/tree/master/ftrack-connect/export-gantt-chart
 
I will keep you updated 🙂

Hi @John Su,
For what I can see it seems you don't have installed ffmpeg on the server, can you please double check ?
On this subject you can find more information on our documentation: https://help.ftrack.com/en/articles/1040538-installing-ffmpeg-and-ffprobe
Hope it helps!
L.

Hi @John Su, sure you can ! 
just extract the given script (or download it directly from here ) and drop it in a folder mapped in a  FTRACK_EVENT_PLUGIN_PATH environment variable.
When the session start will look into that variable to see if there's any plugin to be discovered and run.
I'd suggest having one folder on a shared server folder mapped so you can simply drop events in there.
Hope it helps.
If you need any further help just let us know !
L.

Hi @John Su, the path is resolved through an event available in ftrack_connect itself and called resolve.py
If the path is red is possible that your structure cannot be properly initialised and hence not be resolved.
You can try adding more logs into the resolve.py and see if anything is off.
Please send us , either here or through support (depending on how sensible the information are) and we'll look further into it.
Hope it helps.
Cheers.
L.

Please note, the current development status is in Beta stage and is not suitable for production.
Welcome to the ftrack-python-api tech preview for python 3.x compatibility.
Here are some brief instructions on how to start testing the upcoming release of the new API.
We strongly recommend sandboxing the testing environment using virtualenv.

Prepare your sandbox
Create a virtualenv with the Python 3 interpreter:
$ virtualenv -p `which python3.6` ~/ftrack_python_api_py3k Activate virtualenv:
$ source ~/ftrack_python_api_py3k/bin/activate Install
Install from the development branch:
$ pip install git+https://bitbucket.org/ftrack/ftrack-python-api.git@backlog/ftrack-python-api-compatibility-with-python-3 Test
Run python from virtualenv and check that everything is in place:
(ftrack_python_api_py3k) $ python -V (ftrack_python_api_py3k) $ Python 3.6.5
You can now start the Python interpreter and start using the API as usual.
>>> from ftrack_api import Session >>> session = Session() >>> projects = session.query('Project').all() >>> print(projects) If you need to use the Python3 and the ftrack module just run Python directly from the virtualenv using:
$ ~/ftrack_python_api_py3k/bin/python3 -c "import ftrack_api;print(ftrack_api.__version__)"

Bug reporting
Please use this thread to report issues and bugs.
When reporting bugs, please remember to include:
* Operating system in use.
* Python version in use (use: python -V).
* Full stack trace or error.