Milad Entezami

Members
  • Content Count

    2
  • Joined

  • Last visited

Posts posted by Milad Entezami


  1. On 12/4/2018 at 10:03 AM, Lorenzo Angeli said:

    Although not web based, one option I can think of would be :

    1) have a project to act as library,
    2) one action which allows to re migrate the assets to/from a given project .
    (could be a reworked version of this example: https://bitbucket.org/ftrack/ftrack-recipes/pull-requests/4)
    This could be extended to keep reference (as metadata or custom attribute) on where the asset originally comes from (as project when publishing back).
    3) a pyside based browser (so can be used as widget in maya, nuke and any other qt based application) to act as library browser.

    Although requires some work, seems doable.
    L.

    Thank you for the reply.
    This could be a possible solution. for us, it will make another problem, which is duplicating assets from our asset library into project folders. we don't want to do that since we only want to reference them in the scenes.

    but thank you I will try this solution, if my limited knowledge of python allows me to do so :)


  2. Is there any official update on this?

    I would really appreciate it if anyone could instruct us on how to build a library of models, textures, HDRI, etc, in separated folders, regardless of their respected project hierarchy. This way it is possible to use third-party applications like Connector to build a library with thumbnails, and reference the assets in ftrack projects with whatever hierarchy that suits the user.