Skip to main content

Thumbnails Inheritance

It would be great to have thumbnails propagated across the entities hierarchy. In some scenarios from folder to its children, in other from version to its parents.

Strategy

  • The project's thumbnail, and each folder thumbnail is inherited by children.

    • So at the beginning of the project, every entity shows the project's thumbnail.

    • Inherited thumbnails shows an overlay of the entity type icon to mark that it’s inherited

    • Product versions and workfiles don't inherit thumbnails.

  • On any entity, the frontend gives the ability to set/unset a thumbnail. When set this way, this thumbnail is always the one to display and will not be overriden.

  • When the pipeline publishes a new reviewable, it becomes the thumbnail for the related product version.

    • In case of several reviewables, the main one is used.

    • The frontend web player should give the ability to set a specific frame as the version thumbnail.

  • If a Task has more than one product version, it shows the thumbnail of the last one which updated its status or was created.

Stretch Goal

  • Arbitrary thumbnail can be uploaded or use the thumbnail of another entity.

Settings to introduce:

  • Inherit thumbnail from parent (bool=True)

  • Propagation of version thumbnail as task thumbnail (bool=True)

  • Propagation of version thumbnail as folder thumbnail (bool=False)

Status: Planned4 comments

Log in to comment and vote

Comments4

  • Vincent Ullmann

    It would be great to have some control to influence the thumbnail inheritance.
    There are some cases where we would only update a parent thumbnail if some conditions are meet.

    for example:

    • new asset

    • publish textures v1 → thumbnail gets updated ✅

    • publish turntable v1 → thumbnail gets updated ✅

    • publish textures v2 → don’t update the thumbnail because a “later step”-thumbnail exists.

    similar example would be animation playblasts overwriting lighting or composting sourced thumbnails.

    Some users/studios might like the thumbnails to show the earlier steps as it might be good indication that these assets/shots needs to rerun trough the pipe… but other studios might prefer to always see a thumbnail based on the “latest” step of the pipe.

  • Martin Ličko (murphy)

    Team•

    Merged request

    •

    1 vote

    Thumbnail inheritance

    It would be great to see thumbnail inheritance.

    If there is a thumbnail set for the project, all entities should get the parent thumbnail (with some level of transparency to see it is not the explicit one)

    Only when there is explicit thumbnail set it will get 100% thumbnail and all children will inherit it with transparency