This is part two of an article about how Blender Studio integrated Kitsu into Sprite Fright's production pipeline. In this piece you will learn how the animation and lookdev departments interact with Kitsu from within Blender.
It helps when a .blend file is connected to a task on Kitsu. This way, the .blend "knows" what's currently being worked on. Is it a shot or an asset? Which shot is it and what sequence does it belong to? If we know the answers to these questions, we can offer the artists many useful tools.
For this reason the Blender-Kitsu add-on has a context browser that works like this:
The artists can directly browse the data structure that is stored on Kitsu and either manually select what they are working on or automatically detect it via the filepath.
One very important aspect of animation is the review process. Animators do playblasts of their work and get feedback. Kitsu lets you upload attachments to a specific task and offers paintover and annotation features for videos -- both of which are very useful for the review process.
To upload their work to Kitsu, animators have to go through multiple steps manually, which takes up a considerable amount of time. This is especially true if you have to do multiple playblasts in one day. Luckily, the Blender-Kitsu add-on has a playblast feature built-in, alleviating a lot of this struggle.
With the add-on you don't have to leave Blender to upload a playblast to Kitsu. The animators can even provide a little information on what they did and set the status of the task. In the add-on preferences there are two options that can be enabled:
Open web browser after playblast which opens the default system web browser which in turn points to the active shot after the playblast so the animators can immediately review their work on Kitsu.
Open Sequence Editor after playblast which loads the exported playblast in the Sequence Editor in a new scene and plays back instantly.
Maybe you also noticed that the add-on warns you if the frame range of your current scene is out of date (this is after you connected the .blend file to a shot). This gets checked on scene load and makes sure that the frame range of the animation scene always matches the one on Kitsu. It is not unlikely that frame ranges change during the production and they need to be communicated at every production step.
While the lookdev department also has the frame range check on scene load enabled, they have another small tool to quickly apply render settings. These are just python files that get executed when they click the run button.
This was a quick overview of the context features of the Blender-Kitsu add-on. It is now part of the Blender Studio Tools repository, which you can find here.