Rendering Modes
Table of contents
Introduction to Rendering Modes
In Brender Studio, there are three main modes for rendering with Blender:
- Frame: Frame mode is used for rendering single frames.
- Animation: Animation mode is used for rendering animations.
- Python: Python mode is used for rendering with Python scripts.
Each of these modes is designed to cater to different needs and facilitate the rendering process according to the specific use case.
How to Choose a Rendering Mode
Navigate to CPU Rendering/GPU Rendering > Click on the tab for the desired rendering mode.
Frame Mode
The Frame mode is designed to render a single frame of a Blender scene. It is ideal for obtaining a high-quality static image of your project.
Settings and Features
- Allows adjustment of rendering parameters such as resolution, quality, and output options.
- Possibility to modify the scene configuration before starting the rendering.
Animation Mode
The Animation mode is oriented towards rendering a range of frames, resulting in a final video. It is perfect for creating complete animations from multiple frames.
Settings and Features
- Allows adjustment of rendering parameters just like in Frame mode.
- Setting a specific range of frames to render.
- Automatic generation of a final video and a preview by joining the rendered frames.
Pyhton Mode
The Python mode allows users to run custom Python scripts within Blender using the bpy API. This offers great flexibility for advanced tasks and automation.
Settings and Features
- Uploading Python scripts to be executed within Blender.
- Access to the AWS boto3 module, allowing interaction with services like S3 and SES.
- Customizable environment variables to adapt scripts to different scenarios.
Example Scripts Repository
Brender Studio provides a repository of example scripts that you can use to get started with Python mode. You can access the repository on GitHub
Uploading Python Scripts
There are two ways to upload Python scripts:
- Upload Single File: Upload a Python file from your local machine or use example scripts.
- Upload Folder: Upload a folder containing multiple Python files and resources. You must include an entry point file that will be executed.
AWS Boto3 Module
The Python mode provides access to the AWS boto3 module, allowing you to interact with services like S3 and SES. This enables you to automate tasks and integrate Blender with AWS services.
To use the AWS boto3 module, you can import it in your Python script and use it to interact with AWS services.
Boto3 Documentation
For more information on the AWS boto3 module, you can refer to the Boto3 documentation.
Customizable Environment Variables
The Python mode allows you to define customizable environment variables to adapt your scripts to different scenarios. These variables can be used to configure the behavior of your scripts and make them more flexible.
To define environment variables, you can use the environment variables editor in the Python mode. You can add, edit, and remove variables to customize the behavior of your scripts.
Predefined Environment Variables
| Key | Description | Env Type |
|---|---|---|
| JOB_ACTION_TYPE | Defines the job action type. Brender Studio Docker image uses this variable to determine the action type of the job. | Brender-Studio |
| EFS_MAIN_SCRIPT_PATH | Path to the main script in EFS. | Brender-Studio |
| EFS_BLENDER_FILE_PATH | Path to the .blend file in EFS. | Brender-Studio |
| EFS_BLENDER_OUTPUT_FOLDER_PATH | Path to the output folder in EFS. Useful for saving the rendered images using Brender Studio logic. All contents of this folder are uploaded to S3 after the job is completed. | Brender-Studio |
| BLENDER_EXECUTABLE | Path to the Blender executable. | Brender-Studio |
| USE_EEVEE | Determines if the Eevee render engine is used. Docker image activates a virtual display for Eevee rendering (xvfb). | Brender-Studio |
| USE_GPU | Determines if GPU is used for rendering. No logic is implemented in the Docker image to use the GPU. Users can use this variable to implement their own logic. | Brender-Studio |
| BUCKET_NAME | Name of the S3 bucket. | Brender-Studio |
| BUCKET_KEY | Project key in S3. It is the project name provided by the user in the form. | Brender-Studio |
| AWS_BATCH_JOB_ARRAY_INDEX | Index of the job in the AWS Batch job array. Useful for identifying the job in the array. | AWS Batch |
| AWS_BATCH_JOB_ARRAY_SIZE | Size of the job array in AWS Batch. Useful for identifying the size of the job array. | AWS Batch |
| AWS_BATCH_JOB_ID | ID of the AWS Batch job. | AWS Batch |
| AWS_BATCH_JOB_ATTEMPT | Attempt number of the AWS Batch job. | AWS Batch |
| AWS_BATCH_CE_NAME | Compute environment name of the AWS Batch job. | AWS Batch |
| AWS_BATCH_JQ_NAME | Job queue name of the AWS Batch job. | AWS Batch |