jance wrote:
[posted to rush.general]
We got used to just hitting the F1 key in Rush to launch Framecycler and
view the rendered frames of the currently selected job (at a previous
facility we worked at).
Sounds great -- if you have the script, post it.
Since irush invokes the command you program to the F1 key
with the RUSH_JOBID variable set to the current job, yes, it
should be possible to have that command poll rush to find out
where the rendered images are going, and turn that into a frame cycler
command.
I don't have framecycler here, or know its syntax offhand,
and I guess it depends on what kind of renderer you're using
(maya/softimage/shake..) to assist in how to pull off determining
where the output images are going. Some renderers print this clearly
in the logs, or some have ascii scene files you can grep it out of.
One other approach, besides having the F1 key invoke a magic script,
is to tweak the submit script to have the 'imgcommand' invoke the
framecycler stuff. (when you middle click on a frame in irush, it
invokes the 'imgcommand' for the job, if one is configured)
Many of the submit scripts set up the 'imgcommand' automatically
to invoke the submit script itself with the '-imgcommand' argument,
so that whatever logic is needed to determine the rendered image directory
can be coded into the script.. then it invokes an image viewer.
The 'imgcommand' is documented here:
http://www.seriss.com/rush-current/rush/rush-submit-cmds.html#ImgCommand
..and I suppose you could tweak the submit script's code for 'imgcommand'
to invoke framecycler instead.
It gets complicated because sometimes the user specifies the image directory
as a submit option, or sometimes it's left blank, such that the scene file
determines where the images are written. If the scene file is binary format,
it's impossible to determine from that where the image path is. In those cases
rush tries to grep the log file for an output image pathname, which some
renderers will print, depending on verbosity levels.
Does any have the (quick and easy?) science to do this? Our scripting
buddy gave us some info, but it's pretty involved, so I'm wondering if
there's something simple. I'd love to just paste something into the
command line of the hotkey editor and be done! Pipe dream?
It does involve some scripting footwork, described above.
I imagine there's no one script that will work for all cases,
since different renderers have different file formats, log messages,
and command line overrides.
Get a scripter involved to assist if not up to the task.
Possibly someone on the list here can paste a script of their own,
but I imagine we'd have to first know what renderer you're working with.
--
Greg Ercolano, erco@(email surpressed)
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Cel: (Tel# suppressed)
Fax: (Tel# suppressed)
|