shaynad
February 12, 2020, 7:05pm
4
Hi @mgarward ,
Ah, I see what you mean. If your goal is to ultimately share assets across projects, like having an Asset Library you can pull from, there are a couple of options worth exploring in this post from Tommy:
Hi @marvinmetzner , great question. We don’t really have proper “Asset Library” support in Shotgun. (Yet!) But there are a couple of ways people tend to go about this, and what you describe is probably the most common approach.
The caveat is that you cannot link Elements from one Project into another, so you would need to make a copy of the Element in question if you wanted to use it in a different Project. This might be a little more complicated if you have linked entities attached to it that y…
We also have a couple more posts and related topics:
The way this works in our pipeline is:
we have a lib project, to which all reusable assets are added
in other projects, the loader app is configured to load assets from the lib project
In order to configure tk-multi-loader2, add the following under “entities:”
- caption: Library assets
entity_type: Asset
filters:
- [project, is, {type: Project, id: 359}]
hierarchy: [project, sg_asset_type, code]
- caption: Library shots
entity_type: Shot
filters:
- [project, is, {type: P…
I built an element library using Shotgun back in 2013 for a collection of practical elements (a few thousand.) Been working fine for six years.
I made Version entities for the element proxy.
Artists enjoy searching use the nice animated thumbnails. They chose to put them in about a dozen categories (aka Sequence entity). They can make tags to help find them too.
Drag-n-drop works nicely into Nuke.
I made a submission dialog in RV to allow creating new elements, along with metadata (eg. stan…
Thanks for the added details, Christian. We have a short how-to guide for setting up a Project as an Asset library of sorts that leverages the Toolkit loaders/publishers:
I hope that’s helpful!
Admittedly, this can be handled better. If you’d like to share ideas with our product team or request this as a feature, submit it directly to our product team over on our public roadmap:
If you’ve got an idea or need for a feature, you can submit it directly to our product team over on our public roadmap .
When you submit an idea, your feedback is delivered to our product team and the product owner of that area of Shotgun will review and determine next steps. The best ideas are the ones that explain why this would be useful in your workflow and how you would use it. This helps the product team to understand if there is a need to be filled.
While the roadmap is the best place …
2 Likes