Hamish: > > mpeg_encode or ppmtompeg for r.out.mpeg Benjamin: > There are several mpeg encoders with a binary called mpeg_encode around. > Which one is the one we need, specifically?
from the r.out.mpeg help page: <H2>NOTES</H2> This program requires the program <EM>mpeg_encode</EM> (aka <EM>ppmtompeg</EM>): <P> MPEG-1 Video Software Encoder<BR> (Version 1.3; March 14, 1994) <P> Lawrence A. Rowe, Kevin Gong, Ketan Patel, and Dan Wallach Computer Science Division-EECS, <DD>Univ. of Calif. at Berkeley</DD> <P> Available from Berkeley: <a href="http://bmrc.berkeley.edu/frame/research/mpeg/mpeg_encode.html";>http://bmrc.berkeley.ed u/frame/research/mpeg/mpeg_encode.html</a> <BR>or as part of the netpbm package (<em>ppmtompeg</em>): <a href="http://netpbm.sourceforge.net";>http://netpbm.sourceforge.net</a> > Is ppmtompeg the one that comes with the NetPBM tools? Yes. It is essentially the same code as from Berley, but the NetPBM version is still maintained so it is preferred. (and it's easier to get) Note that this is MPEG-1, and MPEG-1 is slow to encode and creates big files of poor quality. What it has going for it over more modern versions (ie MPEG-4) is widespread deployment of the codec and it is in the public domain. MPEG-4 is supposedly a patent mine field (in the USA). For access to other codecs you could rewrite r.out.mpeg to use the ffmpeg libraries or as a shell script that calls mplayer's mencoder or transcode. Hamish __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ grass-dev mailing list grass-dev@grass.itc.it http://grass.itc.it/mailman/listinfo/grass-dev
