What we did differently:
After the first test we realised we would need a ton more photos to get a better quality result, so this time we took over twice the previous amount: around 36. This would make the bullet flow easily and give a more fluid trajectory instead of having massive jumps which were all too common in the first test. Also another big problem was how the bullet appeared to jump and move on its travels, we instantly solved this by sticking it to a white background. The background was key in this test because the illusion in making the audience think the bullet has moved but instead the camera is only getting closer to it. To do all this we simply blue-tacked a glue stick lid to the projector board and attached the camera to a box resting on some books we moved forward a centimetre after each photo.
To edit the photos we added them to a imovie project on the school Emacs and made each photo transaction 0.1 of a second, we debated on the speed but this appeared to be the best to reflect how fast a bullet travels but also to make the audience jump.
Overall I like how the bullet takes a while to get close and appears to be a blue dot for the first half, this means the audience has time to guess what it is before it gets bigger and closer within a second and finally ends covering the majority of the screen. We could have stabilised the camera more and ensured it was on a continuous path to avoid any mistakes like a jumpy bullet but the end result showed we could do the final bullet shot within 50 pictures, we would just have to be extremely steady and keep the camera on a constant and planned path. This method is extremely better than the first.
Post a Comment