Sunday, April 29, 2007

Relief

"On the 29th April Moscow was washed clean by a thunderstorm. The air was delightful: it mellowed the heart and made one want to start living again."
-- Mikhail Bulgakov, Black Snow. Translated by Michael Glenny.

Black Snow is a wonderful novel about the process of writing a play and having a theatre produce it. I've just re-read it and have enjoyed it more this time as I can relate the main character's thoughts about writing a play to the process of making and releasing an animated film ;o)

The smoking moose film is now composited. There are a few small compositing glitches, but I've gone ahead and created the uncompressed QuickTime movies and have started the "final" edit in Final Cut. I've also made a backup of the "final" scene files and rendered pictures, which is a relief because I was worried about losing months of rendered files if the disk had crashed.

Thursday, April 26, 2007

so close and yet so far and where's Batty?

There are only a few more frames rendering and a few more to composite ... in the meantime the soundtrack is coming along. The moose's cough is better (using Sound Track Pro's EQ channel editor gives a much better result that trying to match pitch using the pitch editor) and I've added a bunch more subtle sound effects that add to the general atmosphere. I'll need to make a few adjustments for synchronization purposes to the music but I need to wait until after I've finished compositing because the compositor takes over the PC's CPU.

In anticipation of finishing the film, I've downloaded XSI 6.01! But I'm not installing it until I've finished the renders and composites. In theory you can run previous versions with the latest version on the same system, but I'm not taking any chances. I'm excited about using some of the new animation features to animate a few teasers for the film.

The title/credit design is still worrying me. Right now it is very basic and in the past I've always created much more creative titles. Hopefully I'll come up with something by the time I'm finished with everything else.

On another note, I went to the Red Bird Studio tonight where Stickey Hickee was showing off their artwork - they are a wonderful bunch of artists who draw comics. Really, really nice, heartwarming, art, even if Batty wasn't there.

Sunday, April 15, 2007

ah zoot alors

My test composites missed some errors and there was a transform problem on the fire in scene 3 -- I'm making the corrections now and will need to relaunch the composites. One of the errors (which I've encountered before as well) is caused by having different maximum sampling values on different passes -- I'm guessing that I didn't remember to boost the max sampling back up to 2 (luckily not all frames are affected, so I'm only re-rendering the frames that are affected).

Still the end is near ;o)

Friday, April 13, 2007

Rendering is DONE! Compositing NOW!

Whoo hoo. my smoking moose film is now compositing! Meanwhile I'm working on the soundtrack and credits.

I'm only wishing the animals I liked weren't so big. Here's a girl who turned a stuffed beaver into a computer ... hmm maybe I should say she re-stuffed a stuffed beaver with a computer.

Tuesday, April 10, 2007

window

ok "stupid" window is more like it. I lost the highlight for the second part of scene 3 -- if I get it to work, I lose the highlight on the canary OR the matte that's cutting out the sofa on the window highlight comes back. I'm not sure how I've done it, but I think I've gotten around it... although I had to add another canary highlight to make it work and I had to adjust the tiger highlight.

The other thing I fixed today was the Raccoon's cigarette smoke (exhale and rising) which looked strange in some frames when it appeared on top of the pizza box. At first I tried to use a painted vector shape to matte it out, and although I proudly got this working correctly (animated shapes and all), for some reason it messed up the smoke when it did appear outside the pizzabox -- it messed it up in a strange way -- it was darker and had black streaks in it. So I went back to my regular method of rendering a matte pass -- it didn't take too long and it's done.

I think this is it!

I have just launched what I hope is the last test composite of scene 3, the mega multi frame multi passes craziness. The window caused me the most problems. Interestly enough, the window was was inspired by the Polish 1982 Oscar winning short film called Tango by Zbigniew Rybczynski, where everything happened in one room and started with a ball coming through the window, followed by a boy. The film continued to show multiple layers and stories in that one room. Much like the moose film and yet so different too. I doubt anyone will see the inspiration. Anyhow I think I've got compositing of the window and the characters who go out of it working. There are still rendering and compositing "mistakes" but I am leaving them, I don't think there is anything drastic that will kill the film.

For the compositing tests, I am rendering every 24th frame at 1/4 of the resolution, so I suppose there could be a surprise when I render every frame at full resolution, but hopefully those surprises can be corrected in photoshop or fixed with a second composite.

In the meantime, I've also made good progress on a redesign of the smokingmoose website, it will go live when the film is finished and available on DVD. I will release a DVD containing only the moose film as soon as possible, but the idea has always been to release a DVD of a compilation of most of my animated films (I'll leave the bad ones off ;o). The compilation will take a little longer to produce, as I need to get the previous films digitized to uncompressed QuickTime movies.

Monday, April 02, 2007

Fxtree: Composite node: Output Size Mode

After transforming effects to use through a composite node (over or math), you can easily crop to the background by setting the Output size node to Use Default Image on the Output tab.

I had been using the psd blend addon but have stopped using it as the "Place Output Image at Origin" is not working consistently and my attempts to use the Output Size Node parameter don't work with the psd blend node. This is unfortunate since the psd blend addon has more compositing options than the math composite (or perhaps they are just easier for me to use as I am used to photoshop).

As promised here is snapshot of the current state of scene 3's fxtree. It is crazy, but it is almost working! I'm having trouble matting some things, I've been attempting to reuse passes into the matte connection of composite nodes and while this is working in most cases, its not working for the fire. I'll need to render a matte for the tiger and canary for the frames when they are in front of the fire.




Thursday, March 29, 2007

promo image of the moose




Ok, so the film isn't available on DVD yet, but it will be soooooo soooooon ;o)



















recentering audio to 0 in SoundTrackPro

Sometimes an audio recording is not centered at 0. To fix this in SoundTrack Pro, switch from Actions to Analysis, expand Analysis type, check DC_Offset and click Analyse. Then select the item on the list below and press Fix.

Tuesday, March 27, 2007

Smoke and Fire

Everything is rendered and composited and unless there are some hidden compositing issues I am almost ready to press the final composite button ;o) The last thing that I'm tweaking is the smoke and fire on the sofa. The start of it is great, but it's not working when the emitter on the sofa is scaled. I've just switched from having 1 emitter on the sofa to having 3 and it looks good in the render region. I also removed the collision that I had set up to the sofa geometry, I'm hoping that this is what was causing the fire to take so long to render.

Anyway, here goes to launching the smoke and fire renders and hoping that will be it!

Tuesday, March 20, 2007

Fire crashing

hmm this is the second time I've had trouble rendering a fire particle pass (using sprites). Rendering from the command line would render 2 or 3 frames and then the window would close. Rendering interactively would crash XSI. The first time this happened a few months ago I changed the sprite (just by duplicating it and changing its name). Today changing the sprite didn't solve the issue. Today's solution was to duplicate the entire PType (I have 2 emitters that were using the same Ptype). I saved the PType preset and applied it to the second emitter. The color animation on the Ptype didn't get saved :o( so I copied the animation from the original ptype to the duplicate. The pass is now rendering more than 2 frames again from the command line.

Sunday, March 18, 2007

rendering and compositing

Yes the smoking moose film is still in progress. I'm still rendering and compositing however I have started to finalize the sound track because I believe the picture is locked. I needed to add a few highlights and shadows -- these are rendering now. Next I need to render a few tweaks to the fire and smoke (but these are quite close to final). I'm not 100% happy with the water so that is next on my list of fixes.

I will post a picture of scene 3's fxtree soon. It is completely insane and although I'm sure there would be a better way to composite it, I am just making it work to get the film done ;o)

creating QuickTime movies for Flash Video

The sync of the FLash Video of my Eyedoll video is much better. After struggling with the Raccoon animation I did for Strut your Reel (and blaming it on Flash video ;o) I did a bit more research on Flash Video encoding and found this article on the Adobe site which helped a lot. Although it recommends using a frame rate of 15 or 12 fps, I stuck with 30 fps (the original animation was at 24fps and I used the retime linear tool in the fxtree to retime the rendered pics). The big piece of the puzzle though is the data rate, which for some reason I had ignored when encoding the raccoon. Big mistake, I'm pretty certain that is what is causing the bad sync.

I might try 15 or 12 fps next time I do one of these things. Especially since that will mean fewer frames to render ;o)

Just a Little Bug

Here's something I did for the AniBOOM's Eyedoll contest. If you like it, head on over to AniBOOM to vote for it!


Thursday, February 22, 2007

happy new year of the golden pig






Another new year to celebrate!


There are no golden pigs in my smoking moose film, which is, still in-progress. It's moved into the compositing stage, although I still have FX passes to render for the huge scene 3, I'm trying to get the rendering and compositing of the room and characters done and then I'll add the Smoke, Fire and Water passes.

Wednesday, January 31, 2007

Strutyourreel.com 10 second contest

Here's my entry to January's Strut your reel animation contest.



The animation was the easy part! The sync is a bit off on YouTube which I am blaming on the conversion process. The first version I uploaded was completely out-of-sync, I believe because I had animated it at 24 fps. I switched to 29.97 and then to 30 fps and it is better, but after uploading many different versions of 30 fps I realized that I could upload the same clip but the sync would be a bit different after the conversion. That said, the best results seemed to be with: 30fps source, converting the sound to mp3, exporting a .mp4 file using the MPEG-4 Codec (although uploading the same clip twice still resulted in slightly different audio synchronisation).

You can see all the entries at strutyourreel

Friday, January 12, 2007

fcurve madness

When fixing animation always remember to double check fcurves. Two things have recently driven me mad!

(a) on curves using spline interpolation if 2 keyframes are of the same value make sure that you use plateau slopes so that the value between the 2 keyframes does not exceed the 2 keyframes;

(b) if you retime animation make sure that there are no keyframes that are not on frames -- this can be achieved by selecting the keyframes and choosing "move keys to nearest frames". However, this may not work IF there is already a keyframe on the nearest frame and you may end up with a keyframe immediately before or after... if you're working in the dopesheet you won't see this stray keyframe

So the lesson of the day is, if you have movement where you don't expect there to be movement, double check the fcurves for the slope between frames and for extra keys between frames.

Thursday, January 04, 2007

RGBA Matte Pass - override ignored if color correction node exists in render tree

One of the comments I received regarding the film was that the carpet didn't have enough resolution. I was simply using a low res texture of a braided rug and had become used to it. Since I didn't have a high res texture I've been testing various methods of creating a higher resolution carpet and have tried a number of different ways (including modeling the braid and using skeletons to wrap it into a rug -- which was way too big of a model to actually use and didn't end up looking that good ;o). I also tried painting a photoshop image (with painted bump map) -- this method looked great in the small tests that I did but when I made the large final rug -- it didn't look so great. Finally I ended up using the fabric procedural shader and after lots of tweaking I have something that I think is acceptable, although I have to give up on the braided rag rug look and accept a rug look.

Now that I've got the rug geometry I thought I could just render it in a RGBA matte pass and composite it into the other renders. However, when I made the matte pass (using the preset) -- the characters appeared in the render in full RGB - while the rest of the objects were as expected rendered in black.

After a bit of searching I discovered that this was being caused by having extra nodes in the render trees -- on 2 of the characters I had a color correction and on another I had a intensity change. Removing these and recreating the pass gives me the pass as I would like it to be. However, this will cause a problem when/if I need to re-render any of the characters as they will no longer match the other frames.

For scenes 1 and 2, since I need to re-render the beauty pass anyway, I'll just add the new carpet to the beauty pass. Scene 3 will be a bit more of a problem.

I'm still using XSI 4.2 so this is possibly fixed in a more recent version.

Tuesday, December 26, 2006

another year over, a new one on the way!







Happy Holidays!








Film Update:
I've stopped rendering the film in order to work on my demo reel. I'm looking for a job as an animator (using XSI in preference ;o). If anyone knows of an opportunity please email me : tiger at smokingmoose dot com.

Sunday, December 03, 2006

tweaking final gathering settings

My small render (250x141) is completed and composited, sent out for feedback and feedback received. Between the time I sent it out and received feedback I started the final res render (1280x720) and discovered to my horror that the final gathering pass was taking up to 23 minutes a frame to render. I went back in to the render settings to tweak them.

Here is a resume what Dave Lajoie wrote in a pdf about final gather settings (I think the pdf is from XSI 3.0 release -- some of the settings are no longer named the same -- you can get it here) :

"So to recap on FG accuracy and radius, [...] here are the different combinations and permutations:
• When Radius is small (0.01-0.2) and Accuracy is high (1000-3000), the render speed is the slowest but the render quality is the best. Usually these settings are suggested to remove FG flickering. Since each frame contains a lot of FG samples, it is suggested that you rebuild the FG map at each frame. Otherwise the FG map file will grow too rapidly and the renderer will run out of memory.
• When Radius is Large (1-100) and Accuracy is High (1000-3000), render speed is a little faster. This combination is perfect for smoothing out the FG result, giving the rendered image a more blurry effect. Again it is suggested that you rebuild the FG map at each frame since the FG accuracy is high.
• When the Radius is small (0.01-0.2) and Accuracy is low (100-500), the FG result is poor. I suggest that you use this combination only for preview purposes.
• Lastly, when the Radius is large (1-100) and Accuracy is low (100-500), the FG settings are ideal for an Image based lighting pass, as long as the image used for the lighting pass doesn’t contain too much high frequency detail. It is strongly suggested that you blur the image that you use for the image based lighting pass, since this allows you to use low Accuracy and a large Radius, which will, in turn, save precious rendering time.

Very important to remember:
If Radius is small, Accuracy needs to be high.
If Radius is large, Accuracy can be lowered."

For my smoking moose purposes I chose the 4th option - large radius and low accuracy using image based lighting. The min radius is set to 20, the max to 50, the accuracy is set to 100 and the filter is set to 1. I'm using a constant image for the image based lighting pass as well as a few constant color cards to bounce rays off. Since I'm also rendering a dirtmap pass I can get away with the larger radius and lower accuracy.

Also, Dave's pdf mentioned that high frequency textures should use lower radius and higher accuracy -- the braided rag rug is a very high frequency texture -- this could explain the high render times. So I used a trick mentioned in the pdf:

"Another trick which can save a lot of time is to use a ray_type shader, which allows you to use two different rendertrees, one for camera rays and one for Final Gathering rays. With this approach you can use a simpler rendertree to remove high frequency from the surrounding object’s surface."

The FG render pass is down to 2 to 6 minutes per frame! Of course the other passes also take time, so the total combined render time is higher than 6 minutes, but it's still a lot less than if I had continued rendering the FG pass with low radius and high accuracy!

The "rebuild" options refer to the Final Gathering Map and have changed since the pdf was written. I'm using XSI 4.2 and the options I have are:
  • Overwrite
  • Append
  • Generate
Since there my film has a lot of small camera moves and a lot of characters moving around, I've set this to append. See chapter 15 of the Shaders, Lights and Cameras user guide for the details.

Thanks to Dave wherever you are!.

Now on to fixing some of the stuff I received feedback on.