V&S_4_Reading_In the Blink of An Eye

By jhclaura in Blog, Video and Sounds 0 Comment

First of all, as one-shot scene mentioned in the reading, here’s an one-shot scene I’d love to share, from movie Atonement by Joe Wright. I respect it more after filming by ourselves.

After this project, I find editing is much more easier than filming actually. Just like cooking, without good and fresh materials, you can’t make a cuisine. It helps a lot if you have all the materials you want on hand, thus the things like “in the middle of cooking finding that you don’t have onions at all and you either have to deal with it or just stop cooking and walking out to buy one” won’t happen on you.

There’re two points I find relatively interesting in the reading.

  • Like sleeping therapy, editor helps director to make description more clearly(when things don’t go as what director originally think about, director will defend for it then thus become more aware of the theme/thoughts). It’s so true. We’re both the directors and editors in this class project, and when we started editing, we kind of rethought about the whole concept and became more aware of the shots we missed.
  • Filming and editing are like learning foreign language. You know it well enough but it’s always difficult to speak or even write it. Sometimes you just have to let it go and speak whatever come across your mind, or you’ll be framed by the grammars and then stuck. And this happens in filming/editing as well. A lot of things didn’t follow the script at all. Storyboard and script become a big concept to follow, and improvisation gradually dominates all. But I’m not sure if it’s a good thing, because it seems professional movies and animations follow the script strictly. Some of the final shots look exactly the same with storyboard. That’s probably because they spend a lot of time in the pre-production and sometimes it takes years, so they can make sure what they really want clearly and then be able to follow the script. And maybe it’s also related to the scale. It costs hugely so you don’t have space to waste, and it needs clear descriptions for a lot of staff to follow. And it makes me wonder, is it normal and good to improvise in small scale production? For either filming or editing?

Below is my first editing work, and since it’s a fantasy told by reconstructing clips of movies, it’s relatively simpler than filming and editing at the same time.

ICM_3_RainMan & Triangles

By jhclaura in Blog, ICM_Processing 0 Comment

Time flies and here I am sweet ICM homework #3. It’s a collaboration work by Karam and I, and basically we just used each other’s class and try to make some interaction! I got the triangle class from Karam and background idea from Gladys, and this work was inspired by reading The Nature of Code of Daniel Shiffman. Just finished chapter 1. Super good/tough stuff!!

   

Here’s my new born baby(click me click me)! It’s about a person who loves being rained, just enjoys the feeling of being miserable. When rain stops, the smile stops and background went blue. You can click your mouse and make this guy happy again.

For this, I wrote 5 classes… just couldn’t stop, and hit into wall sooo many time. I was like a small rooted tree in the corner of ITP floor on Monday. And here’s are some problems(all about using class in class) and answers(except the last one) from try-and-error process of myself.

  • Where to put the moving code?
    • make sure you can control the position in the { } in which the leading moving codes(e.g. x++) settle
  • If things moves in different way?
    • put moving codes separately in its own class
  • Wants rains start from cloud
    • don’t need to declare Cloud class in Rain class!! can use it directly(tearing)
  • How to make smile affected by rain????

Still can’t solve the last problem. I guess there must be something wrong about my rain drops. I use distance between each rain drop and the man’s head to write some condition codes. The rain drops may seem to be affected well by the man, but I bet it’s actually not what we think they are, and that’s why although I could affect rain drops with the man, I failed to affect the smile with the rain drops? Too complicated. So in the end, I compromised and made the man smile when it’s raining and sad when it’s not.

Maybe it’s time to book an office hour with Dan.

And as usual, below are my baby’s bloody organs(codes).

Continue reading

ICM_02_CloudPaint

By jhclaura in Blog, ICM_Processing 1 Comment

This is the idea of Caitlin and I, a self-made Paint software, for ICM week_02’s homework, making something animated and designed an UI. At first, we were ambitious and made a ideal Paint with multiple function, and even a fancy UI. BUT, it’s just too hard to accomplish 😉  Process of bloody stumbling is as followed:

  1. made 3 floating cubes to choose colors from.
  2. frustrated to find out that the color of every cube’s rim changed when I choose different stroke color.
  3. same thing happened in stroke width.
  4. P A N I C .
  5. Struggling for hours.
  6. thought object-orientation program might be the answer of this puzzle, so started learning OOP from scratch.
  7. excited to have a workable class of drifting clouds.
  8. frustrated to find out that problem still existed.
  9. P A N I C .
  10. Struggling for hours.
  11. so desperate that I started googling my problem.
  12. found out the existence of pushStyle()/popStyle()!
  13. had a bitter(FXCK!)-yet-sweet(YAH!) moment for a while.
  14. added stroke width, eraser, and new paper function to finish my mini-Paint.
  15. L E A R N E D    A    L O T .

And here’s my bloody baby!(click me click me click me)

And below are my bloody baby’s organs(codes).

Continue reading