For instance once a render is done, the windows are closed and another chor is loaded and the render to file is clicked... etc.
Therein lies the problem as far as I can tell.
Who knows how to remotely cue up a Choreography?
Who can automate the clicking of the render to file icon?
I sure can't.
I half suspect A:M can take such arguments upon loading... render through if you will... but maybe not.
Hash Inc ain't tellin' all their trade secrets.
'Render to File' can be assigned a shortcut key.
If you can find a program that will hit that key for you automagically... kerboom... You are rendering.
Well... not quite but at least one click closer to it.
'File: Import Choreography' can be assigned a shortcut key too.
Getting a program to import a Chor wouldn't be enough though as it would have to know what Chor to open and click the dialogue button too. I believe the last Chor opened will be the default entry in the dialogue box.
But again, perhaps more importantly, what are the underlying needs that scripted rendering addresses?
I can think of one off hand that might not be obvious.
Having the renderer spit out an image in a low resolution (thumbnail) first and then automatically go on to render a high res version.
The benefit here would be that we get to see our render quickly while the rendering goes on to do the dirty work behind the scenes.
Extending that further...
Lets say I want to sample a high res image to make sure something is going to render properly... a particularly important shot with hair.
If we could just see the most important part of the image we are interested in we could make a decision to continue or terminate the session based on that. If the test meets our approval it gets pushed on to the background renderer.
I would imagine the most apparent use of scripted rendering would be to have a list of choreographies that the renderer would grab and chew on until consumed. This type of rendering would be ideal for greenlighted projects in the cue. In my estimation its not the best solution for determining what we want to render. For that we need evalators and evaluation tools. Are the colors correct? Is this shot too dark? Too light? Too Blurry? How can we communicate our needs to the renderer? How can it respond with a proper solution.
When looking for solutions I like to shoot for the moon.
We may not ever get there but we can usually count on a clearer view.
Scripted rendering could get really complex.
It would need to be pretty complex to satisfy everyone's needs.Now back to your reality based query Bill.
(Sorry for all the Off Topic)
You really should look into RenderDone
. I assume it can still be used in v14.
Contact Glen Anthofer and see if he's updated it anymore for himself.
At the very least you'd be able to Render your animations out and shut down A:M immediately thereafter.
If you can then load A:M with another Project automatically you'd just have to Whack the Render to File button.
I'm sure Glen would gladly share his knowledge and code, especially if someone were interested in extending it.