How to add your knowledge

What's New in Gateway Import Workflow

     

    Load Clip Versions into the Gateway Import Node in Batch

    You are now able to append versions to Gateway Import nodes when loading a new clip. You can then switch between versions using the "Versions" box. This allows you to create your own source clip versioning of multi-channel sources, from within the application. When loading a new multi-channel clip as a version of an existing Gateway Import clip, the application attempts to preserve all connections and identify all common channels between versions. All common channels will be replaced with the new version, while new channels are appended to the Gateway clip.

    To load a clip as a version:

    1. Select the Gateway Import node of the clip you want to version.
    2. Double-click the Gateway Import node.

      The Gateway Clip library appears.

    3. Optional: Create import rules and manage import preferences for the file to import.
      NoteGlobal Import options are disabled in a Gateway Import node: clips are always imported as unmanaged media, and include their alpha and other channels within the node.
    4. Optional: Set In and Out points using the Preview panel.
    5. Select the clip to import.
    6. From the Load drop down menu, select Load as Version.

      You are returned to Batch and the Gateway Import node is updated with the selected file. The previous clip is now available as a version from the Clip Versions box. You can have as many versions as you need.

    Not available in Smoke for Mac OS X.

     

    Save Import History as an Import Rule

    You can now create Import Rules from the Import History menu, allowing you to save the settings from an imported clip as an import rule.

    To create a rule from a previously imported clip:

    1. In the Clip Library, double-click an imported clip.

      The Import History menu opens.

    2. In the Rule Name field, enter the name of the new rule.
    3. Optional: Click the Clip History box to modify the import preferences, as needed.
    4. Click the Save dropdown list and select one of the following options.
      Select: To save the rule:
      Save in Project In the project directory. This rule becomes available to anyone who uses the current project and is identified with the PROJ prefix in the Active Rule box.
      Save with User With the user profile. This rule becomes only available to the current user and is identified with the USER prefix in the Active Rule box.

      The new rule is now available for future exports.

    TipTo apply the camera settings from one R3D file to a series of other files, do the following.
    1. In the Import Preferences for the R3D format, enable Colour > Save as User Settings. Enabling Save as User Settings tells the application that you will want to edit the colour settings at a later time; it also makes the same colour settings available to the Rules.
    2. Import the reference RED file.
    3. Open the Import History of the imported file by double-clicking it.
    4. Create a new rule from the Rules menu.

      The new rule, and the colour settings it contains, can now be used to apply the look of the original file to other R3D files.

    This tip also works with ARRIRAW files.

     

    Save and Load Batch Export's naming conventions

    You can now save and load Naming conventions created in the Batch Export node.

    Save and share with other users, or re-use in other export nodes or even other setups. Save time by not requiring the user to type in the entire path with every new setup.

    Not available in Smoke for Mac OS X.

     

    DPX Framerate control

    You are now able to override the frame rate found in the DPX header of a file, when using the Timecode From Header option. This is useful in cases where the DPX header contains a frame rate that is inaccurate.

    The framerate control is used commonly when the desired frame rate is 23.98, but the DPX header contains a frame rate of 24, and the timecode would be accurate for both frame rates.

     

    Frame or Pixel Aspect Ratio

    You can now use the Import Preferences for AVCHD, MXF, P2, QuickTime, and XDCAM to override the aspect ratio stored in the file header, for situations when this information is incorrect. In order to allow you flexibility in how this aspect ratio setting is overridden, different options are offered under the Aspect Ratio section of the Image menu.

    Aspect Ratio box
    Select the aspect ratio of the frames used to import the file and override the aspect ratio stored in the file as specified. You might need to change the aspect ratio as many applications erroneously write a pixel aspect ratio of 1 (a square pixel), even for formats that have non-square pixels (NTSC, PAL).

    Viewing the clip in the Player with the specified aspect ratio requires that you enable the Use Ratio toggle in the View menu. The Preview panel in the Clip Library always displays the clip with the selected aspect ratio. Also note that the application internally uses a frame ratio, not a pixel ratio. To specify a pixel ratio, you must select either Square Pixels or Enter Pixel Aspect Ratio; Aspect Ratio from Resolution and Aspect Ratio from Header are interpreted as frame ratios.

    Aspect Ratio field
    Set the ratio used to define the frame or pixel aspect. Affects the frame aspect if the Aspect Ratio box is set to Enter Frame Aspect Ratio. Affects the pixel aspect if it is set to Enter Pixel Aspect Ratio.
     

    Display the Absolute Frame in Gateway Import Node

    You can now read the file name and frame number for the current frame from the Gateway Import node in Batch. Use it to quickly identify the exact file you are looking at, as well as the absolute source frame of the clip.

    Frame field
    Displays the absolute frame number of the current frame, read from the file displayed in the File Name field. Use it to confirm offsets or identify specific frames.
    File Name field
    Displays the name of the file from where the current frame is being read. Use it to confirm the source of the displayed frames.

    Not available in Smoke for Mac OS X.

     

    Offset To Start Frame

    You can now offset one or many Gateway Import nodes in the Batch Timing view, based on their source frame number.

    For example, a clip with a start frame of 20, will have an offset of -20 applied so that the source frame number matches the Batch frame number. As this is based on frame number, this can be done using either the file naming or the information stored in the file header for source frame.

    Not available in Smoke for Mac OS X.

     

    Improved Gateway Messaging

    You can now more easily identify problems with the Gateway process by reading the extended error messages displayed in the application message bar, or the message log (Ctrl+Alt+F7).

     

    Restarting the Gateway

    You can now restart the local Gateway from within the application. Use the Restart button in the Network Panel.