Render scheduler

[rgbaguy]

Hi there,

I want to look into the possibility of developing a render scheduler (a simple version with a custom goal in mind). The only problem is, how do I tell whether the renderer (any in maya - software, hardware, mr) has completed a frame?

Is this possible? I had a look at the API doc, couldn't find anything that would suit my needs?

Or is the only way to do this to actually do batch renders, except this time just 1 pass and 1 frame and use the maya status return as result? So in that case, would have to open a scene file (contains a bunch of layers etc) - keep that file open and track which frames of which passes to render/have been rendered.

What about Qube!, as I understand it returns progress information per frame whereas backburner gives progress updates only on completion of a task.

And no, please don't say it would be easier to buy Qube! or whatever. I don't have that option.

Hope someone can help!

Thanks!

[joojaa]

The only problem is, how do I tell whether the renderer (any in maya - software, hardware, mr) has completed a frame?

Well, there are lots of easy ways. (heres the short list form top of my head)

1. put in pre/post frame/job/layer melscript that notifes you wneevere a frame is rendered.
2. read the text stream maya batch prints when rendering, it contains info on progress (well in mentalray only if you enable progress messages). Should be pretty standard.
3. modify the mel procdure that calls the renders to notify per frame (this is essentially the same as pre/post melscript but its hidden form the user)*
4. monitor your disk, whenever maya finsihes a frame it starts a new file, notifications on disk access is easy. You can also detect if maya has hung if the file thats currently rendering hasnt been touched for a while. This has the added benefit of not actually needing maya at all so your program should translate to any application in jiff. Also it can detemine the actual prrecental prgress by looking what tiles are finsihed.
5. make a shader that emits progress messages to your engine.
6. Use tha same command port architecture for messages as maya uses, thisway you dont have to roll out your own.

(any in maya - software, hardware, mr)

well actually theres 4 of them built in software, hardware, mr and vector. But seriously you need to be able to tackle even more since maya has atleastfollowing additional options renerman for maya, turtle, vray. That can be bolted along with a myriad of other options.

I had a look at the API doc, couldn't find anything that would suit my needs?

Your reading the wrong docs. Maya api only deals with maya dg evelauation, mostly (some viewport and event stuff also) but rendering is a outside of maya job. Because it needs to support mentalray and other erdnerers which have thier own API's etc. So its actually a job for mel.

And no, please don't say it would be easier to buy Qube! or whatever. I don't have that option.

well may be however did you condiser that getting one would be cheaper than rolling your own, even if your situation is very convoluted they usually offer you a much easier to work with api/ script envirnement to work on. And indeed some of them are FREE OF CHARGE.

*on a related trick you can use the api to monitor launch and fill in the post pre melscripts.

[rgbaguy]

Hi Joojaa!

Thanks for the quick reply. I did think of MEL, but wanted to see if there were any other takes.

MEL is probably the best way I guess...

That way I don't have to worry about which renderer is going to be used

Thanks!

[joojaa]

Just wanted to add that whever you call the batch render maya runs:

mayaBatchRenderProcedure.mel (found in scripts/others)

Which you can modify to suit your needs. Copy it over to your own script path directory so you retain the factory original should you screw up.

PS: I use a modified version of this to collect render statistics.

[rgbaguy]

Thanks for that Joojaa! I'll definitely look into it!