[Nothing happens after clicking 'Actions']

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.

[0.2.3]

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

["import ftrack_api" in maya]

HI @Dimitri Lucy, glad to hear ! 
let us know if anything else comes up
L.

["import ftrack_api" in maya]

Hi @Dimitri Lucy, 

whenever you are manipulating the PYTHONPATH I suggest extending it rather than overwriting it with something like : PYTHONPATH=%PYTONPATH%:C:\Python27\Lib\site-packages\ftrack_api

On the error you are having though, seems to me that you are installing the new api , but trying to import the legacy ones.
Could you please try to import ftrack_api rather than ftrack ? 

Let us know how it goes ! 
Cheers.
L.

[Copy structure from another Project]

HI @Mani Varma, If all you need is an efficient api to represent a tree I'd suggest having a look at this widget from connect.
It does use a qtmodel which is quite efficient.

Hope it helps.

L.

[Py3K early access]

HI @Milan Kolar, Thanks for reporting it.
I wasn't aware you were already using it ! 
Be aware that some breaking changes (session won't connect automatically to the event hub) are coming soon on the story branch so be careful.

Feel free to get in touch through support to share any stack trace you might be getting.
Cheers.

L.
 

[Switch between managed/unmanaged location]

Hi @Julian Martinz looks like we are on the same page now
let us know how it goes!

L.

[Switch between managed/unmanaged location]

Hi @Julian Martinz, you cannot create two locations with the same name  that would confuse the system.
The idea of the proxy is exactly for this reason, the proxy will have your old name to match (studio.server1), where the underlying (proxied) locations will retain the different behaviour (studio.server1.managed, studio.server1.unmanaged) and the logic in the overwritten methods of the proxy location will dictate what component to handle with what location. 

Hope it helps.

L.

 

[Py3K early access]

We have been restarting the work on the Python api with Python3k support.
There's a new branch  ( backlog/api-2.0/story ) to use to pick the latest and greatest, and it'll be used until the official release.

Here how to update the above snippets to use it:

• ./pip3 install git+https://bitbucket.org/ftrack/ftrack-python-api.git@backlog/api-2.0/story

If you do have any question of you find any issue please let us know.

 

[Switch between managed/unmanaged location]

>> What would work is creating two distinct locations studio.server1 and studio.server1.unmanaged.
Hi Julian, my suggestion of having a third location acting as proxy was coming from the idea of leveraging two different location with different behaviour.
This though , requires to have clear rules on how these two locations will accept data (eg: image sequences -> unamanged, maya files-> managed.)

>> Is there any way to revert a location instance back to the state it was before mixin in the unmangedLocationMixin? 
Not that I'm aware of tbh....  the above solution was though to be able to provide both at the same time.

>> reconfigure my locations by emitting an 'ftrack.api.session.configure-location' event. 
This is something should be called when initialising the session not sure doing it programmatically would provide the results you are after.

L.

[Faster querying]

Hi @Jakub Trllo, you have almost answered yourself the question:
>> It's probably because every time is used `custom_attributes` key on entity, api is querying values of custom attributes?

It is quite possible that is what causing your slowdown.
If you don't need / care about what the previous value was you can think of turning off the auto_popluate using the context manager for it.
You can find further information here.

Let us know how it goes!

L.

[Switch between managed/unmanaged location]

Hi @Julian Martinz , we'll be looking soon on providing something off the shelf. 
Your approach seems the on the right track though !
L.

[Switch between managed/unmanaged location]

Hi @Julian Martinz if you want to use either one or the other in the same project you might have to think of creating what I would call a proxy location.
This location would accept both (or more) the locations you want to use and through logical gates you can redirect the publish to what you want, either based on task, component or any other logic that suits you.

Hope it helps.
L.

[locations and s3]

Hi @narvi, the latest perforce location plugin can be downloaded from this address.
For what concerns S3 there's an example built on top of the legacy api here but still has to be ported to the new one.
This is something on our todo list to port it over.

Hope it helps.
L.

[locations and s3]

Hi @narvi,  there was , in the old api , an ftrack s3 accessor to make you able to move data in an out from there, but this is something we have to look back into and port over the new api, hopefully we'll be able to schedule this sooner rather than later. (contributions are welcome though  )
 

Perforce wise, is coming.
It does work as a normal ftrack storage , hence is client side  but do not require local installation of the server .

If you have any more questions please let us know.
Cheers.

L.

[Custom attribute default value instead of None]

Hi @Jakub Trllo, hierarchical attributes are tricky.
Hope this snippet can help you out.

If case does not let us know!
Cheers.
L.

[Distributed action-listener // multi-threading]

Hi Julian,
if you have long running jobs, the best option you have is to actually use multithreading from within the action ,
just be careful to use this solution as api are not thread safe, so the session will have to be created for each thread.overall though, my suggestion would be to use either a docker or a vm , where you can spawn a python process for each action you want to use, and potentially monitor them
through supervisor or a similar process , so if any dies it'll restart automatically.As you stated , running more of the single event won't work as it will register more than one.hope it helps.
L.

[2.2.3]

Download 2.2.3

What's new

• Fix: Improve render task deduplication logic.
• Fix: Integration fails to start on nuke >= 12.
• Fix: Thumbnail frame is now generated from the mid frame of the exported clip.

How to install

1. stop ftrack-connect-package
2. remove previous nuke studio plugin from : 
   <ftrack-connect-package>/resource/connect-standard-plugins/ 
3. download and uncompress the new version in :
   <ftrack-connect-package>/resource/connect-standard-plugins/ 
4. restart ftrack-connect-package

[Unable to import ftrack on windows 10 x64 machine running Python 3.7 64 bit]

Hi @Alican, although api3 have been tested only on 2.7, 3.6 and 3.7, this error is usually given when the api are not properly installed with all their dependencies.
I'd suggest looking at this post and try the suggested procedure to install the api with pip , through git.

If you still have issues, please let us know!
Cheers.

L.

[Encoding media with exr sequences]

Hi @John, encode_media does not currently support image sequences, only singe image or movies .
you can find more information about this method here

hope it helps.

L.

[new-framework]

Hi @Konstantin Maslyuk yes we are currently working on that repository for some upcoming features on integrations, but is far from being usable.
Regarding your note on the QApplication is something we'll also be looking into as soon as its more stable.

Stay tuned
L.

[Publish comp from within Nuke Studio]

HI, since 2018 the Nuke Studio integration has been revamped with new set of features.

You can find the updated documentation here
And here you can get access to the latest and greatest version.

Hope it helps.
L.

[Task Status Update]

Hi @Duncan, if you want to have statuses changes to persist, you have to remember to commit your session.
Overall you can find a similar example on our recipes repository.

Hope it helps.

L.

[Automatically populating Start Date (API)]

hi @Phil Franjo, although with different scope , there's an example to monitor status changes through the events here : https://bitbucket.org/ftrack/ftrack-recipes/src/master/python/events/cascade_status_changes/

Being event based (hence real time) won't act retroactively , this is something you can implement as one off script on the same logic.
Hope it helps.
L.

[Any plans to make the API python 3.x compatible?]

Hi @Jed Frechette , the Py3k branch didn't get much of an update as we have not found any issue so far , but neither we heard users reporting using it.
We do have testing on the latest python versions and lately tested on Blender 2.8.x (the only DCC which provides Py3k to my knowledge) and seems to be working fine there as well, but of course automated testing and light testing on just one DCC app does not provide full insights on whether something have been missing or not working properly to replace the current stable version.

Siggraph wise, we wanted to start providing updates , but we've been kept busy with other things and we have not managed to find time to address proper time to push this forward, but this is something we'll definitely doing now that we are all back from the summer break.

We are mostly waiting to have users reporting its testing so we can move forward.
If you had a chance to test I would like to hear more from you ! 
(feel free to do so through support channel if you prefer ! )

Cheers.

L.