> > > My workaround would be to do add the metadata as a second process, after > the render is done, but I hope to avoid that if possible... >
There is a way to do as you describe, but why would you want to avoid a second process? I know most people frown upon running it as a second process but in most cases where I've come across it's usually what the second process is being used for rather than any despite towards the notion of a second process in it self. Some bad ones: --[ The second process involves starting up secondary application or software. --[ The second process breaks a lot. --[ The second process alters images so reviews are inaccurate. --[ Some genius figured to write an embedded header altering plugin which locks the files down to only being loadable in a modified instance of Maya. The easiest one I know of is to just simply use the generic exr python libraries and write additional header attributes as a post-mel python Frankenscript within the render globals, ugly as heck but works a charm, that way it's technically still an internal Maya "process" completing a rendered image but I'm sure a lot of folks can suggest a more direct and API friendly way of achieving this. In the meantime I hope this helps. -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/261e6302-cda4-4785-9067-f6d186b4d47d%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
