Overscan in different 3D software

Real camera lenses have distortion, but virtual cameras in 3D software don’t, which leads to renders with straight lines.
To blend CG with real footage, you need to apply lens distortion. This can create empty edges on the render.


Overscan helps solve this by rendering with extra margin, ensuring that after distortion, the frame remains complete.
In this guide, we’ll show how to apply overscan in various 3D software tools.

Overscan through Nuke camera

Download the Nuke Overscan Script

Why do you need an overscan

Screenshot 1 shows a grid with lens distortion. You can see how straight lines are distorted at the edges.

Let’s assume that the CG object is at the edge of the frame (screenshot 2)

In order for a CG object to render correctly in the footage, you must apply distortion to it that corresponds to the lens.
In this case, after distortion is applied, the CG part will be stretched and “tiling” will occur.

To find out which overscan is needed, you can look at the bounding box settings in Nuke.
The dotted box shows how much the image extends beyond the edges.

You can also create a reformat node with these parameters:

It is important to note that overscan is not just an increase in render resolution.
It is an increase in the field of view of the camera + an increase in the resolution of the CG renderer.

Cinema 4D

To create an overscan in Cinema 4D there is a handy xpresso script that will create a new camera with overscan values.
To do this, add Canvassizecamera to your project and select the xpresso tag.

Next, in the camera parameter you need to create a link to your 3D camera.
After that specify old resolution and new resolution with overscan and then make the Canvassizecamera camera active.
Don’t forget to specify the new resolution in the project render settings.

As a result, the renderer will have an increased FoV.

Houdini

Mantra

To get overscan you need to go to the camera settings, View tab and then in the Resulution field specify how many percent overscan is needed.

ovesrcan 10%

Then specify a new value in the Screen Window Size field. In the case of the example it is 1.1

ovesrcan 10%

When rendering, select the desired camera with the applied modifications and do not change the resolution in the render settings.

Karma

To specify overscan parameters, go to the render settings, Image Output → Aspect Ratio tab. In the Data Window NDC field specify the required parameters.
For example, an overscan of 10% will have the following parameters: -0.1, -0.1, 1.1, 1.1

Note that the first two fields must have negative values.

Houdini Docs:

The default is 0, 0, 1, 1 (no cropping). Note that you can use negative values.
For example, -0.1, -0.1, 1.1, 1.1 will give you 10% overscan on each side.

Blender

In order to apply overscan in Blender it is necessary to install Addon.
The addon has been tested in program version 3.5.1.
Download Camera Overscan Script (Python)
Download Overscan Background Popover Script (Python)

Installation Instructions

Place both files in the following path:
Windows: C:\Users\{USER}\AppData\Roaming\Blender Foundation\Blender\3.5\scripts\addons
Linux: HOME/.config/blender/3.5/scripts/addons
macOS: /Users/$USER/Library/Application Support/Blender/3.5/scripts/addons

Then run the program, go into the settings and enable addons:

After that, an additional button will appear in the viewer, which will open the menu.

Overscan Percentage – specify the percentage of overscan;
Toggle Overscan – increases overscan by the specified percentage;
Restrore Original Settings – returns original parameters.

Maya

To set an overscan in Maya, regardless of the renderer, you need to go into the render settings:

Specify a new resolution with overscan. For example, if you need 10% overscan, then the new resolution for 1920×1080 will be 2112×1188.
Then, in Outliner, select the required camera and in the camera attributes, change the Camera Scale parameter by specifying the required FoV increase of the camera. For example, at 10% you should specify 1.1.

Conclusion

Now you understand the purpose of overscan and how to work with it in various 3D packages.
For convenience, you can use a ⚙️🔧 script for Nuke that automates the process of creating overscan and preparing nodes for its further use.

Guide to file naming

File naming in a project is a crucial aspect that helps maintain order and facilitates working with files at different stages of the project. File names should be standardized so that any artist in the team understands exactly what each file contains.

In this guide, we will explore the fundamental rules and recommendations for creating consistent file names, as well as discuss methods for organizing projects based on the practices of our studio.

Project organization

  1. First and foremost, create a folder named “Matchmove_machine” at the root of your drive. This will be our main working folder. It is important to place it directly in the root, not in a path like D:\Vasya\Work\matchmove or any other variations. For ease of interaction within the team and for transferring to the client, we use a standardized path for everyone.
  2. Next, when we start working on a new project, we create a folder with the project’s name. The name is taken from the work table where all the shots are listed, or from the Telegram group for that project; we use the full name as indicated.
  3. Next, within the project folder, create a folder with the name/number of the shot as listed in the table, FTP, or the topic in the Telegram group. After this, you can download the source material into this folder.
  4. While the download is in progress, create a folder named “_v001” within the project folder. This folder will be used to store all our exports from the first version of the project. The underscore is not mandatory, but it ensures that the export folder will always appear at the top of each shot.

Thus, the general path of a shot will be: Drive/Matchmove_machine/Project_Name/Shot_Number/ShotNumber_v001

File naming

After setting up the project structure, we begin our work.

During the work process, all files are saved in the “_v001” folder. Here are the main types of files you will encounter:

Undistort files

  1. shotnumber_undistort_v001/shotnumber_undistort_v001_####.jpg — For exporting the undistort sequence, create a folder where the sequence itself is saved. Do not forget to add the frame variable after the version (in most cases, this is _####, as sequences usually start from frame 1001).
  2. shotnumber_STMap_undistort_v001.exr — Export of the undistort as an STMap.
  3. shotnumber_STMap_distort_v001.exr — Export of the distort as an STMap.

Geometry naming

Geometry naming nuances:

  1. If, during the work process, any geometry is created and used that was not created within Nuke but loaded separately (obj or fbx) and exists in a single instance, then we use the naming: shotnumber_geo_v001.obj.
  2. If there are multiple files of such geometry, we use simple names, for example: shotnumber_floor_v001.obj, shotnumber_locators_v001.obj, shotnumber_door_v001.obj.
  3. If we have geometry provided by the client and we use it in our work, then the name remains unchanged (unless specified otherwise in the technical task).

Version numbering

Special attention should be paid to version numbering.

It is important to pay special attention to version numbering.

We never increment the version number on our own. Even if we create internal versions during our work or receive comments from the lead, the project version only changes when we receive comments from the client. Only then do we create a new version folder “_v002” within the project folder and save all the files under the second version.

There should not be a situation where the export folder with version 001 contains files with higher version numbers (shotnumber_track_v004_3_(2).3de).

To save intermediate versions, when you want to fix the result and try a different approach, you can create a “backup” folder within the version folder. This folder should be used to store various working versions. However, in such cases, it is important to be careful not to get confused, not to send this folder during the export to FTP, and not to send an incorrect version.

All of this is necessary to avoid confusion between the client’s and our versions during the work process. When we start working on a shot, the client expects the first version (v001) from us. If a situation arises where corrections or additions are needed, then the second version (v002) is expected from us, and so on. This ensures clear naming and understanding from all sides.

Uploading the result

Before uploading the result, we check how our folder with files looks. We ensure that if the working version is 001, then all files have this version. We look for typos in the names.

The export requirements are usually specified and pinned in the project’s work chat and may vary. We carefully read the chat and ensure that we have all the files and there are no extras. The export location is also specified and pinned in the project’s work chat.

Note: If a situation arises where corrections are needed and a new version is created, then we upload all files with the v002 suffix. Even if these files have not been changed. It should not be the case that, for example, the scene is the second version, but the geometry and undistort are the first. This can lead to questions about whether the correct files have been uploaded and whether the required changes have been made. Explanations like “take the scene from the third version, the geometry of the second, and the undistort from the first” look confusing to everyone.

Therefore, we eliminate these questions by uploading everything in the new version.

It is important to check yourself every time before and after uploading the result, regardless of how confident you are and how automatic the process is. Mistakes, typos, and oversights can happen to anyone, so it is not difficult to double-check the number of uploaded and required files, check the names, and check the version.

  • Project file 3DE4 (.3de)
  • Lens file from Nuke (.nk)
  • Scene script file in Nuke (.nk)
  • Scene export file in Alembic (.abc)
  • Scene export file in FBX (.fbx)
  • Geometry file from 3DE4 (.obj)
  • Result preview file (.mov)
  • Folder with undistort sequence in (.jpg)
  • STMap undistort file in (.exr)
  • STMap distort file in (.exr)

How To Shoot Distortion Grids

Welcome to our comprehensive step-by-step guide on how to shoot distortion grids! In this video, we will walk you through the entire process, ensuring you capture precise and accurate distortion grids for your projects.

Discover the essential techniques and tips for setting up your shots, avoiding common pitfalls, and achieving optimal results. We’ll highlight the most frequent mistakes made during the shooting process and provide valuable insights on how to correct them.

Additionally, you can find links to useful materials and resources in the description below, which will further aid you in mastering the art of shooting distortion grids.

Watch the video to enhance your skills and ensure your distortion grid captures are flawless every time!

Guide

Explore our complete Distortion Grid shooting guide with detailed instructions for different cameras and lenses, including proper file naming schemes according to industry standards. Based on experience from major VFX studios.

Multi-Camera Geometry Tracking

Welcome to an in-depth exploration of Multi-Camera Geometry Tracking Technology! In this video, we’ll unlock the mysteries behind this cutting-edge innovation and its incredible applications.

Dive into the world of 3D tracking, where multiple cameras work in unison to accurately track and locate objects within a scene. This advanced technique revolutionizes the way we capture and analyze motion, providing unparalleled precision and flexibility. Whether you’re working in film, television, or any field requiring precise motion tracking, this technology offers powerful solutions to complex challenges.

Join us as we explore the principles behind multi-camera geometry tracking, demonstrate its practical applications, and showcase its potential to transform your projects. From setting up the cameras to analyzing the data, we’ll guide you through every step of the process.

Watch the video to discover how multi-camera geometry tracking can elevate your work to new heights!

Extract Focal Length

In this article, we’ll explore the “Extract Focal Length” script, which allows you to copy the focal length curve from EXR metadata directly into the Curve Editor. Additionally, if the focal length remains constant and a curve is unnecessary, you can extract the value from the EXR and write it directly to the lens connected to the camera.

Script Origin and Improvements

Our script is a fork of an existing script by Uwe Sassenberg. However, we found that it did not always function correctly. To improve its reliability and functionality, we made several fixes and added new features, including the ability to transfer focal distance to the camera lens and subsequently convert it to focus distance.

How to Use the Script

  1. Focal Length Curve Extraction

The script copies the focal length curve from the EXR metadata and writes it into the Curve Editor.
If the focal length does not change, you can extract it directly from the EXR and write it to the lens without needing a curve.

  1. Specifying the Focal Length Attribute

The script attempts to automatically detect the focal length attribute. If it is not detected or is incorrect, you need to manually specify the focal length attribute.

How to install the script

To install the script, follow the instructions provided in the “Installation.txt” file included in the downloadable archive.
The installation process is straightforward, ensuring that you can quickly integrate the script into your workflow and start using it immediately

Practical Tips

  • Automatic vs. Manual Detection: Always verify the automatically detected focal length attribute to ensure accuracy. If needed, manually enter the correct attribute.
  • Consistent Focal Length: For static focal lengths, writing the value directly to the lens simplifies the process and avoids unnecessary curve creation.

Conclusion

The “Extract Focal Length” script is a versatile tool for managing focal length data within 3DEqualizer. By improving upon the original script and adding new functionalities, we provide a reliable solution for both dynamic and static focal length scenarios.

OpenEXR Metadata Reader

In this article, we will discuss the “OpenEXR Metadata Reader” script, designed to allow users to view the metadata of EXR files directly within 3DEqualizer. While 3DEqualizer’s Script Database includes a similar script, our custom version offers enhanced reliability and functionality.

Why Create a Custom Script?

Although the existing script in 3DEqualizer’s Script Database serves a similar purpose, it presented several issues during testing with different footages. We encountered errors and found some functionalities to be inconvenient. Therefore, we developed our own version to address these shortcomings and provide a more seamless user experience.

Interface and Functionality

The interface of our script mirrors the metadata tab of Nuke, ensuring a familiar and intuitive user experience.

Key features include:

  • Automatic Data Update: When you change a frame, the metadata updates automatically. There’s no need to restart the script, allowing you to check for changes in parameters such as focal length or focus distance on the fly.
  • Search Functionality: The script includes a search feature, with a drop-down list to specify the search scope. This makes it easy to find specific metadata attributes quickly

How to Access the Script

You can find the script under the Options tab in 3DEqualizer. For easier access, you can also add it as a panel via the Config tab.

How to Install the Script

To install the script, follow the instructions provided in the “Installation.txt” file included in the downloadable archive.
The installation process is straightforward, ensuring that you can quickly integrate the script into your workflow and start using it immediately.

Practical Applications

The “OpenEXR Metadata Reader” script is a powerful tool for VFX artists and post-production professionals. By providing real-time access to metadata within 3DEqualizer, it streamlines the workflow and enhances the efficiency of tasks such as camera tracking and matchmoving.

Conclusion

Our custom “OpenEXR Metadata Reader” script offers a reliable and user-friendly solution for viewing EXR metadata in 3DEqualizer. By addressing the limitations of existing scripts and enhancing functionality, we aim to provide a tool that meets the practical needs of professionals in the field.

Favorite’s Project

In this article, we will discuss the script, a handy tool that allows you to save projects to a list for quick access later. This feature functions similarly to the “Recent Projects” list found in other software, but with additional flexibility tailored for 3DE4 users.

Purpose and Concept

The inspiration for this script came from the need to make frequent edits to various projects stored in different folders. By saving these projects to a list, you can easily access and manage them without navigating through multiple directories.

Script Features

The script is accessible under 3DE4 → Favorite’s Project and offers three main options:

  1. Open the Main Window

This option opens the primary interface of the script, where you can manage your saved projects.

  1. Add Current Project to Saved List

This option adds the currently open project to your saved list for quick access in the future

  1. Open Last Project from the List

This option opens the most recently added project from the list, not the last project you worked on. This is particularly useful when you know the project you want to open and need to access it immediately

Script interface

The main window of the script is divided into several sections for ease of use.

The list displays all projects saved to the “database.” Each entry includes the project name and any associated comments.

List Management

This section allows you to work with the list.

  • Search for Projects: Find the necessary project by name or comment.
  • Open Selected Project: Opens the selected project with a buffer by default (you can disable this if needed).
  • Delete Selected Project: Removes the project from the list without deleting it from the hard disk.

Save Current Project

In this section, you can save the currently open project to the list. You can also add a comment, which will be saved to both the Project Notes and the list.

How to install the script

To install the script, follow the instructions provided in the “Installation.txt” file included in the downloadable archive.
The installation process is straightforward, ensuring that you can quickly integrate the script into your workflow and start using it immediately.

Practical Use

The “Favorite’s Project” script enhances your workflow by providing quick access to frequently used projects. This can significantly reduce the time spent searching for and opening files, allowing you to focus more on your work.

Conclusion

By utilizing the “Favorite’s Project” script, you can streamline your project management in 3DE4, making your editing process more efficient and organized. Whether you’re handling multiple projects simultaneously or revisiting old ones, this tool is an invaluable addition to your toolkit

Extract Focus Distance

In this article, we’ll explore how to extract the focus distance curve from EXR metadata and transfer it directly into the 3DE4 Curve Editor. This process is crucial for accurate camera tracking and matchmoving, ensuring that the focus distance matches the original footage.

Step-by-Step Guide

  1. Adding the EXR Section to the Camera

Begin by adding the EXR section to your camera in 3DE4. This section contains the metadata that we’ll use to extract the focus distance.

  1. Opening the Curve Editor

Navigate to the Curve Editor:

  • Go to Edit
  • Select Extract Focus Distance from OpenEXR Metadata

A new window will open, prompting you to enter the attribute that contains the focus distance.

  1. Finding the Focus Distance Attribute

The script will attempt to automatically locate the focus distance attribute, typically named “focus” or something similar. However, metadata naming can vary, especially with new material. It’s important to verify the correct attribute name.

  • Use Nuke or any other software to inspect the metadata and confirm the attribute name
  • If the script fails to find the correct attribute or identifies it incorrectly, manually enter the attribute
  1. Checking Units of Measurement

Ensure that you verify the units in which the focus distance is specified. By default, this is usually in meters, but it’s always good practice to double-check.

  1. Applying the Focus Distance Curve

After entering the correct attribute and confirming the units:

  • Press OK.
  • The existing focus distance curve (if any) will be deleted.
  • The new curve, extracted from the EXR metadata, will be written into the Curve Editor.

To ensure everything is accurate, check a few frames manually. Compare the focus distance values against the metadata to confirm the extraction process was successful.

How to install the script

To install the script, follow the instructions provided in the “Installation.txt” file included in the downloadable archive.
The installation process is straightforward, ensuring that you can quickly integrate the script into your workflow and start using it immediately.

Tips and Troubleshooting

  • Inconsistent Metadata: If you encounter inconsistencies in metadata naming conventions, maintain a reference list of common attributes used in your projects.
  • Unit Conversion: Be mindful of the units specified in the metadata. Conversion errors can lead to incorrect focus distances.
  • Regular Checks: Periodically check frames during the extraction process to catch any errors early on.

By following these steps, you can efficiently extract and apply focus distance curves from EXR metadata, enhancing the precision of your camera tracking and matchmoving projects.

Camera Database

In visual effects and post-production, accurate camera data is crucial for ensuring realistic and precise results. The “Camera Database” script for 3DEqualizer simplifies the process of finding and utilizing camera sensor data, with the added benefit of allowing updates to keep the database current. We also launched our own database, please check it out: camdb.matchmovemachine.com

Basic Functionality

The script offers several key features to streamline your workflow.

Immediate Access to Camera Sensor Data

The script allows you to quickly find camera sensor data directly within 3DEqualizer, eliminating the need to search for information manually.

Data Source

The basic data is parsed from the vfxcamdb, providing a reliable source of camera specifications.

User-Friendly Interface

  • Camera Selection: Select the desired camera from a comprehensive list, with the added convenience of a search function to quickly locate specific models.
  • Metadata Retrieval: For supported cameras, you can try to get the camera model data from metadata (currently in beta-testing stage), making the process even more efficient.

Detailed Usage Instructions

Open Sensor Data Window

After selecting your camera, a new window will open displaying the sensor size.

Specify Sensor Dimensions

Choose the required sensor dimension (height or length) and input the value.
Ensure that the pixel aspect ratio is correctly set beforehand to achieve accurate calculations for the Passive parameter

Database Updates

The script supports database updates, so we propose to update it with new camera models, including phone cameras.
To help build the most comprehensive VFX Camera Database, you can send verified data to our email solveme@matchmovemachine.com.
We will review and add the new entries, continually improving the database for the VFX community

How to install the script

To install the script, follow the instructions provided in the “Installation.txt” file included in the downloadable archive.
The installation process is straightforward, ensuring that you can quickly integrate the script into your workflow and start using it immediately.

Conclusion

The “Camera Database” script is an invaluable tool for VFX professionals, providing immediate access to essential camera sensor data and ensuring accurate matchmoving and compositing results. By supporting easy updates and encouraging community contributions, this script ensures that the database remains current and comprehensive.

Feel free to explore the script’s features and contribute to the database. And don’t forget to check out our new database at camdb.matchmovemachine.com
If you have any questions or need further assistance, don’t hesitate to reach out. Together, we can create the coolest and most complete VFX Cam DB!

Change Setting for Points

Efficient point tracking is essential for accurate matchmoving and compositing in visual effects workflows. The “Change Setting for Points” script enhances your control over 2D points by allowing you to change the tracking direction and toggle the calculation status of points. This script simplifies these processes, providing a more intuitive and streamlined user experience.

How the script works

The script is accessible directly from the viewer.

It offers two primary functionalities:

  1. Change Calculation
    • Function: When clicked, this option toggles the calculation status of the selected point(s).
    • Usage: Easily enable or disable points for calculation to refine your tracking process and focus on specific areas of your project.
  2. Change Direction
    • Function: This option changes the tracking direction of the selected point(s) to the opposite direction.
    • Usage: Clicking this will switch the tracking direction from forward to backward or vice versa, without affecting the Forward & Backward mode. This feature is particularly useful for correcting tracking paths or adjusting points as needed.

Shortcut customization

To enhance workflow efficiency, you can assign shortcuts to these scripts.
Setting up shortcuts allows you to quickly toggle calculation statuses and change tracking directions with minimal interruption to your workflow.

How to install the script

To install the script, follow the instructions provided in the “Installation.txt” file included in the downloadable archive.
The installation process is straightforward, ensuring that you can quickly integrate the script into your workflow and start using it immediately.

Conclusion

The “Change Setting for Points” script is a powerful tool for VFX professionals, providing greater control and flexibility in point tracking.
By enabling easy toggling of calculation statuses and directional changes, this script ensures that you can optimize your tracking processes efficiently.

Feel free to experiment with these features and customize shortcuts to suit your workflow.
If you have any questions or need further assistance, don’t hesitate to reach out. Have a good solve!