HOUDINI - Chunking method (processing batches of frames during single task session on the given node instead of rendering only 1 frame per task/node)

HOUDINI - Chunking method (processing batches of frames during single task session on the given node instead of rendering only 1 frame per task/node)

Method 1

The previous method for chunking renders in Houdini is a little node intensive, but can garner some rather substantial savings of both time and credits if implemented on the right scene.   The best effect for this method will be found on shots that are extremely fast to render, sub 1 minute or less.
  1. Create reference copies of your ROP node for each chunk range you want to do, it is best to keep this number to the number of machines you want to engage.
    1. 5 for Economy, 40 for Standard, 100 for Rush
  2. Unlink all of the Valid Frame Range and the Start/End/Inc parameters on the ROP nodes.
  3. Set the Valid Frame Range parameter to Render Frame Range Only (Strict) on all of the ROP nodes.
  4. Set the Start/End/Inc to ranges which butt up against each other so there are no unwanted gaps.
  5. Wire each ROP into a Batch node.
  6. Wire all of the batch nodes into a Render Submit node.

Method 2

With the release of PDG/TOPs support for the GridMarkets cloud, easier methods for chunking have become available.
  1. Inside a TOPs network, add a ROP Fetch TOP.
  2. Target the ROP from which you wish to render/cache.
  3. Right click on the ROP Fetch TOP and select "Generate Static Work Items".
  4. Inside the ROP network, place a GridMarkets PDG ROP.
  5. Target the ROP Fetch TOP with the TOP Path parameter.
  6. Set the Service Level parameter to the level which you wish to use for your submission.
  7. Match the Submission Type parameter to the type of ROP which is being rendered/cached.
  8. Wire the GridMarkets PDG ROP into a Render Submit node and continue submission as usual.
    1. Note: The rendering ROP is not wired into the Render Submit network chain with this method, the GridMarkets PDG node takes its place.

    • Related Articles

    • HOUDINI + REDSHIFT - Render optimizations

      Summary This article explains the process of pre-converting textures to help decrease render times when rendering with Redshift. The following topics are covered: Pre-Convert Textures - References for converting textures locally. Upload Pre-Converted ...
    • HOUDINI + REDSHIFT - OCIO (using color profiles built into Redshift 3.0.46+)

      For using the OCIO color profiles in Houdini scenes using Redshift 3.0.46+ we recommend utilizing the profiles that ship with Redshift itself. Please follow the instructions below (but before sending the scene to the farm please ensure the frame is ...
    • HOUDINI - Solaris - flattening the USD assets by exporting all layers to a single USD

      How to flatten the USDs by exporting all layers to a single USD. 1 - Load the given USD in the Sublayer node or Asset Reference node. When using Asset Reference node please make sure to load USD file as an Assmebly (Primitive Kind = Assembly). 2 - ...
    • HOUDINI - Clearing Manifest (reverting HDA to defaults)

      Please note that if you prevent the given assets from being uploaded in the plugin by unchecking the Upload box it will get saved in the scene and those won't be marked for upload for future submissions for the given scene. There are also other ...
    • HOUDINI - budgeting / credit cap per job

      You can set the price limit expressed in credits that the given job can consume before 1 of 3 actions are taken. Go to Jobs tab of your Houdini submission plugin and edit the Credits Budget field by double clicking it, set the desired value: Finally ...