Final Hand In Work

The hand in folder consists of three folders, one has all my illustrative sketches, the second has my storyboards and the third has my mood boards + written discriptions. The loose files consist of the animated 6s8f animation, the entire animatic of my storyboard, the abstract and written treatments in Word Format as well as a link to the blog on a plain txt file.

Inside the Mood Boards folder, I followed the brief and did the written description in a .txt format. However, this seems has to read and unproductive. I played with the idea of adding the word document in there also, and decided to do it regardless of brief specifications. If it’s not supposed to be there, hopefully it’ll just be ignored. I find the brief a little confusing on that wrong. What counts as a plain text format? (my guess is .txt and nothing else).

screenshot-41screenshot-42screenshot-43

Advertisements

Updated Sroryboard

storyboard-1storyboard-2storyboard-3storyboard-4storyboard-5

This is my finalised storyboard. It’s hard to know if it’s up to standard because getting feedback from Zoe isn’t the same as feedback from Melvyn. On panel 17 (page 3), I wanted to cut out that shot, but I didn’t want to faff about and waste time moving all the slides along one thumbnail just to get it looking neat and tidy. This is why I lowered that thumbnails oppacity and wrote ‘cut’ in bit red letters. Hopefully this is an acceptable thing to do.

Another question I had, was handwritten text. I tend to prefer hand writting everything, it helps me concentrate and remember information better and overall, I believe, it creates a more personal, intresting look. However, due to not being able to receove the green-to-go from Melvyn, I’m a littlw unsure as to whether that’s something that’ll mark me down. I like it, therefore I’m keeping it, but I wish I could know if it was okay.

Final Presentation!

title-card12345678910111213141516171820progress-furthertarget-audience192122

This final presentation went without a fault. I am glad I added the storyboard in after the “questions?” panel because Zoe had asked to see it. There wasn’t anything to say negatively about my presentation or project at this stage, or at least I don’t believe there was. Zoe has taken the presentation and blog URL to read through in order to give more solid feedback to Melvyn, which I think is fair enough.

Overall, I am proud of what I achieved and how much work went into it and I believe this presentation shows that succesfully. I’m looking forward to the 1-2-1 next week and hope there’s notjing drastic to change, because it seems if there is that it’s certainly cutting it very close to deadline.

Making our own 1-2-1’s and Presentation Practices

img_4867

When Melvyn cancelled his 1-2-1 session with us, we grouped together (Curtis, Ryan, Reece, Heather, Charlotte, Handyn and I) and did semi-presentation 1-2-6’s instead. It was a very useful and helpful experience where we all got to discuss our successes and failures in a safe environment. This also gave us a change of offering feedback and critically analysing our own work as well as others and aiding with any problems or confusions.

On Tuesday, because we were worried about who we would be presenting to today, we got together (Marta, Reece, Charlotte, Heather, Haydn and I) to present our presentation as practice. It also gave us time to examine what everyone else had done for their presentations and to smoothen our any bumps.

img_4866

Colour makes all the difference

This is probably the first 2D animation I did and felt a sense of pride in achieving. I’m certainly not the best animator, but I try. Regardless, I really enjoyed this process and am glad this is the outcome of all my hard work.

The sound really adds to it, and let’s me slide it seemlesssly into the animatic.

 

Fiddling with (Perfecting?) the bsckground

I seem to have hit an impass with the colours cjosen for the round(wooting) bird and the backgrounds. Nothing works! Here are my most recent attempts using Adobe Kuler and searching “leave”, “plant”, and “branch” to see what other people came up.

This slideshow requires JavaScript.

I’m really liking these. I believe the darker backgrounds (behind the leaf) work better than the lighter ones for the darkness of the leaf and branch themselves help the colour of the birds pop out.
It took a lot of trial and error, but I can finally say I enjoy these and am most likely going to go with them.

The Survival Guide

Whilst constantly struggling with the bounce effect of the Wooting Bird looking succesful in my animation, I decided one early Monday morning to take refuge inside the Animation Survival Guide, praying that there would be some helpful information that I hadn’t already considered/attempted. I began, where I began in first year. At page one. Bizarrly, I have a fascination with the introduction to this guide, it’s strangely terrifying and motivating at the same time.

I know that animating a bouncing ball was one of the, or, actually the first University Animation Task those years ago in first semester (back when I had just learnt to cook shepards pie succesfully – for some reason those memories blend together).

Starting at page 36 is where the magic truly begins “it’s all in the timing and spacing.” In which the depiction of a bounding ball is shown frame by frame and the overlapping and timing is mapped out superbly. It isn’t until p.56 that I started to get a resemblance onto where I was going wrong, how the spacing of the inbetweens can affect the outcome and dividing the frames equally can have a profoundly negative effect on the animation alongside the extremes (p. 52).

In page 94, the bounding ball is depicted explicitely with a sequence of drawings exploring where the ‘contact’ should be, and where it shouldn’t be. When the ball lands on the ground, the force causes if to compact, this gives it more life. Meaning that when it uses the momentom to move onwards and upwards, the speed of the knteracrion withthe surface causes it to warp and strech  more quickly then it landed (by drawing the frame slightly higher than the point of contact).

After studying all this and doing my own quick practices, ( https://youtu.be/HPc-yCyc9pk ,  https://youtu.be/rBCuAdUu8nU ) I’ll give the animated bird another go. Hoewever, I believe my problem lives mostly in the speed in which the bird shoots off the ground (there’s not enough spacefor the necessary frames required, perhaps?)

The Animating Begins

I began animating in photoshop using a small blue pencil (10px wide). I have since deleted it (foolishly) after going over it with a red charcoal brush, in an attempt to neaten the lines so that they’re  more understandable. This animation is still in it’s rough stages and will need improving before I go over the lines in an attempt to finalise it.

Animating to sound is something I found quite difficult. I attempted to dope sheet the bird’s whistling but this seemed unhelpful because I couldn’t get it right. After an hour or so of trying, I threw it away and moved onto classic pencil and paper.

I began making notes of what happens in each sequence of frames (whilst going frame by frame in premierpro). In my first set of notes, I seperated the different movements. This helped me get an idea of how much work each section would be.

img_4833

After doing that, I went through the soundfile and made notes of eat time the whistling was louder and quiter. This is because I wanted the beak of the bird to open wider when the whistle was louder (meaning I needed to get the timing exact).

img_4840

However, when I went to animate, this proved difficult to figure out for I had marked down the seconds as they happened in the entire animatic (therefore my frame counts began at 29s 11f) but the photoshop file when animating began at 0secs 0frames. So I did my calculations again (see image bellow), after making a new sequence in PremierPro and ajusting the times accordingly. As you can see in the photograph bellow, the timecode in the video is in the correct seconds and frames for the entire animatic, but the timecode in the softare itself is reset to 0seconds 0frames at the start of this scene.

img_4839img_4834

I also went through and rewrote the frames of the whistle using these new found calculations for easy access.

img_4836

Once I had finished animating that sequence, I moved on and calculated the bouncing of the other bird in the next shot using this exact same method.

img_4835

There was probably a much much easier way of doing all this, but this tis the way I did it. Isn’t there a saying: If it looks stupid and it works, it aint stupid. Or at least, I hope it isn’t!

So after all that and countless hours sat unmoving animating the whole rough animation.Here it is so far. It’s not perfect and far from finished, but it’s a step in the right direction.

 

 

Background for Animation

I started with some warm up exercices using doted technique and a variety of bright colours.

animation-background

animation-background-2

This slideshow requires JavaScript.

When that proved unsuccesful, I decided to go with a more traditonal colour palett. However, I found difficulty in deciding on the background colour.

To make my choice easier, I imported a see-through screenshot from the storyboard.

animation-background-14animation-background-15animation-background-16

When importing the see through image didn’t help, I took the final designs and imported the two birds side  by side. This showed me that the green shade I had chosen was too dark therefore I brightened it.

It looks fine in my opinion, but I carried on experimenting with colour anyway, using complimentary colours.