|This is a child page. You can use Parent in the quick nav bar at the top or the bottom of the page to navigate directly back to the parent of this page. Some child pages are more than one level deep, and in that case will require more than one Parent click to reach the outermost document level.|
§ 16.139 - Make Fields
|Quick Reference to Scripting Command|
|Items in CAPS are 0/1 or ranges with more options than just 0/1.|
Ranges other than 0/1 are indicated by brackets, such as [0-2].
This operation is designed primarily for TimeLine usage. The idea is that you have a series of full video resolution frames for either pal or NTSC as your action images. You have 60 of these, one for each field interval in the video stream.
The objective is to output a series of field resolution rather than frame resolution images, with the images taken from the correct odd or even set of scan lines. That's what this operator does - it extracts the correct scan lines from the correct full-frame, based on the odd or even position of the frame in the timeline. The resulting image has half of the scan lines (and so is a field image rather than a frame image.)
Sometimes, the odd/even parity of the images is switched, either because the sequence starts on an odd frame, or because the device you are feeding the images to requires odd lines first. In that case, change the state of the Field Dominance switch, and the fields will be generated in reverse order.
In order to generate animated sequences that are perfectly NTSC or PAL compatible, always generate the animation using the full frame resolution for the video standard you are working with.
For instance, to generate a 1-second, proper NTSC field mode morph, you would set the output resolution to 768 x 482, and generate 60 frames. You would then take those 60 frames and "feed" them to this operator, which would generate the correct fields, 60 of them, from the 60 input frames. These fields would then be 768 x 241, correct for NTSC (for most hardware.)
If the fields are reversed, remember, all you have to do is run the sequence again with the Field Dominance check in the other state. From now on, always run your conversions that way, and they should always be correct for your particular video encoding hardware.
§ 16.139.1 - Make Fields Controls
§ 126.96.36.199 - Trends
Operator dialog controls that have a Trend button next to them offer animation functionality. Trend allows you to set that variable over a set of frames. Each frame of the animation can be thought of as a slice of time. The trends allow you to alter some, all, or none of the variables for a particular time slice. Variables that have multiple states can be set to any of a number of values in the trend. Variables that are either on or off can only have an on or off value in the trend. You will notice that the trend graphs have equidistantly spaced vertical lines. Each of these lines represents a frame in the animation. The number of frames can be altered using Sequence controls... in the TimeLine pull down menu. Animation lengths of 100 - 999 frames will be represented with a vertical bar being 10 frames, and animation length greater than 1000 frames will have a vertical bar for every 100 frames. Click here to view more information on Trends.
§ 188.8.131.52 - Field Dominance Switch
If your field conversion is reversed for any reason, so that the fields are produced in the wrong order, change the state of the checkmark and re-generate.
§ 184.108.40.206 - Replace Image
You need this checked for TimeLine operation, so that the output of the operator in the TimeLine is the new image. You can leave it unchecked in one-at-a-time operation if you want to keep the original full-frame intact.
, Previous Page
. Next Page
WinImages F/x, Morph and all associated documentation
Copyright © 1992-2007 Black Belt Systems ALL RIGHTS RESERVED Under the Pan-American Conventions
WinImages F/x Manual Version 7, Revision 6, Level A
This manual was generated with wtfm
wtfm uses aa_macro and SqLite
aa_macro uses python 2.7