Actually, I do this all of the time on AIX and Linux, including automated
production for a web site of dozens of animations daily. Granted the
machines I am using happen to have a few GB of RAM, but it's not need for
this purpose.
Yes, convert does use memory. You need to increase the cache size for
convert (i.e., convert -cache n, where n is the number of MB). Temporary
files are written to $TMPDIR, which by default points to /tmp. If /tmp
isn't big enough, just point it to a filesystem with enough space, and make
the cache large.
You can do this in other ways to be more efficient, such as saving the
image to separate files, and process them via a script, which does
operations per file prior to MPEG-encoding.
David Thompson <[EMAIL PROTECTED]>@opendx.watson.ibm.com on
10/18/2003 02:15:38 AM
Please respond to [email protected]
Sent by: [EMAIL PROTECTED]
To: [email protected]
cc:
Subject: Re: [opendx-users] Creating large movies
I do this all the time using a Mac and Quicktime Pro. Just save the
images out separately as a series into a folder and then import the
image sequence into Quicktime.
David
>I am trying to convert some visual program animations to mpeg (or any
>other movie format). I have had some success with using the Continuous
>Saving option of the Save Image command to save my files as ImageMagick
>.miff files, then using ImageMagick's convert command to convert .miff
>to .mpeg. This procedure fails for large movies (say, 200 frames or
>more) because convert seems to be loading the entire movie into memory
>before converting. My 1 GB machine runs out of memory quite quickly in
>this scenario.
>
>Does anyone have a suggestion for creating large movies that does not
>require gigabytes of RAM?
>
>Thanks,
>Jim Amundson
--
.............................................................................
David L. Thompson Visualization and Imagery Solutions,
Inc.
mailto:[EMAIL PROTECTED] 5515 Skyway Drive, Missoula, MT 59804
Phone : (406)756-7472
