Perfect!
Thanks Greg
|-----Original Message-----
|From: Greg Ercolano [mailto:erco@(email surpressed)]
|Sent: Wednesday, 8 February 2006 2:12 PM
|To: void@(email surpressed)
|Subject: Re: Start-middle-end frame rendering.
|
|[posted to rush.general]
|
|Dylan Penhale wrote:
|> We are just about to look into modifying our 3D submit scripts to
|> render the first-middle-last frames first then fill in the gaps, but
|> before we do I thought I would ask if there is already a way to do
|> this? I can't see any reason why this couldn't be a default
|behaviour,
|> but an option to toggle it would probably be best.
|
| If the frame range is 1-100, then you could submit the
|start/middle/end
| by specifying the following at the 'Frames:' prompt:
|
|Frames: 1 50 100 2-49 51-99
|Batching: 1
|
| (note spaces). This should yield a frame list that
|looks like this:
|
|0001
|0050
|0100
|0002
|0003
|0004
|..
|0048
|0049
|0051
|0052
|..
|0098
|0099
|
| If you want to some how automate this, you can tweak the script
| to either break out the frame range into bits, or
|invoke 'rush -reorder'
| from within the script, after the job has been submitted:
|
|http://www.seriss.com/rush-current/rush/rush-command-line-optio
|ns.html#-reorder
| ..just parse the output of 'rush -lf', grab the
|first/middle/last frames,
| then call 'rush -reorder <first> <middle> <last>' to
|get those frames to
| appear first.
|
| Gets complicated if you want to also support batching.
|
|--
|Greg Ercolano, erco@(email surpressed)
|Rush Render Queue, http://seriss.com/rush/
|Tel: (Tel# suppressed)
|Cel: (Tel# suppressed)
|Fax: (Tel# suppressed)
|
|