Images in session review

[sati]

Hi,

We are making some tests with "Client Review" and we can upload images, but they are not displayed in review session. Is it possible to display images there? Do we need to configure something? Because besides videos, we would like to have images/frames in the session too.

Thanks!

[Mattias Lagergren]

Hi Sati, uploading images should work fine. Are they completely invisible or show up but cannot be clicked? Are you drag&dropping them to the review session on the manage page or how are you adding them to the review session?

If you want you can create a support-case and attach screenshots/extra information privately.

[sati]

When I do the upload in ftrack, it is displayed like a blue square with the message "Missing playable component." Then, opening the session, it does not appear there. It is like they does not exist in the client session. I will send an e-mail to support then.

Thanks!

[Lucas Correia]

Including my answer to sati here as well for future reference:

"Missing playable component" means that the version does not contain a component with the required metadata to mark it as a reviewable component.

For local installations, we try to encode videos to a web playable format, but do not support encoding images at this point. To make the images viewable you can do one of the following:

• Publish versions that fulfills the requirement via the API: Publishing for web review
• Run an event listener which automatically updates images to be reviewable: Image 'encoder' for local installations. 

[laba Kumar Maharana]

Hi Lucas,

I got the image_encoder.py file, please guide me how to deploy it.

Ftrack is live now. I don't want to take a chance for downtime.

[Lucas Correia]

Hi,
 

The image_encoder.py is what what we refer to as an event listener. An event listener is a small python script that can be used to subscribe to changes in ftrack and perform custom logic such as updating a status, starting a external process or triggering a user interface.

Here are some useful resources for setting up an event listener:

• Developer hub with introduction to the API
• How to subscribe with the API
• Information about the update event
• Example event listeners

An event listener can be deployed centrally on a server (typically separate from the local/on-prem ftrack installation), or the user's machine if it needs access to it. In this case, you will want to have one instance of the listener running centrally.

You can run the event listener from the command line:

python image_encoder.py

You can also register the event listener as a plugin. For more information, see the links above. You can use something like Supervisor or Monit to monitor and ensure the event listener is always running.

Regards,
Lucas