baitstudio/tk-multi-renderfarm — pull request #6 by maxpersson (2014-01-17 16:49:51+00:00)
Title: Add five optional commonly used templates for rendering

This is a crucial part of functionality for us, and I wish there was a way to make the templates fully optional in the outputs. Different outputs need different templates...

I totally understand if you don't want to merge this, I would love to have a cleaner solution. Currently we use a couple of templates for log files, scene export and rendering:
```
maya_shot_render_job: '@shot_root/work/otis/{pipe_step}[_{name}]/v{version}/{Shot}_{pipe_step}[_{name}]_v{version}.otis'
maya_shot_render_scene: '@shot_root/work/otis/{pipe_step}[_{name}]/v{version}/{Shot}_{pipe_step}[_{name}]_v{version}.mb'
maya_shot_render_export: '@shot_root/work/otis/{pipe_step}[_{name}]/v{version}/{Shot}_{pipe_step}[_{name}]_{layer}_v{version}'
maya_shot_render: '@shot_root/work/images/{pipe_step}[_{name}]/v{version}/{width}x{height}/{Shot}_{pipe_step}[_{name}]_{layer}_v{version}[_{aov}].{SEQ}.exr'
maya_shot_render_pub: '@shot_root/publish/elements/{pipe_step}[_{name}]/v{version}/{width}x{height}/{Shot}_{pipe_step}[_{name}]_{layer}_v{version}[_{aov}].{SEQ}.exr'
```

I wanted you to see this part of our solution, and maybe we can come up with a more flexible solution with optional templates. What do you think?