Overview | Features | FAQ | Getting Started
Pipeline includes the following features:
- Easy installation and setup
- Edit existing jobs or create new jobs based on existing ones
- Generic rendering to render with virtually any command-line based renderer
- Priority sorting
- Group management
- Optional progress and completion email
- Publish the current status to an ftp server
- Cpu temperature and memory usage monitoring for all clients
- Remotely restart or shutdown clients
- Energy saving
- Send scripts to clients for software updates or other tasks
- Use of render projects for organizing and collecting render information
- Render statistics with information about machines, workload and more*
- Export of render statistics
- Checking for missing or incomplete frames in the output folder
- Editable resume frames after suspension or restart
- and much more…
Easy installation and setup ↑
Pipeline comes with an easy installation process without the need to install any additional software, frameworks or plugins. The setup only requires a few steps without any complex network setup and configuration. The documentation provides easy step-by-step instructions to get started instantly.
Edit existing jobs or create new jobs based on existing ones ↑
Pipeline allows you to easily modify existing jobs to re-render a file without having to open the render application or you can create an entirely new job based on an existing one.
Generic rendering to render with virtually any command-line based renderer ↑
Pipeline lets you define your own renderer description to support rendering with any command-line based renderer without the need to manually edit configuration files. Pipeline provides it’s own interface to configure the use of command-line options and progress handling. You can also customize the submission window to respect the functionality of the renderer.
Priority sorting ↑
Set the order in which jobs are executed by defining a job priority. This allows you to have urgent render jobs send to the render farm before others, even if they are created later.
Group management ↑
Pipeline lets you create render groups to pass certain jobs only to specific machines. Render groups are used if plugins are only installed on a limited number of machines or the render software is only available on some workstations.
Optional progress and completion email↑
Get informed about the status of your rendering by optionally setting up a notification email, which is either send whenever a job is complete or if a single task has been finished.
Publish the current status to an ftp server ↑
You can set up Pipeline to publish the current render status to a FTP server. This allows you to check your rendering from wherever you are with your smartphone or tablet.
Cpu temperature and memory usage monitoring for all clients ↑
All rendering clients can be monitored regarding their cpu temperature and their memory usage. This can help to allocate problems, as well as create and distribute render jobs based on performance requirements.
Remotely restart or shutdown clients ↑
All clients can be remotely restarted or shutdown in case they are not needed anymore or if a restart is required.
Energy saving ↑
Pipeline features energy saving options to reduce energy consumption and power costs. Idle machine can be automatically shut down after a defined time period to reduce the energy footprint of the render farm.
Send scripts to clients for software updates or other tasks ↑
Pipeline allows you to send custom shell scripts to selected clients to perform software updates, install plugins or clean cache files. Scripts can be send on a one-shot basis or even be stored as a script file which is automatically available from the scripts context menu the next time it’s needed.
Use of render projects for organizing and collecting render information ↑
Render projects can be used to better organize and identify render jobs. Render projects can be easily created through the submission windows or scripts. They are also used to gather render data of finished jobs to generate render statistics of processor usage and render time.
Render statistics with information about machines, workload and more ↑
Render statistics are helpful to calculate render costs and needed processor usage. The information is automatically collected if a render job is associated with a render project and contains all important information about the job and its tasks.
Export of render statistics ↑
Render statistics information can be exported either as an html or csv-text file. This is helpful when calculating render costs and needed processor usage.
Checking for missing or incomplete frames in the output folder ↑
After finishing a render job Pipeline can check the output folder for either missing or incomplete frames. You can also define which file-size to use for checking for corrupt files.
Editable resume frames after suspension or restart ↑
When terminating a render the currently rendering frame is stored as a resume frame to have the next available machine continue at this frame without having to re-render existing frame. The resume frame is editable and can be even used to render frames which are not defined in the original job.