1.1 --- a/org/capture-video.org	Sat Feb 18 10:28:14 2012 -0700
     1.2 +++ b/org/capture-video.org	Sat Feb 18 10:59:41 2012 -0700
     1.3 @@ -2,7 +2,7 @@
     1.4  #+author: Robert McIntyre
     1.5  #+email: rlm@mit.edu
     1.6  #+description: Capture video from a JMonkeyEngine3 Application with Xuggle, and use gstreamer to compress the video to upload to YouTube.
     1.7 -#+keywords: JME3, video, Xuggle, JMonkeyEngine, youtube, capture video, Java
     1.8 +#+keywords: JME3, video, Xuggle, JMonkeyEngine, YouTube, capture video, Java
     1.9  #+SETUPFILE: ../../aurellem/org/setup.org
    1.10  #+INCLUDE: ../../aurellem/org/level-0.org
    1.11  
    1.12 @@ -70,7 +70,7 @@
    1.13  # throttles its physics engine and graphics display.  If the
    1.14  # computations involved in running the game are too intense, then the
    1.15  # game will first skip frames, then sacrifice physics accuracy.  If
    1.16 -# there are particuraly demanding computations, then you may only get
    1.17 +# there are particularly demanding computations, then you may only get
    1.18  # 1 fps, and the ball may tunnel through the floor or obstacles due to
    1.19  # inaccurate physics simulation, but after the end of one user-hour,
    1.20  # that ball will have traveled one game-mile.
    1.21 @@ -134,7 +134,7 @@
    1.22  first step the game forward by up to four physics ticks before
    1.23  rendering to the screen. If it still isn't fast enough then it will
    1.24  decrease the accuracy of the physics engine until game-time and user
    1.25 -time are synched or a certain threshold is reached, at which point the
    1.26 +time are synced or a certain threshold is reached, at which point the
    1.27  game visibly slows down. In this case, JME3 continuously repeat a
    1.28  cycle of two physics ticks, and one screen render. For every
    1.29  user-second that passes, one game-second will pass, but the game will
    1.30 @@ -198,7 +198,7 @@
    1.31  where it finalizes the recording (e.g. by writing headers for a video
    1.32  file).
    1.33  
    1.34 -An appropiate interface describing this behaviour could look like
    1.35 +An appropriate interface describing this behavior could look like
    1.36  this:
    1.37  
    1.38  =./src/com/aurellem/capture/video/VideoRecorder.java=
    1.39 @@ -214,7 +214,7 @@
    1.40  =.cleanup()= method, it is only called when the =SceneProcessor= is
    1.41  removed from the =RenderManager=, not when the game is shutting down
    1.42  when the user pressed ESC, for example. To obtain reliable shutdown
    1.43 -behaviour, we also have to implement =AppState=, which provides a
    1.44 +behavior, we also have to implement =AppState=, which provides a
    1.45  =.cleanup()= method that /is/ called on shutdown.
    1.46  
    1.47  Here is an AbstractVideoRecorder class that takes care of the details
    1.48 @@ -311,7 +311,7 @@
    1.49  
    1.50    - Establish an =Isotimer= and set its framerate :: For example, if
    1.51         you want to record video with a framerate of 30 fps, include
    1.52 -       the following line of code somewhere in the initializtion of
    1.53 +       the following line of code somewhere in the initialization of
    1.54         your application: 
    1.55  #+begin_src java :exports code
    1.56  this.setTimer(new IsoTimer(30));
    1.57 @@ -362,7 +362,7 @@
    1.58  : 932K	hello-video/hello-video-moving.flv
    1.59  : 640K	hello-video/hello-video-static.flv
    1.60  
    1.61 -And can be immediately uploaded to youtube
    1.62 +And can be immediately uploaded to YouTube
    1.63  
    1.64  - [[http://www.youtube.com/watch?v=C8gxVAySaPg][hello-video-moving.flv]]
    1.65  #+BEGIN_HTML
    1.66 @@ -471,11 +471,11 @@
    1.67  : 180M	physics-videos/helloPhysics.flv
    1.68  
    1.69  
    1.70 -Thats a terribly large size!
    1.71 +That's a terribly large size!
    1.72  Let's compress it:
    1.73  
    1.74  ** COMMENT Compressing the HelloPhysics Video
    1.75 -First, we'll scale the video, then, we'll decrease it's bitrate. The
    1.76 +First, we'll scale the video, then, we'll decrease it's bit-rate. The
    1.77  end result will be perfect for upload to YouTube.
    1.78  
    1.79  #+begin_src sh :results silent