From 05798af5593fc5f755cbfad9b623b8857cf9b3a1 Mon Sep 17 00:00:00 2001 From: Jacob Gustafson Date: Thu, 4 Aug 2016 22:55:46 -0400 Subject: [PATCH] formatting --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 3214a3b..c0e125e 100644 --- a/README.md +++ b/README.md @@ -20,6 +20,7 @@ Possibly, rotoscoping applications are not considered commercially viable since The RotoCanvas class is modular, with hopes that it can be used by various video editing applications in the future. The recommended use of RotoCanvas in a video editing application is for applying effects to source media as a preprocessing step before they are trimmed or other effects are added, since rotoscoping is highly dependent on the source frame (base layer) remaining the same. Using the RotoCanvas as a post-processing effect is possible, but accurate frame seeking must be assured somehow (such as by a frame-accurate video editing engine), and further edits to the previous layers will in some cases cause the rotoscoped parts (parts of the image edited by RotoCanvas) to no longer make sense (such as, if a lens pinch effect is added to a scene where there was a layer order error that has been rotoscoped out, instead of the error being rotoscoped out, there will be both the error and a corrected blotch that is the error's original position & shape), which in such cases would require redoing the rotoscoping. ### Storage Method +` where is sequence name (such as, if mygreatvideo0000.png is first frame, is mygreatvideo) [folder] rotocanvas.yml [not yet implemented] @@ -29,6 +30,7 @@ where is sequence name (such as, if mygreatvideo0000.png is first layers [folder] .png .yml [not yet implemented] +` ## Credits * created by expertmm (see also LICENSE)