Re: 12 FPS, 15 FPS, 24 FPS Tests. Which one looks the best?

WARINING Image Heavy Post!


This Tutorial is For Monkeyjam.

First, fire up Monkeyjam, Then go to Settings and change the framerate to 30FPS.
http://www.brickshelf.com/gallery/WAprod/Twos/step1.jpg

Open up the capture window and select "Two" for the Image Hold.
http://www.brickshelf.com/gallery/WAprod/Twos/step2.jpg

Capture a few frames that only need to be at 15 FPS, then select the Image Hold to be "One".
http://www.brickshelf.com/gallery/WAprod/Twos/step4.jpg

Catch a couple more frames with "One" selected for the parts that require smoother animation.
http://www.brickshelf.com/gallery/WAprod/Twos/step5.jpg

Now you've been shooting in two's, hooray!
http://www.brickshelf.com/gallery/WAprod/Twos/step6.jpg

This Isn't part of the tutorial, but I strongly recommend you use the "Stop Motion" Mode, so you can flip between frames and make sure the animation is more fluid.
http://www.brickshelf.com/gallery/WAprod/Twos/step7.jpg

I'll make a tutorial for the technique NickMOC posted when I get the time to. I think I'll submit a few MonkeyJam Tutorials to the Resources page mini/smile.

Re: 12 FPS, 15 FPS, 24 FPS Tests. Which one looks the best?

It seems that the image heavy tutorial posted in the thread has messed up the thread.  The "Quote" and "Post Reply" links no longer work.  Would it be more appropriate for a graphical tutorial like this to be posted on web-site and just the link to that site posted in this thread?

As for "Shooting on twos", I do my filming at 15 FPS ("shooting on ones"?).  If I decide I need to tweak things, I'll import my frames "hold 2" into a new 30 FPS ExpSheet in Monkey Jam.  (I usually use Animator DV Simple + for frame capture to make use of its onionskinning feature.)

Re: 12 FPS, 15 FPS, 24 FPS Tests. Which one looks the best?

It was screwed up before my post, I tried to click the quote button underneath D.J.M.'s post but nothing seemed to happen.

Re: 12 FPS, 15 FPS, 24 FPS Tests. Which one looks the best?

Hey Riley, sorry for blaming your tutorial for the problem, then.  Must be a different bug.