UpdateCamera takes the same point of view as Image, but allows you to change the resolution to make a bigger picture, say 3000 pixels wide (the height will be calculated for you using the same aspect ratio as Image has). Reduce then allows you to resample the large image to achieve cheap anti-aliasing. So, say the Image is 640x480. You want a final image of 1500 pixels wide with anti-aliasing. Set UpdateCamera to 3000 (resolution) and Reduce to 2 (default). Then WriteImage will see an image that is 1500x1125 (more or less, sometimes roundoff adds/loses a pixel).
In this snapshot, I was not making an animation, so there is no Sequencer feeding Format; I just had 2 strings, one a path, one a filename, to grab various views the client wanted.
ScaleScreen corrects screen objects (legends, colorbars, captions) which are not properly scaled by UpdateCamera/Reduce. Use the same value for 'finalres' in ScaleScreen as you provide as camera resolution in UpdateCamera (normally, I'd data-drive both from the same Integer interactor, but I was lazy here).
Selector(on/off)-Route lets me turn off file writing when I'm fussing with the scene.
If you can't see this image attachment, let me know; I've had trouble with attachments before going to opendx-users.
On Aug 24, 2005, at 1:49 AM, J Dick wrote:
I'm trying to save animation frames, using the<x-tad-bigger>_______________________________
continous save option on the image module, but the
images are overwriting eachother. I'm looking for the
images to save under a single name, but with
increasing numbers after them. For example:
frame01
frame02
frame03
etc.
Any suggestions on how I can do this?
-Jessica
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Chris Pelkie
Scientific Visualization Producer
622 Rhodes Hall, Cornell Theory Center
Ithaca, NY 14853 (607) 254-8794</x-tad-bigger>
