I had a discussion with an artist recently who mentioned a feature from another pipeline that he used recently that he really liked, thumbnails for workfiles. Basically the work file browser could show these thumbnails as you click a particular workfile.
Where to show?
So basically in the workfiles tool it would show a thumbnail top right. The thumbnail could be e.g. saved next to the workfile with the same name but with extension .jpg and that would then show in the UI.
Top right here it would then show a thumbnail - thatâs some sweet sauce!
When to generate or what thumbnail to show?
The thumbnails could e.g. be generated on workfile save with a little âcapture screenshotâ tool or maybe even a dedicated capture from the host (e.g. single frame playblast or M3DView api image save in Maya).
Another approach could also be that during publishing when e.g. a review is published that it could take maybe a first frame of it as a thumbnail.
We could even say that IF a workfile had been involved with a publish that on the right hand side it could show the outputs of that workfile and if any of those publishes had thumbnails that it could pick show any of those thumbnails. Thatâd be quite perfect?
Would love to hear thoughts on this!
Especially on implementation with regards to where the thumbnail should be and how it should be linked? (Also with keeping an eye on potentially remote artists connected with site sync, etc?)
I am all for it. We were discussing it here multiple times, and with the simple capture tool it would cover most of the cases even without per host implementation of some auto-capture functionality.
Having thought about this some more and also checking back in with the original artist who mentioned he loved the feature in another pipeline I think itâs not about having a thumbnail PER workfile version in particular but much more about just quickly being able to see the thumbnail of a task/workfile.
So thatâd mean we could just find any reviews/renders or alike that came from the particular task and be pretty close what weâd need?
Maybe the first step is just showing a thumbnail at all for a particular asset as soon as you click it?
This could be probably done very quickly. We already do something like that in the loader, where we show the latest published thumbnail when asset is selected.
I wouldnât make it too clever and pick the latest published thumbnail from any subset published from the given task. We could technically crawl back up the links and find the subsets actually produced from the workfile and just pick the latest of those.
Alternatively
find latest review or render family subset published from this workfile
find any other latest subset published from this workfiles
find latest review or render family subset published from this folder (asset in OP)
find any other latest subset published from this folder (asset in OP)
Of course if the workfiles has explicit thumbnails, use that.
I agree that thumbnails are handy and would be lovely to have.
I have just to add something to it. I do prefer to have it for each workfile from simple reasonsâŚit should be useful not for show of. So it should help artist to locate the proper workfile with visual aid and thats it. The only purpose.
So Im against single thumbnail for shot only (from latest or selected version) its just bells and whistles not being really too much of a use.
Here is how it is in blender and can tremendously help to find the right workfile visually (not needing to read the names) We should strive for this. Could be just viewport capture of active viewport. So artist would be aware that the workfile saves with whatever he has on the screen. So he could benefit from it and set it to his liking communicating the content of it for later search.
Did some more thinking and also testing out ideas and this is definitely true - you want to see the state per workfile, not for the asset/shot.
I actually even want the thumbnails laid out visually per workfile directly instead of only the right-hand side thumbnail. So preferably the list would also show the thumbnails.
I was thinking of prototyping it for now by just saving a {workfile}_thumbnail.jpg file or alike next to the workfiles, and when found that then the UIs would show it. Itâd be the most trivial implementation thatâd not require any database access, etc. Itâd not be site-sync ready but I believe actual (non-published) workfiles arenât anyways so I guess itâs a good start since itâs the easiest.
Then upon save for each DCC a screenshot would just be automatically grabbed from the current active viewport, e.g.:
There is similar kind of approach already in Hiero. Workfile product type is grabbing screenshot of timeline.
But as you can see, it is not really ideal image ratio.