[Custom attribute default value instead of None]

HI @Jakub Trllo,  

>> I hope this issue is not caused because we don't have newest ftrack_api version
I've been checking this with the one of latest api (1.8.0), but I would expect the same behaviour from previous versions too.
If you suspect is an api version issue please let me know what version are you using so I can try to replicate.

>> Api do not return `None` if default value is set 
Setting the default value on the custom attribute indeed override the None if the value is not set, that's what is for.
>> If value is not set, `None` should be returned 
If you want it to return None, you simply have to leave the default value empty, tested now and seems to be working as expected.

>> [....] if all parents don't have set that custom attribute's value then default should be returned like values in web app.
On checking the previous hierarchy item, that's something I'd leave to the coder to implement as custom logic , rather than providing it by default (as it might cause confusion)

 

Hope it helps!
L.

[Reply on Note makes unable to create next Note]

Hi @Jakub Trllo the only thing which might be happening is a bit of slowdown, but this won't impact the robustness of the overall system.

If there's any doubt let us know.
Cheers.

L.

[Reply on Note makes unable to create next Note]

Hi @Jakub Trllo, look like you hit a genuine bug there ! 
Thanks for reporting, we will soon start looking into it.

For now though you can use this workaround (see the session.reset() before the last commit)

task = session.query('Task').first()
user = session.query('User').first()

# This will work as expected
task.create_note('Note 1', user)
session.commit()

task.create_note('Note 2', user)
session.commit()

note3 = task.create_note('Note 3', user)
session.commit()

note3.create_reply('Reply 1', user)
session.commit()

task.create_note('Note 4', user)
# here is the fix
session.reset() # reset the session
session.commit() # On this line

Hope it helps!
L.

[Component path shows up red]

@John Su if you want this to be working for everyone, $FTRACK_EVENT_PLUGIN_PATH  should be set on each machine , and should be pointing to a shared folder on the network path.   If on the other hand you just want to test it by yourself you can drop it in the local plugin folders under a hook folder (please note this applies also on the shared one).

If you are still having issues please let us know and we'll try to further help you out.

Cheers.

L.

 

ps.

Best of course is to extend the environment and not to replace it , so something like:

FTRACK_EVENT_PLUGIN_PATH=$FTRACK_EVENT_PLUGIN_PATH:/your/central/path

 

[Filtering actions discovered]

Hi @AlexOddbratt, overall your approach seems right.
For general actions though, I'd suggest having a looking into our helper class  in there you can find a helper function that might help you out narrowing down the entity type you are after.

For what concerns custom attributes I'd suggest having a look a the query projections as might be a good way to speed it up.

Hope it helps.
L.

[Component path shows up red]

Hi @John Su, you don't need to have ftrack connect running to have actions and events.
You can run them as simple python scripts (as long as they can access the ftrack-python-api).

1) no it should jut work 

2) In here you can find many examples on how to run events and actions as standalone.
Hope it helps.
L.

[Centos 7: Nuke crashes when trying to open tasks view]

Thanks @Michael Habenicht I'll check if there's anything we can do to ease these issues .

Cheers.

L.

[1.2.2]

Download 1.2.2

Changes:

• Allow Open of asset along with Import and Reference (to retain render settings)
• Allow Alembic to be imported as reference
• Fix fbx export under windows

Install integration as plugin:

1) remove previous plugin from either connect plugins or connect resources.
2) download the new version from the above link
2) decompress the zip in the FTRACK_CONNECT_PLUGIN_PATH
3) restart connect

If there's any problem please let us know!
L.

[Component path shows up red]

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.

[Py3K early access]

Installing and testing the api in Blender

• Go to the blender's python folder (blender <version>/<version>/python/bin/)
• Ensure pip is installed with:

  ./Python3.7m  -m ensurepip

   

• Install the api using pip: 

  ./pip3 install git+https://bitbucket.org/ftrack/ftrack-python-api.git@backlog/ftrack-python-api-compatibility-with-python-3

• as alternative is possible to run the pip module directly from python with:

   ./python -m pip install git+https://bitbucket.org/ftrack/ftrack-python-api.git@backlog/ftrack-python-api-compatibility-with-python-3

• If you want/need to have this included in your requirements.txt you can use the the pip editable syntax as such :
  (in your requirements.txt)
   

  [...]
  someothermodule >= 0.2
  -e git+https://bitbucket.org/ftrack/ftrack-python-api.git@backlog/ftrack-python-api-compatibility-with-python-3#egg=ftrack-python-api
  [...]
  

  
  
   
• Launch Blender and open Python Console to test the api

[link to session]

Hi @TTT

there's no need to install it locally to each machine.
This event can be easily hosted on a central network folder and mapped into the FTRACK_CONNECT_PLUGIN_PATH

Hope it helps.
L.

[Component path shows up red]

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.

[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

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

[Session | KeyError: storage_scenario]

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:
 

Quote

The key error is because the JSON blob with which the server responds is used as the error message when the ServerError is raised. When displaying that error, we call the format() method on the error message string. Since it's a JSON blob, the braces are interpreted as replacement fields, so format() expects keys to have a key-value pair for the first word inside the first braces in the server response, which is "storage_scenario". This is erroneous.

we are looking now on how to properly fix this for an upcoming api release.

[Session | KeyError: storage_scenario]

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.

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

Hi @instinct-vfx, glad to hear!
Please feel free to report any issue or notes about your experience with them.
Cheers.

L.

[Session | KeyError: storage_scenario]

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.

[Session | KeyError: storage_scenario]

@tweak-wtf could you please try with a simple standalone python script rather than from within maya to see if you can replicate ?
Thanks !

[Session | KeyError: storage_scenario]

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.

 

 

[video assets uploaded with Deadline Draft & Ftrack Pipeline not encoding after upload]

@sconlogue@czarnowski.com it might well be to be fair.
Deadline integration is not something we maintain, and I fear might still be using old api under the hood.
If you do have any update from Thinkbox let us know, might be handy for other users facing the same issue.

Cheers.

L.

[video assets uploaded with Deadline Draft & Ftrack Pipeline not encoding after upload]

Hi @sconlogue@czarnowski.com
as I'm not sure what method you are using to upload the movies here couple of resources for you to further investigate.

With this the video will be encoded server side, so you can provide the mov you generate:
http://ftrack-python-api.rtd.ftrack.com/en/stable/example/encode_media.html?highlight=encode_media

If you, on the other hand, want to have more control.
I would suggest to use a combination of (let say) ffmpeg and this solution:
http://ftrack-python-api.rtd.ftrack.com/en/stable/example/web_review.html?highlight=reviewable

With the latter solution will be up to you though, to provide the proper format.

Hope it helps, if you have any further issue or doubt please let us know !
L.

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

Hi Thorsten, there are some news regarding api and support for py3k.

We have been opening a new forum section to provide early access (with instructions and warnings) to the development branch which provide support to python 3.6 , how to install and test.

If you have a chance to test, please share there your finds in there!
Cheers.

L.

[Py3K early access]

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.

[Centos 7: Nuke crashes when trying to open tasks view]

Hi @hulmanen, sorry to see you are having issues.

I've been able to replicate the problem and it seems to be coming from missing library in Nuke Studio.
In order to confirm, can you please check if in your console you get this error ? 
 

/usr/local/Nuke11.2v3/QtWebEngineProcess: error while loading shared libraries: libQt5WebEngineCore.so.5: cannot open shared object file: No such file or directory

Looks like Foundry is aware of this (Ticket #334788).
You can check the status of this ticket here : 

 Hope it helps, we will follow up with Foundry and see by when they'll be able to provide support.
Cheers.

L.

 

[Has anyone written an AWS S3, or MS Azure Location Accessor]

Answered in support case, but here for reference:

For what concerns location accessors, is pretty doable to write S3 and Azure ones (it has already been done before), you can find further information looking into the api: https://bitbucket.org/ftrack/ftrack-python-api/src/master/source/ftrack_api/accessor/

If the cloud storages provide a python api access (eg: boto for Amazon S3) and using the base accessor ( https://bitbucket.org/ftrack/ftrack-python-api/src/master/source/ftrack_api/accessor/base.py)
as baseclass , is just matter of fully re implement the various method exposed.

Although I would suggest to use these as a mid ground storage and keep the production files locally to the office and use these other locations just for transfer, this would allow you to get the best of both worlds. 

Hope it helps.
L.