I decided that the frame rate for my animation should be 12 frames per second as I have been creating a very basic animation that does not need very fluent motion for it to be affective. If I had decided to animate at 24 frames per second, I would have needed to animate on 2s, therefore it was easier to create the animation at 12 frames per second. I did this so that I could save time in the animating of my animation. Other 2-D computer generated animations animate on 24 frames per second and they have a more fluent animation as they make smaller movements in the subject of the animation between the frames of the animation. To improve my animation further I could have used the animation technique of Squash and stretch to be able make the juggling balls look more realistic as they flew through the air. I also could have animated the juggler's arms moving as he juggled the balls in order to make it more realistic. I used 383 frames in my animation, however, if i had chosen to animated on 24 frames per second, it would've meant that my animation would have had 766 frames for the whole animation, but kept the animation the same.
The animation is also only 32 seconds long. I decided to make my animation this length as it is specified in the brief that the animation needs to be between 30-90 seconds. The brief also specifies that the animation will be used as a loading screen on the app and on the website, usually, when apps and website pages load, it does not take much longer than 30 seconds. Therefore, I made the animation this length so that it would fit the brief, but also be the best length so not to bore the audience while their app/web page is loading. Other loading screens for apps have an average length of 5 seconds. This length is a good length for a loading screen as it doesn't take very long for an app to load, however, these loading screens are not very good at introducing their target audience to what the app is about, therefore, I think that 32 seconds is a good length for an animation that introduces the target audience to what the app is about (the festival), and what the content of the app is about (the content of the festival).
The animation is longer than my pre-production materials would suggest that it would be as I underestimated how long the animation would be. As evidenced by my storyboard, I was supposed to create the 'musical wind' in one movement and have all three parts of the 'musical wind' portion of the animation be at once. However, I underestimated how long it would take for me to do that, therefore I continued the animation past where the storyboard ended so that I could reach the full time that it needed to be as said in the brief. To do this, I animated the three separate parts of the animation individually, and added some text at the end so that the loading screen of the animation would be introducing the festival.
When comparing my animation to this animation, it is easy to see how they differ; for starters, the movement in my animation in comparison to this animation is jagged and no smooth. As well as this, my animation is more interesting that this animation as it has a background and music, as well as other features such as the 'musical wind' that is in my animation. In terms of believability, this animation looks more realistic as the arms and facial expressions of the characters move as a normal person would when they juggle, whereas my character does not move. This animation is similar to my animation as they are both about someone juggling with three juggling balls. The frame rate appears to be a lot quicker in this animation in comparison to my animation as the movement is more fluent.
No comments:
Post a Comment