cortex: org/capture-video.org comparison

comparison org/capture-video.org @ 0:92f8d83b5d0b

initial import: I've made hearing and vision, and am working on touch.

author	Robert McIntyre <rlm@mit.edu>
date	Sun, 16 Oct 2011 05:12:19 -0700
parents
children	50c92af2018e

comparison

equal deleted inserted replaced

--1:000000000000
+:92f8d83b5d0b
+#+title: Capture Live Video Feeds from JMonkeyEngine
+#+author: Robert McIntyre
+#+email: rlm@mit.edu
+#+MATHJAX: align:"left" mathml:t path:"../aurellem/src/MathJax/MathJax.js"
+#+STYLE: <link rel="stylesheet" type="text/css" href="../aurellem/src/css/aurellem.css"/>
+#+OPTIONS:   H:3 num:t toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t <:t
+#+BABEL: :exports both :noweb yes :cache no :mkdirp yes
+#+description: Capture video from a JMonkeyEngine3 Application with Xuggle, and use gstreamer to compress the video to upload to YouTube.
+#+keywords: JME3, video, Xuggle, JMonkeyEngine, youtube, capture video, Java
+#+INCLUDE: ../aurellem/src/templates/level-0.org
+:PROPERTIES:
+:EXPORT_FILE_NAME: ../whatever.html
+:END:
+* The Problem
+So you've made your cool new JMonkeyEngine3 game and you want to
+create a demo video to show off your hard work. Screen capturing is
+the most straightforward way to do this, but it can slow down your
+game and produce low-quality video as a result. A better way is to
+record a video feed directly from the game while it is
+running.
+In this post, I'll explain how you can alter your JMonkeyEngine3 game
+to output video while it is running. The main trick is to alter the
+pace of JMonkeyEngine3's in-game time: we allow the engine as much
+time as it needs to compute complicated in-game events and to encode
+video frames. As a result, the game appears to speed up and slow down
+as the computational demands shift, but the end result is perfectly
+smooth video output at a constant framerate.
+* Game-time vs. User-time vs. Video-time
+A standard JME3 application that extends =SimpleApplication= or
+=Application= tries as hard as it can to keep in sync with
+/user-time/.  If a ball is rolling at 1 game-mile per game-hour in the
+game, and you wait for one user-hour as measured by the clock on your
+wall, then the ball should have traveled exactly one game-mile. In
+order to keep sync with the real world, the game throttles its physics
+engine and graphics display.  If the computations involved in running
+the game are too intense, then the game will first skip frames, then
+sacrifice physics accuracy.  If there are particuraly demanding
+computations, then you may only get 1 fps, and the ball may tunnel
+through the floor or obstacles due to inaccurate physics simulation,
+but after the end of one user-hour, that ball will have traveled one
+game-mile.
+When we're recording video, we don't care if the game-time syncs with
+user-time, but instead whether the time in the recorded video
+(video-time) syncs with user-time. To continue the analogy, if we
+recorded the ball rolling at 1 game-mile per game-hour and watched the
+video later, we would want to see 30 fps video of the ball rolling at
+1 video-mile per /user-hour/. It doesn't matter how much user-time it
+took to simulate that hour of game-time to make the high-quality
+recording.
+* COMMENT Two examples to clarify the point:
+** Recording from a Simple Simulation
+*** Without a Special Timer
+You have a simulation of a ball rolling on an infinite empty plane at
+one game-mile per game-hour, and a really good computer. Normally,
+JME3 will throttle the physics engine and graphics display to sync the
+game-time with user-time. If it takes one-thousandth of a second
+user-time to simulate one-sixtieth of a second game time and another
+one-thousandth of a second to draw to the screen, then JME3 will just
+sit around for the remainder of $\frac{1}{60} - \frac{2}{1000}$
+user-seconds, then calculate the next frame in $\frac{2}{1000}$
+user-seconds, then wait, and so on. For every second of user time that
+passes, one second of game-time passes, and the game will run at 60
+frames per user-second.
+*** With a Special Timer
+Then, you change the game's timer so that user-time will be synced to
+video-time. Assume that encoding a single frame takes 0 seconds
+user-time to complete.
+Now, JME3 takes advantage of all available resources. It still takes
+one-thousandth of a second to calculate a physics tick, and another
+one-thousandth to render to the screen. Then it takes 0 seconds to
+write the video frame to disk and encode the video. In only one second
+of user time, JME3 will complete 500 physics-tick/render/encode-video
+cycles, and $\frac{500}{60}=8\frac{1}{3}$ seconds of game-time will
+have passed.  Game-time appears to dilate $8\frac{1}{3}\times$ with
+respect to user-time, and in only 7.2 minutes user-time, one hour of
+video will have been recorded. The game itself will run at 500 fps.
+When someone watches the video, they will see 60 frames per
+user-second, and $\frac{1}{60}$ video-seconds will pass each frame. It
+will take exactly one hour user-time (and one hour video-time) for the
+ball in the video to travel one video-mile.
+** Recording from a Complex Simulation
+*** Without a Special Timer
+You have a simulation of a ball rolling on an infinite empty plane at
+one game-mile per game-hour accompanied by multiple explosions
+involving thousands of nodes, particle effects, and complicated shadow
+shaders to create realistic shadows. You also have a slow
+laptop. Normally, JME3 must sacrifice rendering and physics simulation
+to try to keep up.  If it takes $\frac{1}{120}$ of a user-second to
+calculate $\frac{1}{60}$ game-seconds, and an additional
+$\frac{1}{60}$ of a user-second to render to screen, then JME3 has
+it's work cut out for it.  In order to render to the screen, it will
+first step the game forward by up to four physics ticks before
+rendering to the screen. If it still isn't fast enough then it will
+decrease the accuracy of the physics engine until game-time and user
+time are synched or a certain threshold is reached, at which point the
+game visibly slows down. In this case, JME3 continuously repeat a
+cycle of two physics ticks, and one screen render. For every
+user-second that passes, one game-second will pass, but the game will
+run at 30 fps instead of 60 fps like before.
+*** With a Special Timer
+Then, you change the game's timer so that user-time will be synced to
+video-time. Once again, assume video encoding takes $\frac{1}{60}$ of
+a user-second.
+Now, JME3 will spend $\frac{1}{120}$ of a user-second to step the
+physics tick $\frac{1}{60}$ game-seconds, $\frac{1}{60}$ to draw to
+the screen, and an additional $\frac{1}{60}$ to encode the video and
+write the frame to disk. This is a total of $\frac{1}{24}$
+user-seconds for each $\frac{1}{60}$ game-seconds. It will take
+$(\frac{60}{24} = 2.5)$ user-hours to record one game-hour and game-time
+will appear to flow two-fifths as fast as user time while the game is
+running. However, just as in example one, when all is said and done we
+will have an hour long video at 60 fps.
+* COMMENT proposed names for the new timer
+# METRONOME
+# IsoTimer
+# EvenTimer
+# PulseTimer
+# FixedTimer
+# RigidTimer
+# FixedTempo
+# RegularTimer
+# MetronomeTimer
+# ConstantTimer
+# SteadyTimer
+* =IsoTimer= records time like a metronome
+The easiest way to achieve this special timing is to create a new
+timer that always reports the same framerate to JME3 every time it is
+called.
+=./jme3/src/core/com/jme3/system/IsoTimer.java=
+#+include ./jme3/src/core/com/jme3/system/IsoTimer.java src java
+If an Application uses this =IsoTimer= instead of the normal one, we
+can be sure that every call to =simpleUpdate=, for example, corresponds
+to exactly $(\frac{1}{fps})$ seconds of game-time.
+In order to facilitate setting the =Timer= in user code, I added
+getter and setter methods to =Application.java=.
+In =./jme3/src/core/com/jme3/app/Application.java= I added:
+#+include ./jme3/src/core/com/jme3/app/Application.java src java :lines "340-356"
+* Encoding to Video
+Now that the issue of time is solved, we just need a function that
+writes each frame to a video.  We can put this function somewhere
+where it will be called exactly one per frame.
+JME3 already provides exactly the class we need: the =SceneProcessor=
+class can be attached to any viewport and the methods defined therein
+will be called at the appropriate points in the rendering process.
+If you want to generate video from Java, a great option is [[http://www.xuggle.com/][Xuggle]]. It
+takes care of everything related to video encoding and decoding and
+runs on Windows, Linux and Mac.  Out of all the video frameworks for
+Java I personally like this one the best.
+Here is a =SceneProcessor= that uses [[http://www.xuggle.com/][Xuggle]] to write each frame to a
+video file.
+=./jme3/src/core/com/jme3/app/VideoProcessor.java=
+#+include ./jme3/src/core/com/jme3/app/VideoProcessor.java src java
+With this, we are able to record video!
+* Hello Video!
+I've taken [[http://code.google.com/p/jmonkeyengine/source/browse/trunk/engine/src/test/jme3test/helloworld/HelloLoop.java][=./jme3/src/test/jme3test/helloworld/HelloLoop.java=]] and
+augmented it with video output as follows:
+=./jme3/src/test/jme3test/helloworld/HelloVideo.java=
+#+include ./jme3/src/test/jme3test/helloworld/HelloVideo.java src java
+The videos are created in the =hello-video= directory
+#+begin_src sh :results verbatim
+du -h hello-video/*
+#+end_src
+#+results:
+: 932K	hello-video/hello-video-moving.flv
+: 640K	hello-video/hello-video-static.flv
+And can be immediately uploaded to youtube
+- [[http://www.youtube.com/watch?v=C8gxVAySaPg][hello-video-moving.flv]]
+#+BEGIN_HTML
+<iframe width="425" height="349"
+	src="http://www.youtube.com/embed/C8gxVAySaPg"
+	frameborder="0" allowfullscreen>
+</iframe>
+#+END_HTML
+- [[http://www.youtube.com/watch?v=pHcFOtIS07Q][hello-video-static.flv]]
+#+BEGIN_HTML
+<iframe width="425" height="349"
+	src="http://www.youtube.com/embed/pHcFOtIS07Q"
+	frameborder="0" allowfullscreen>
+</iframe>
+#+END_HTML
+* Summary
+It's quite easy to augment your own application to record video,
+almost regardless of how complicated the actual application is.  You
+can also record from multiple ViewPorts as the above example shows.
+The process for adding video recording to your application is as
+follows:
+Assuming you want to record at 30 fps, add:
+#+begin_src java :exports code
+this.setTimer(new IsoTimer(30));
+#+end_src
+Somewhere in the initialization of your Application.  Right now, you
+will have to add the =setTimer= method to =Application=, but hopefully
+this method will be included soon by the JMonkeyEngine3 team.
+Then, you create a =VideoProcessor= object and attach it to the
+=ViewPort= from which you want to record.
+If you want to record from the game's main =ViewPort= to a file called
+=/home/r/record.flv=, then add:
+#+begin_src java :exports code
+viewPort.addProcessor(new VideoProcessor(new File("/home/r/record.flv")));
+#+end_src
+Do this for each =ViewPort= from which you want to record.  The more
+ViewPorts from which you record, the slower the game will run, but
+this slowness will not affect the final video output.
+* More Examples
+** Hello Physics
+=HelloVideo= is boring. Let's add some video capturing to =HelloPhysics=
+and create something fun!
+This example is a modified version of =HelloPhysics= that creates four
+simultaneous views of the same scene of cannonballs careening into a
+brick wall.
+=./jme3/src/test/jme3test/helloworld/HelloPhysicsWithVideo.java=
+#+include ./jme3/src/test/jme3test/helloworld/HelloPhysicsWithVideo.java src java
+Running the program outputs four videos into the =./physics-videos=
+directory.
+#+begin_src sh :exports both :results verbatim
+ls ./physics-videos | grep -
+#+end_src
+#+results:
+: lower-left.flv
+: lower-right.flv
+: upper-left.flv
+: upper-right.flv
+The videos are fused together with the following =gstreamer= commands:
+#+begin_src sh :results silent
+cd physics-videos
+gst-launch-0.10 \
+filesrc location=./upper-right.flv ! decodebin ! \
+videoscale ! ffmpegcolorspace ! \
+video/x-raw-yuv, width=640, height=480, framerate=25/1 ! \
+videobox border-alpha=0 left=-640 ! \
+videomixer name=mix ! ffmpegcolorspace ! videorate ! \
+video/x-raw-yuv, width=1280, height=480, framerate=25/1 ! \
+jpegenc ! avimux  ! filesink location=upper.flv \
+\
+filesrc location=./upper-left.flv ! decodebin ! \
+videoscale ! ffmpegcolorspace ! \
+video/x-raw-yuv, width=640, height=480, framerate=25/1 ! \
+videobox right=-640 ! mix.
+#+end_src
+#+begin_src sh :results silent
+cd physics-videos
+gst-launch-0.10 \
+filesrc location=./lower-left.flv ! decodebin ! \
+videoscale ! ffmpegcolorspace ! \
+video/x-raw-yuv, width=640, height=480, framerate=25/1 ! \
+videobox border-alpha=0 left=-640 ! \
+videomixer name=mix ! ffmpegcolorspace ! videorate ! \
+video/x-raw-yuv, width=1280, height=480, framerate=25/1 ! \
+jpegenc ! avimux  ! filesink location=lower.flv \
+\
+filesrc location=./lower-right.flv ! decodebin ! \
+videoscale ! ffmpegcolorspace ! \
+video/x-raw-yuv, width=640, height=480, framerate=25/1 ! \
+videobox right=-640 ! mix.
+#+end_src
+#+begin_src sh :results silent
+cd physics-videos
+gst-launch-0.10 \
+filesrc location=./upper.flv ! decodebin ! \
+videoscale ! ffmpegcolorspace ! \
+video/x-raw-yuv, width=1280, height=480, framerate=25/1 ! \
+videobox border-alpha=0 bottom=-480 ! \
+videomixer name=mix ! ffmpegcolorspace ! videorate ! \
+video/x-raw-yuv, width=1280, height=960, framerate=25/1 ! \
+jpegenc ! avimux  ! filesink location=../youtube/helloPhysics.flv \
+\
+filesrc location=./lower.flv ! decodebin ! \
+videoscale ! ffmpegcolorspace ! \
+video/x-raw-yuv, width=1280, height=480, framerate=25/1 ! \
+videobox top=-480 ! mix.
+#+end_src
+#+begin_src sh :results verbatim
+du -h youtube/helloPhysics.flv
+#+end_src
+#+results:
+: 180M	physics-videos/helloPhysics.flv
+Thats a terribly large size!
+Let's compress it:
+** Compressing the HelloPhysics Video
+First, we'll scale the video, then, we'll decrease it's bitrate. The
+end result will be perfect for upload to YouTube.
+#+begin_src sh :results silent
+cd youtube
+gst-launch-0.10 \
+filesrc location=./helloPhysics.flv ! decodebin ! \
+videoscale ! ffmpegcolorspace ! \
+`: # the original size is 1280 by 960` \
+video/x-raw-yuv, width=1280, height=960, framerate=25/1 ! \
+videoscale ! \
+`: # here we scale the video down` \
+video/x-raw-yuv, width=640, height=480, framerate=25/1 ! \
+`: # and here we limit the bitrate` \
+theoraenc bitrate=1024 quality=30 ! \
+oggmux ! progressreport update-freq=1 ! \
+filesink location=./helloPhysics.ogg
+#+end_src
+#+begin_src sh :results verbatim
+du -h youtube/helloPhysics.ogg
+#+end_src
+#+results:
+: 13M	youtube/helloPhysics.ogg
+[[http://www.youtube.com/watch?v=WIJt9aRGusc][helloPhysics.ogg]]
+#+begin_html
+<iframe width="425" height="349"
+	src="http://www.youtube.com/embed/WIJt9aRGusc?hl=en&fs=1"
+	frameborder="0" allowfullscreen>
+</iframe>
+#+end_html
+** COMMENT failed attempts
+Let's try the [[http://diracvideo.org/][Dirac]] video encoder.
+#+begin_src sh :results verbatim
+cd youtube
+START=$(date +%s)
+gst-launch-0.10 \
+filesrc location=./helloPhysics.flv ! decodebin ! \
+videoscale ! ffmpegcolorspace ! \
+video/x-raw-yuv, width=1280, height=960, framerate=25/1 ! \
+schroenc ! filesink location=./helloPhysics.drc > /dev/null
+echo `expr $(( $(date +%s) - $START))`
+#+end_src
+#+results:
+: 142
+That took 142 seconds. Let's see how it does compression-wise:
+#+begin_src sh :results verbatim
+du -h ./youtube/helloPhysics.drc
+#+end_src
+#+results:
+: 22M	./physics-videos/helloPhysics.drc
+#+begin_src sh :results verbatim
+cd youtube
+START=$(date +%s)
+gst-launch-0.10 \
+filesrc location=./helloPhysics.flv ! decodebin ! \
+videoscale ! ffmpegcolorspace ! \
+video/x-raw-yuv, width=1280, height=960, framerate=25/1 ! \
+theoraenc ! oggmux ! filesink location=./helloPhysics.ogg \
+> /dev/null
+echo `expr $(( $(date +%s) - $START))`
+#+end_src
+#+results:
+: 123
+#+begin_src sh :results verbatim
+du -h youtube/helloPhysics.ogg
+#+end_src
+#+results:
+: 59M	physics-videos/helloPhysics.ogg
+=*.drc= files can not be uploaded to YouTube, so I'll go for the
+avi file.
+** COMMENT text for videos
+Video output from JMonkeyEngine3 (www.jmonkeyengine.org/) using Xuggle
+(www.xuggle.com/).  Everything is explained at
+http://aurellem.org/cortex/capture-video.html.
+Video output from JMonkeyEngine3 (www.jmonkeyengine.org/) HelloPhysics
+demo application using Xuggle (www.xuggle.com/).  Everything is
+explained at http://aurellem.org/cortex/capture-video.html.  Here,
+four points of view are simultaneously recorded and then glued
+together later.
+JME3 Xuggle Aurellem video capture
+* Sample Videos
+I encoded most of the original JME3 Hello demos for your viewing
+pleasure, all using the =VideoProcessor= and =IsoTimer= classes.
+** HelloTerrain
+[[http://youtu.be/5_4wyDFwrVQ][HelloTerrain.avi]]
+#+begin_html
+<iframe width="425" height="349"
+	src="http://www.youtube.com/embed/5_4wyDFwrVQ"
+	frameborder="0" allowfullscreen>
+</iframe>
+#+end_html
+** HelloAssets
+[[http://www.youtube.com/watch?v=oGg-Q6k1BM4][HelloAssets.avi]]
+#+begin_html
+<iframe width="425" height="349"
+	src="http://www.youtube.com/embed/oGg-Q6k1BM4?hl=en&fs=1"
+	frameborder="0" allowfullscreen>
+</iframe>
+#+end_html
+** HelloEffects
+[[http://www.youtube.com/watch?v=TuxlLMe53hA][HelloEffects]]
+#+begin_html
+<iframe width="425" height="349"
+	src="http://www.youtube.com/embed/TuxlLMe53hA?hl=en&fs=1"
+	frameborder="0" allowfullscreen>
+</iframe>
+#+end_html
+** HelloCollision
+[[http://www.youtube.com/watch?v=GPlvJkiZfFw][HelloCollision.avi]]
+#+begin_html
+<iframe width="425" height="349"
+	src="http://www.youtube.com/embed/GPlvJkiZfFw?hl=en&fs=1"
+	frameborder="0" allowfullscreen>
+</iframe>
+#+end_html
+** HelloAnimation
+[[http://www.youtube.com/watch?v=SDCfOSPYUkg][HelloAnimation.avi]]
+#+begin_html
+<iframe width="425" height="349"
+	src="http://www.youtube.com/embed/SDCfOSPYUkg?hl=en&fs=1"
+	frameborder="0" allowfullscreen>
+</iframe>
+#+end_html
+** HelloNode
+[[http://www.youtube.com/watch?v=pL-0fR0-ilQ][HelloNode.avi]]
+#+begin_html
+<iframe width="425" height="349"
+	src="http://www.youtube.com/embed/pL-0fR0-ilQ?hl=en&fs=1"
+	frameborder="0" allowfullscreen>
+</iframe>
+#+end_html
+** HelloLoop
+[[http://www.youtube.com/watch?v=mosZzzcdE5w][HelloLoop.avi]]
+#+begin_html
+<iframe width="425" height="349"
+	src="http://www.youtube.com/embed/mosZzzcdE5w?hl=en&fs=1"
+	frameborder="0" allowfullscreen>
+</iframe>
+#+end_html
+*** COMMENT x-form the other stupid
+progressreport update-freq=1
+gst-launch-0.10 \
+filesrc location=./helloPhy ! decodebin ! \
+videoscale ! ffmpegcolorspace ! \
+video/x-raw-yuv, width=1280, height=960, framerate=25/1 ! \
+x264enc ! avimux ! filesink location=helloPhysics.avi \
+gst-launch-0.10 \
+filesrc location=./HelloAnimationStatic.flv ! decodebin ! \
+videoscale ! ffmpegcolorspace ! \
+video/x-raw-yuv, width=640, height=480, framerate=25/1 ! \
+videobox border-alpha=0 left=-640 ! \
+videomixer name=mix ! ffmpegcolorspace ! videorate ! \
+video/x-raw-yuv, width=1280, height=480, framerate=25/1 ! \
+x264enc ! avimux ! progressreport update-freq=1 ! \
+filesink location=../youtube/HelloAnimation.avi \
+\
+filesrc location=./HelloAnimationMotion.flv ! decodebin ! \
+videoscale ! ffmpegcolorspace ! \
+video/x-raw-yuv, width=640, height=480, framerate=25/1 ! \
+videobox right=-640 ! mix.
+gst-launch-0.10 \
+filesrc location=./HelloCollisionMotion.flv ! decodebin ! \
+videoscale ! ffmpegcolorspace ! \
+video/x-raw-yuv, width=800, height=600, framerate=25/1 ! \
+x264enc bitrate=1024 ! avimux ! \
+filesink location=../youtube/HelloCollision.avi
+gst-launch-0.10 \
+filesrc location=./HelloEffectsStatic.flv ! decodebin ! \
+videoscale ! ffmpegcolorspace ! \
+video/x-raw-yuv, width=640, height=480, framerate=25/1 ! \
+videobox border-alpha=0 left=-640 ! \
+videomixer name=mix ! ffmpegcolorspace ! videorate ! \
+video/x-raw-yuv, width=1280, height=480, framerate=25/1 ! \
+x264enc bitrate=1024 ! avimux ! progressreport update-freq=1 ! \
+filesink location=../youtube/HelloEffects.avi \
+\
+filesrc location=./HelloEffectsMotion.flv ! decodebin ! \
+videoscale ! ffmpegcolorspace ! \
+video/x-raw-yuv, width=640, height=480, framerate=25/1 ! \
+videobox right=-640 ! mix.
+gst-launch-0.10 \
+filesrc location=./HelloTerrainMotion.flv ! decodebin ! \
+videoscale ! ffmpegcolorspace ! \
+video/x-raw-yuv, width=800, height=600, framerate=25/1 ! \
+x264enc bitrate=1024 ! avimux ! \
+filesink location=../youtube/HelloTerrain.avi
+gst-launch-0.10 \
+filesrc location=./HelloAssetsStatic.flv ! decodebin ! \
+videoscale ! ffmpegcolorspace ! \
+video/x-raw-yuv, width=640, height=480, framerate=25/1 ! \
+videobox border-alpha=0 left=-640 ! \
+videomixer name=mix ! ffmpegcolorspace ! videorate ! \
+video/x-raw-yuv, width=1280, height=480, framerate=25/1 ! \
+x264enc bitrate=1024 ! avimux ! progressreport update-freq=1 ! \
+filesink location=../youtube/HelloAssets.avi \
+\
+filesrc location=./HelloAssetsMotion.flv ! decodebin ! \
+videoscale ! ffmpegcolorspace ! \
+video/x-raw-yuv, width=640, height=480, framerate=25/1 ! \
+videobox right=-640 ! mix.
+gst-launch-0.10 \
+filesrc location=./HelloNodeStatic.flv ! decodebin ! \
+videoscale ! ffmpegcolorspace ! \
+video/x-raw-yuv, width=640, height=480, framerate=25/1 ! \
+videobox border-alpha=0 left=-640 ! \
+videomixer name=mix ! ffmpegcolorspace ! videorate ! \
+video/x-raw-yuv, width=1280, height=480, framerate=25/1 ! \
+x264enc bitrate=1024 ! avimux ! progressreport update-freq=1 ! \
+filesink location=../youtube/HelloNode.avi \
+\
+filesrc location=./HelloNodeMotion.flv ! decodebin ! \
+videoscale ! ffmpegcolorspace ! \
+video/x-raw-yuv, width=640, height=480, framerate=25/1 ! \
+videobox right=-640 ! mix.
+gst-launch-0.10 \
+filesrc location=./HelloLoopStatic.flv ! decodebin ! \
+videoscale ! ffmpegcolorspace ! \
+video/x-raw-yuv, width=640, height=480, framerate=25/1 ! \
+videobox border-alpha=0 left=-640 ! \
+videomixer name=mix ! ffmpegcolorspace ! videorate ! \
+video/x-raw-yuv, width=1280, height=480, framerate=25/1 ! \
+x264enc bitrate=1024 ! avimux ! progressreport update-freq=1 ! \
+filesink location=../youtube/HelloLoop.avi \
+\
+filesrc location=./HelloLoopMotion.flv ! decodebin ! \
+videoscale ! ffmpegcolorspace ! \
+video/x-raw-yuv, width=640, height=480, framerate=25/1 ! \
+videobox right=-640 ! mix.

Mercurial > cortex

comparison org/capture-video.org @ 0:92f8d83b5d0b