After some rethinking I changed my approach a little, reason is, EXR have a good support for long/custom metadata but others don't have limited support, DPX for example, which we use as well.
So instead of figuring out each format metadata support, I rather dump the metadata in a file or a Database, located where the images/movie are, I could have infinite amount of metadata without relying on each format ability to store metadata. this is doable in our environment since the rendered files won't get moved from the metadata file. I still wish MR would have a built in hook to inject metadata :) but this workaround would help improve on other wider issues as well On Mon, Dec 23, 2013 at 12:19 PM, Ævar Guðmundsson < [email protected]> wrote: > Hehe, cool, have seen so many people get carried away with doing this I'm > always retentive on showing people how ( like, seriously, I don't want to > get blamed if you then use the method in production and break a delivery > frame with it, when you start altering production raw frames as it sounds > like is the case here, things tend to get more serious than a forum can > accommodate for I'd think ) > > If nobody else has pasted by the time I get back in front if Maya I'll > send you a plug and play snippet that works in any configuration, super > clean for you to evaluate, it's not tricky at all but not a chance I could > resite it from memory typing on a phone :) > > > > > On 23 Dec 2013, at 19:10, Asi Sudai <[email protected]> > wrote: > > I was hoping for a clean way to let MR do the metadata injected and avoid > post-mel or a 2nd post-process. > I'm hoping we'll move from MR soon, that's why I don't want to develop > more code around it, not cause post-process is a problem. > > thanks for replying Evar > > > > On Saturday, December 21, 2013 2:31:51 PM UTC-8, Ævar Guðmundsson wrote: >> >> >>> 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 a topic in the > Google Groups "Python Programming for Autodesk Maya" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/python_inside_maya/Tggunq6Bo0Q/unsubscribe > . > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/python_inside_maya/887da10b-69b2-4123-9b18-eac0168fdcc0%40googlegroups.com > . > For more options, visit https://groups.google.com/groups/opt_out. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Python Programming for Autodesk Maya" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/python_inside_maya/Tggunq6Bo0Q/unsubscribe > . > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/python_inside_maya/AE6A2F8A-0D93-42AC-92F8-9F73ECBBA007%40gmail.com > . > For more options, visit https://groups.google.com/groups/opt_out. > -- Asi Soudai | Pipeline Supervisor | Goldtooth Creative Agency, Inc. -- 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/CAP-786d2hprDbgA4OhOH%2BKGg_XLXH%2BodGaVSp07eZ%2B-7yh7W6A%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
