← Krita/Animation/Usecases You do not have permission to edit this page, for the following reason: The action you have requested is limited to users in one of the groups: Users, Administrators, trusted, KDEDevelopers. You can view and copy the source of this page. =Animation: Roles and Usecases= Who are the people that use animation, what do their workflows look like, and how do we visualise Krita helping them? == Storyboarders == Storyboarders are people that take a SCRIPT and turn it into a sequence of images indicating the layout and posing of the characters. These include camera directions. When a storyboard is turned into a rough animation by having it set to time and playback, this is called an ANIMATIC. Some storyboarders don't only deal with layout and posing, but also with the colours and shading of a scene. What can Krita do for them? * Rough animation is already helpful to them in creating the animatic. * With this, the ability to direct the 'camera' is helpful. This'll require simple layer tweening. * Tools to analyse and assist layouts. Traditional artists like deevad have already request a sort of 'overlay guide' tool that can present a frame with a rule of thirds or golden mean, for the purpose of working out thumbnails. The Storyboarder will find this tool useful as well. The tool itself does not need to be animated. * Similarly, one of the main concepts of animation is that of 'silhouette', which means that the posing of a character should convey what he is doing, even if the audience were to only see his silhouette. To facilitate this, we could consider a seperate viewing mode where the whole layer's colour values are overridden by a single one, so that the storyboard arist (and the animator for that matter), can analyse the quality of his silhouette. (Granted, this suggests that the sotryboard artists will put their characters on a seperate animation layer). * Annoy Gooseberry's matias: http://gooseberry.blender.org/video-how-matias-made-1000-storyboard-images/ Links: * http://en.wikipedia.org/wiki/Storyboard_artist * http://sevencamels.blogspot.nl/search?q=silhouette << very important blog. * http://johnkstuff.blogspot.nl/2006/05/animation-school-lesson-5-line-of.html << this one is mostly about lies of action. == Keyframe animators & Tween animators. == "A keyframe in animation and filmmaking is a drawing that defines the starting and ending points of any smooth transition." - Wikipedia. Keyframe artists are usually the senior animator who draws the most important frames of an animation. They typically draw the so-called 'key-poses' which define the motion of the animated object. An example of this is the walk cycle, where the pose where the head is highest, and the person has one leg up, and the other straight is one keypose, where the other is where the person's head is lowest and his legs furthest appart is the other. Then, junior animators will do the work inbetween. In vector and 3d animation, the main animator is the only animation, as the software will take care of the (inbe)tweening. What can Krita do for them? * Onionskinning! Very useful. * I think the silhouette idea from above would be really useful for analysis. * Audio playback is useful in the case of socalled 'mickey-mousing' or just plain lip-syncing. (We need to consider how far we limit this - suggestion: add jack sync like blender and synfig to allow syncro with an external audio editor) Links: * https://en.wikipedia.org/wiki/Key_frame * http://minyos.its.rmit.edu.au/aim/a_notes/anim_pose.html * http://en.wikipedia.org/wiki/Mickey_Mousing == Background artist. == Paints backgrounds, sometimes these are in paralax What can Krita do for them? * File Layers are invaluable. It'll allow the background artist to work independandly on backgrounds, improving and perfecting them, and each time they update their background, the background in animator's file will update along. Even better, Krita does not require them to actually USE Krita, which may be beneficial to respecting the individuality of a given artist in the studio's pipeline. (That is, the studio does not need to force it's background artists to use Krita, which makes Krita easier to adopt into the pipeline) * Studio ghibli movies and a lot of modern animation uses very segmented backgrounds, which then use an paralax effect to work in animation. If we could have a way to have the artist work on the backgrounds, while the animators work on a seperate file, and ease the pipeline between these. One example is the 'save group layers' focussing more on saving OVER an existing set of files. The other is to allow filelayers to point to a specific layer or group within a given *.kra (and I hate saying it, but also in a given *.psd... let's see *.exr as our golden mean here) * Having wrap-around mode be only horizontally or vertically. This is already in the tracker, and can benefit scrolling backgrounds. == Sprite Animator. == That one sucker in your gamejam who happens to understand animation. The Sprite animator makes stock animation for games, which are usually put into a 'sprite sheet', which is a big image containing all the frames(like an atlas). These then get loaded into the GPU as one whole, where offset-trickery is used to draw the images onto the end object. They are similar to the senior artist is that they take care of the whole animation, but the big difference is that the sprite artist will usually work in colour immidiately, where this is not fact for the traditional animators. The stock-effect of the sprite art allows the sprite animator to work on something more granular and shorter than the traditional animation where everything is headed under a full scene. What can Krita do for them? * Onionskining! * Some very retro games use color cycling to achieve a variety of effects: http://www.effectgames.com/demos/canvascycle/ However, this assumes an indexed palette, and is not properly supported by modern GPUs anyhow, so let's ignore that. * Export to spritemaps or spritesheets. * Combining animation and wrap-around mode for things like animating tiling water textures. == Matte Painters & VFX artists. == People who do the shinies in the movies. Matte Painters and VFX artists primarily use Krita to improve upon 3d renders. We already facilitate this crowd somewhat with *.exr and OCIO support. What can Krita do further for them: * Some VFX artists might use Krita for painting out annoyances, but as Krita does not have motion tracking, I am not sure if this is the most enjoyable past-time. We need to investigate how to have Krita's abilities work together with the existing tools. * Animation support for OpenExr. * There was some worry on IRC about the difference between reference animation and end-product animation. File-layers for animation maybe? MS5 has the ability to set a layer to 'sketch' so it gets ignored on export, which might be an idea? We want to reduce annoyance for the end user in quickly sending his work out. * Annoy Eiken on IRC about this, they'll know more. ==Colorists== People who do the task of colouring and shading everything. This is a crowd we need to study the needs of better. What can Krita do for them: * Lazybrush(aka the algorithm the colorize gmic filter was based on) was originally intended for animation: http://dcgi.felk.cvut.cz/home/sykorad/lazybrush.html = Workflows = == Traditional frame-by-frame painting == === Paint main frames === <ol> <li>Convert a layer into animated layer (Add to Timeline)</li> <li>Paint first frame</li> <li>Change current frame and seek to a new position with the next "main" frame</li> <ul> <li>using mouse and timeline</li> <li>using "next/prev frame" buttons</li> <li>using shortcuts</li> </ul> <li>Activate onion skins to compare to the previous frame</li> <li>Add new keyframe to the timeline</li> <ul> <li>Press special button or a shortcut</li> <li>Just start painting if lazy keyframes mode is activated</li> </ul> <li>Repeat until all main frames are painted</li> </ol> ===Import images=== <ol> <li>Import a single image in selected frame (to import a reference or a keyframe for exemple..)</li> <li>import a file sequence (a file sequence must be a suite of image files with same name including an incremental number; non-linear frame-rate can be supported with non-linear numbering of the files.. and/or using something like those .lst files: http://wiki.synfig.org/wiki/Doc:ListImporter/fr sorry it's in french..) </ol> === Adjust keyframe time position === <ol> <li>Move a keyframe in timeline</li> <ul> <li>using Drag&Drop</li> <li>using special shortcuts</li> </ul> </li> <li>Copy/paste selected content from one frame to another, in the same or another layer.</li> <li>Clone content from one frame to another to save time and memory for frames repeated exactly in a layer</li> <li> [NOT_NEEDED]Adjust keyframe blending options to mix nicely with a *previous* keyframe </li> </ol> === Check the animation === # Play the animation around selected frame (user defined frame values, from a few frames to a few seconds) at selected framerate. === Adjust offset/position of a keyframe on the canvas === # Select keyframe # Select non-properly positioned layer # Use Move Tool to adjust its position #Also, add another mode to transform/pan all frames on a layer (to adjust position of a whole sequence) === [NOT_PRIORITY*] Change ordering of the layers on the canvas === #*Not priority or even not really needed as one can easily bounce content in two layers if needed. # Select layer that should be put below the previous one # Select/Add a keyframe at position where it should go behind # Activate "Push below" option in the keyframe === Export sequence of resulting frames into PNG/JPEG files === # Press Save Sequence As... #Option to export a file sequence for each layer (or selected layers) #Option to export a file sequence for each group layer (similar to current "Save group layers" but for sequences) == Assisted painting with Transformation Masks == === Create initial keyframe === # Make the layer animated by pressing "Add to Timeline" action # Add a transformation mask to it # Transform if needed === Producing transformed frames === # Select desired keyframe and layer # Use Transform Tool to edit the Transformation Mask === Editing/fixing transformed frames === Transformations may induce some visible artefacts of the image so the user should be able to fix them with his hands (brush). '''NOTE:''' should the masks be put into Timeline separately? Should they be shown there at all? # Select desired keyframe and layer with a transformation mask # Right-click on a layer on the timeline and press "Bake layer" to merge all the masks into the layer for this very frame # Start painting over the layer Return to Krita/Animation/Usecases. Retrieved from "https://community.kde.org/Krita/Animation/Usecases"