Spencer Luebbert

@

rafal
Looking at it, it seems like `_standardLibrariesDoc()` uses `DEFAULT_LIBRARY_PATH` which is set to Houdini's installation path. So it does not appear like it's straight forward to specify own library path.

Hi Rafal. Do you know if there has been any updates around library handling in the last couple of years?

mbeaud
So the idea would be, from one materialX graph (that could be created anywhere, Houdini, MaterialxGraphEditor, ...), get multiple "black boxes" with only the chosen inputs available for each DCC

@mbeaud where you able to figure this out? I'm stumbling through the exact same setup right now. One issue I have, is that unless I write the mtlx file by hand (in text) there is no way to define a node def where only a smaller set of specific inputs are exposed to the DCCs.

I think the right idea is to ship higher level convivence mtlx nodes that are built out of standard mtlx nodes, not mtlx HDAs. That would keep things cross compatible.