Overview | Features | FAQ | Getting Started

futuristic f1 stock footage by brave rabbit

2.0 Service Pack 1

 

  • note: In order to update to Pipeline 2.0 Service Pack 1 only the manager application needs to be updated from the previous installation. Also, the After Effects scripts should be replaced if the CreativeCloud version of After Effects is used.
  • update Updated the After Effects scripts to work with the CreativeCloud version of After Effects (After Effects CC).
  • bugfix Setting a custom frame range in the After Effects submission script doesn’t produce corrupted job files anymore.
  • bugfix Fixed an issue that kept email notifications from being sent properly.
  • bugfix Updated the default environment path for Nuke to allow better compatibility with installed gizmos. It now points to the default user’s nuke directory.
  • changes When looking for updates Pipeline now also checks for service pack updates and not major updates alone.

2.0

 

  • new Generic Rendering: Pipeline now supports virtually any command line based renderer. (still, there might be certain renderer specifics that are not covered yet)
  • new Generic rendering is based on a renderer description for each renderer that defines how a command line is constructed, how to read the frame progress and which errors to look out for.
  • new Renderer descriptions can be easily created and modified through the interface.
  • new All renderer descriptions are stored in ‘Application Support/Pipeline/rendererDescriptions’.
  • new Sample descriptions are provided and can be found in the Pipeline Manager application bundle.
  • new All generic renderer job submissions are processed through a unified window. The renderer to use can be selected from here.
  • new Most elements of the submission window are customisable through the renderer description.
  • new The render option element can be used to create presets, which help to set a specific combination of render arguments at once.
  • new Rendering with REDLine allows to refer to presets from REDCINE-X PRO.
  • changes The new version of Pipeline Client is not compatible with previous versions of Pipeline Manager. Manager and Clients must be the same versions. Machines running older versions of Pipeline Client will be ignored by the manager.
  • changes Jobs originating from previous versions of Pipeline are not supported.
  • new The application bundles feature a new folder structure to account for new configuration files and renderer descriptions.
  • new Each client now also transmits it’s version number for checking which version of Pipeline is running on each client.
  • changes Frames are now only shown as integers. All possible subframes will be discarded.
  • new Version numbers for all internally supported renderers can be easily updated from the interface. This reduces the need to update Pipeline when a new version of the rendering software is released. The version is dynamically read in the submission window for each renderer.
  • changes Better storage for user information and passwords.
  • update All parts of Pipeline have been subject to code improvements.
  • changes Project and group management has been moved to the preferences for cleaner integration.
  • changes The files for the renderer specific environment variables have been moved to the environments folder in the application bundle.
  • new Custom shell scripts can now be send to the clients. Scripts are either entered through a simple interface and send directly to the clients or can be saved and made available through the Client list context menu. All saved scripts are plain text files containing regular shell commands and are stored in ‘Application Support/Pipeline/scripts’. Scripts can only be executed when clients are idle or inactive.
  • new The client application can be remotely updated from the manager UI.
  • update The job list now features customisable columns with it’s own context menu.
  • update The job list shows two new columns with information about the frame range of each job and the number of contained tasks for a better overview. This way no additional steps are necessary to collect information regarding the range or task count.
  • changes When adding new project names they will be added to the top of the list and not at the bottom as in previous versions.
  • new The project list can be ordered alphabetically or in reverse.
  • new In order to save energy, clients which are idle can be set to shutdown or sleep after a defined period of time. The setting can be found in the preferences.
  • new The current rendering status can be send to an FTP server to be viewed from anywhere. The transmitted status contains the same information as the eMail notification but without the need to send an email in certain intervals.
  • changes The new version of Pipeline Client is not compatible with previous versions of Pipeline Manager.
  • changes The log window, which displays the output of the renderer, is now included in the client main window as a tab.
  • new Memory usage is now transmitted as a status information. The type of memory display can be set in the preferences. Only one type of memory usage can be displayed and transmitted to the manager at a time. The user can select between eight types of memory and combinations.
  • new The type of memory to display can be set either locally for each client or globally through the manager.
  • new The client can now be setup to also show in the menu bar. All important functions can be accessed from here. It only shows information whenever present. In all other cases the status will be shown (i.e. frames won’t be shown when idle, but temperature or cpu usage will be displayed).
  • new The client can be set to appear hidden when the application is not in the foreground. The setting can be found in the preferences.
  • new The client can be run as an agent only. This removes the application from the dock as an icon, as well as from the application switcher. The client is then only accessible through the menu bar. Note, that even when the client is running as the foreground window the menu bar will not be shown. This mode can be activated from the preferences. The application needs to be restarted for the changes to take effect.
  • changes The group setting to ignore any new tasks has been renamed to ‘Ignore’
  • new In order to cover the temperature readout of any computer a sensor code list can be edited to account for new macs. The property list can be found in the application bundle of the client.
  • changes If a temperature compatible mac is not listed the reading of the temperature is turned off and disabled.
  • new The interface of the client application features a new console view where message are printed when the client receives tasks or commands from the manager. This can be best used for testing command lines when working with generic rendering.
  • new When booting a client and automatically connecting to the manager made the client receive more than one task at a time leading to a range of errors. Each client now has to remain inactive for a certain waiting time before being allowed to receive any tasks. The time value can be set in the preferences and depends on how long the machine needs to be ready to render after booting.
  • bugfix Setting more than one client to inactive at a time doesn’t produce the same resume frame for all assigned tasks anymore.
  • bugfix Removed an error when trying to submit a shake job from the manager submitter with a manually typed in script name.
  • changes All items of the context menu for the client list are now disabled if nothing is selected.
  • bugfix Fixed a wrong application path for VRay in the maya submitter for maya versions 2013 and up.
  • bugfix The Nuke submission script reported an error with a non-readable environment file even if the file was not given.
  • bugfix Creating a new After Effects job from an existing didn’t read the multiprocessing flag and render group correctly.
  • bugfix After Effects Script: The output path padding now works correctly if the user changes the padding separator (default separator is the underscore).
  • bugfix After Effects: It’s now possible to create a render job even if the composition shares the same name as the enclosing folder.
  • update Maya: If a scene contains more than one render camera the submitter will set the appropriate camera flag automatically as a custom argument and add the camera name to the name of the job. When rendering with Maya or MentalRay the output path has to be adjusted manually.
  • new After Effects: A new Script UI Panel is included to open the submission window without having to use the menu.

f1 stock footage by brave rabbit

1.4

 

  • changes Changes to the licensing model.

1.3.1

  • new feature It is now possible to define custom environment variables when submitting a job with Maya, VRay and Nuke. The environment is defined in a text file and evaluated during job submission.
  • bugfix Fixed the remaining days counter for expiring licenses.
  • bugfix Removed duplicate render arguments when rendering with After Effects.
  • bugfix After Effects projects paths with spaces are now handled correctly.
  • bugfix Maya submission script: Fixed the reload button.
  • bugfix Maya submission script: Tile rendering is not enabled by default.
  • bugfix Removed the limit of 20 entries when submitting jobs with new project names.
  • bugfix Fixed a bug in the job submission window for Maya where the scene path was not correctly displayed under certain conditions.
  • bugfix Fixed a output path related bug when creating a job for Nuke in Pipeline Manager.
  • bugfix Updated the Nuke submission script to be compliant with a toolbar integration within Nuke.
  • bugfix Cinema 4D submission script: Removed a problem with correctly reading existing render projects.

1.3

  • new feature Added a tile rendering feature for Maya Software, MentalRay, VRay and VRay standalone available through the Maya submission script. This feature is not available when creating a job in the manager application.
  • new feature When using tile rendering the render output can be collected to a common folder through the preferences.
  • new feature After Effects Submission Script: During job submission the script can optionally check any used project fonts and collect them in a font folder. This only applies to the submission script but not the job creation in the manager application.
  • bugfix After Effects Submission Script: Fixed a script incompatibility with CS5.5 (fixed in 1.2.1).
  • bugfix After Effects Submission Script: Having more than one renderqueue item doesn’t produce an error anymore.
  • bugfix After Effects Submission Script: Fixed a task size bug with compositions exceeding 1000 frames.
  • bugfix Fixed an issue where checking output sequences would produce an error if a folder is present with the same name as the image sequence.
  • bugfix Setting a new task timeout for a currently rendering task to 0 minutes is now correctly applied in the client.
  • bugfix Setting a new task timeout for multiple currently rendering tasks is now correctly transmitted to the participating clients. Previously only one client would be informed of the change.
  • bugfix Elimited another possibility that a client would receive more than one job from time to time.
  • bugfix Fixed a general submission bug with timelines starting at frame 0.
  • bugfix Removed the ability to enter a new timeout with a negative number.
  • update All submission scripts now check upon startup if the pool folder is valid.
  • update Maya Submission Script: The masterLayer is now substituted with the target render layer in the output path for checking image sequences.
  • update Remodeled UI for the After Effects Submission Script.
  • update After Effects Submission Script: Included a check for inactive render queue items (updated in 1.2.2).
  • update After Effects Submission Script: Included a check for making sure that the project is saved before submission (updated in 1.2.2).
  • update After Effects Submission: Included the multiprocessing option of After Effects.
  • update Added additional possible error messages to Maya and VRay rendering.
  • update Updated the VRay render application string that changed with VRay version 2.2.
  • changes Removed the need to disable the Auto Connect in the client when manually connecting to the manager.
  • changes Better behavior of the edit resume frame window.
  • changes Added a reminder and counter for expiring licenses. Counting starts from 10 days down.
  • changes Updated the documentation and completed the network information topic

1.2

  • new feature Maxon Cinema 4D rendering is now supported.
  • bugfix Fixed various bugs that concerned selecting paths through open and save panels due to changes in OS X 10.7.
  • bugfix Re-enabled the Archive Job and Delete Job menu items in the job list right-click menu.
  • update Finally added an After Effects CS 5.5 option.
  • update Added additional possible error messages to Maya and VRay rendering.
  • changes Changed the authorization procedure. The registration information is now copied to the clipboard to paste into a new mail. Opening a direct email link defaults to a new email in Apple Mail which might not be configured for all users.
  • changes removed the version number from the window title to clean up the interface.
  • changes Added email feedback and website link to the help menu.

1.1

  • new feature Clients can now be remotely shutdown or restarted from the client list right click menu. Clients can be set to ignore the shutdown command via the preferences.
  • new feature Timeouts can now be set after job submission for either an entire job or for individual tasks that are already queued. Individual task timeouts will only be preserved as long as Pipeline Manager is running.
  • new feature The task timeout is displayed through a new column in the task list.
  • new feature Tasks can be individually deleted from the render statistics.
  • new feature Rendertime and workload can be individually calculated for the selected projects or tasks.
  • new feature Clients now also transmit the current cpu temperature.
  • changes Cleaned up the interface and extended the right-click menus.

1.0

  • changes Removed the limit of 20 projects for job assignments. The project number is now infinite.
  • changes The restore task list now automatically removes unused entries from old or obsolete tasks during startup and displays only the number of restored tasks in the message history.
  • new feature Added a project column to the job table.
  • bugfix Fixed that the resume frame of finished tasks is also saved in the restore task list.
  • bugfix The stored task backup is now correctly updated when manually clearing any resume frame of a task.
  • bugfix When a task error occurs the resume frame is not set to 0 anymore.
  • bugfix When the estimated render time has reached 00:00:00 the time now stalls and doesn’t show negative numbers with hours, minutes and seconds.