Skip to main content

Image sequence to movie : Mencoder

UPDATE: I have switched over to ffmpeg.

Mencoder works on both Linux and windows and is a great option for the simple, repetitive task of taking an image sequence dumped from a data analysis program and converting it into a movie (to animate the data) [Mencoder help page: movie from image frames].

What I end up using is the following command

mencoder -audiofile sound.wav -oac copy mf://*.jpg -mf fps=25 -ovc lavc -lavcopts vcodec=wmv2 -of avi -o output.avi -vf scale=800:600

-audiofile sound.wav -oac copy tells mencoder that the audio file to attach to the animation is called sound.wav and I want it copied as is (no change in encoding) [more here, and here]. You can omit this if there is no audio file

mf://*.jpg -mf fps=25 -ovc lavc -lavcopts vcodec=wmv2 tells it to take all the .jpg files in the directory and make a movie at 25fps using the microsoft wmv codec

-of avi -o output.avi -vf scale=800:600 The output file is called output.avi and has a size of 800 x 600 pixels in avi format. Omitting -vf scale will keep the original size of the images

Install notes:
  1. Download the binaries [mplayer.hu]
  2. Unzip to a directory /my/mplayer/
  3. Add the root to your path
Labels:

Comments

  1. AnonymousJuly 10, 2008 at 9:10 PM

    This works great - thanks for the tip.

    ReplyDelete

Post a Comment

Popular posts from this blog

A note on Python's __exit__() and errors

Python's context managers are a very neat way of handling code that needs a teardown once you are done. Python objects have do have a destructor method ( __del__ ) called right before the last instance of the object is about to be destroyed. You can do a teardown there. However there is a lot of fine print to the __del__ method. A cleaner way of doing tear-downs is through Python's context manager , manifested as the with keyword. class CrushMe: def __init__(self): self.f = open('test.txt', 'w') def foo(self, a, b): self.f.write(str(a - b)) def __enter__(self): return self def __exit__(self, exc_type, exc_val, exc_tb): self.f.close() return True with CrushMe() as c: c.foo(2, 3) One thing that is important, and that got me just now, is error handling. I made the mistake of ignoring all those 'junk' arguments ( exc_type, exc_val, exc_tb ). I just skimmed the docs and what popped out is that you need to return True or...
Post a Comment
Read more

Store numpy arrays in sqlite

Use numpy.getbuffer (or sqlite3.Binary ) in combination with numpy.frombuffer to lug numpy data in and out of the sqlite3 database: import sqlite3, numpy r1d = numpy.random.randn(10) con = sqlite3.connect(':memory:') con.execute("CREATE TABLE eye(id INTEGER PRIMARY KEY, desc TEXT, data BLOB)") con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", sqlite3.Binary(r1d))) con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", numpy.getbuffer(r1d))) res = con.execute("SELECT * FROM eye").fetchall() con.close() #res -> #[(1, u'1d', <read-write buffer ptr 0x10371b220, size 80 at 0x10371b1e0>), # (2, u'1d', <read-write buffer ptr 0x10371b190, size 80 at 0x10371b150>)] print r1d - numpy.frombuffer(res[0][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] print r1d - numpy.frombuffer(res[1][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] Note that for work where data ty...
Post a Comment
Read more