In the Shading AOVs, p 216 . talking about more network traffic and exrs with tons of extra image layers; Do you still have issues now with Exr2? It's meant to just load in the layers pulled, not the entire file as in Exr1.
The OpenEXR lib allows you to select the channels you want to read, and has for quite some time. COPs and MPlay will only load and decompress the data that it needs for that frame, and this gives a pretty big performance boost for reading a small subset of channels from a huge EXR file. So at least with Houdini, it comes down to how much disk space you have available.
twod COPs and MPlay will only load and decompress the data that it needs for that frame, and this gives a pretty big performance boost for reading a small subset of channels from a huge EXR file. So at least with Houdini, it comes down to how much disk space you have available.
The lesson here for all is never underestimate the power of COPs
I have been using COPs extensively, more as an image engine than to do final composite and they are extremely useful for me, the fact that you can embed a COP network in an asset and run it to create composition is incredibly interesting.
My only thing is that they need some love, specially I miss a tracker as this will feed data to SOPs and the power of such a possibility would amazing.
:-)
MartybNz
twod COPs and MPlay will only load and decompress the data that it needs for that frame, and this gives a pretty big performance boost for reading a small subset of channels from a huge EXR file. So at least with Houdini, it comes down to how much disk space you have available.
The lesson here for all is never underestimate the power of COPs
This wraps Shading and if any of you want to suggest any other particular I will try to add it, in the next day I will consolidate it in one single document (shading that is) like I did with general concepts.
Jordi, that is an interesting approach to HDAs, other option might be:
1 material - 1 HDA, group of those materials(HDAs) saved to same .otl (metals.otl?) and diplayed in separate TAB sub menu (not sure about galleries but they might help too)
EDIT: or is it something you'll speak about in Digital Assets section?
owlYzarc Jordi, that is an interesting approach to HDAs, other option might be:
1 material - 1 HDA, group of those materials(HDAs) saved to same .otl (metals.otl?) and diplayed in separate TAB sub menu (not sure about galleries but they might help too)
EDIT: or is it something you'll speak about in Digital Assets section?
I have not tried but if you consider in my previous library I have close to 500 materials maintaining these, versioning them and probably loading will be more painful if each material is an HDA.
I think these materials will be then copied to the project, then modified by adding scratches, dust, etc… and used on the the project so you end up with a per project library so it could be very cumbersome I think
Anyway, if you give it a go I would love to know your results.
And very interesting thing to see Pixar has embraced fully this approach I have been banging about for more than 6 years (the guys at The Mill know very well)…
