Andriy Babak
ababak
About Me
VFX Pipeline supervisor at Plarium
EXPERTISE
CG Supervisor
INDUSTRY
Film/TV
Connect
LOCATION
Ukraine
WEBSITE
Houdini Skills
Availability
Not Specified
Recent Forum Posts
hou.IPRViewer.saveFrame() + OCIO/ACES March 23, 2023, 8:48 a.m.
Hi Moritz,
Try to use it like this:
Cheers,
Andriy
Try to use it like this:
ipr_viewer = hou.ui.paneTabOfType(hou.paneTabType.IPRViewer) if not ipr_viewer: return "" conv_lut = os.path.join( os.path.dirname(os.getenv("OCIO")), "baked", "houdini", "Rec.709 for ACEScg Houdini.lut", ).replace("\\", "/") ipr_viewer.saveFrame(path, 0, -1, -1, "C", "C", "*", conv_lut, 1.0, False)
Cheers,
Andriy
Pass some data into custom Asset Resolver June 14, 2022, 3:57 p.m.
As there are no replies, I'll try to add my thoughts.
Currently I've come up with this solution: asset resolver gets its context path with a suffix:
Then in CreateDefaultContextForAsset I separate the context path ("/path/to/context/file.usd") and decode the key-value pairs into my context dictionary.
This solution is almost fine as I can encode my data and use configureStage node's "resolvercontextassetpath" parm to send this to my resolver.
Any other ideas?
Currently I've come up with this solution: asset resolver gets its context path with a suffix:
/path/to/context/file.usd?key1=value1&key2;=value2...Then in CreateDefaultContextForAsset I separate the context path ("/path/to/context/file.usd") and decode the key-value pairs into my context dictionary.
This solution is almost fine as I can encode my data and use configureStage node's "resolvercontextassetpath" parm to send this to my resolver.
Any other ideas?
Pass some data into custom Asset Resolver June 7, 2022, 3:09 p.m.
Could you share some thoughts on possible options of setting some key-value pairs in Solaris to read them back in a custom Asset Resolver?
The data could be stored in some JSON files, addressed by the Resolver Context or in the environment variables, but I'd prefer some native (or custom) node-based solution if it does exist.
Thank you.
The data could be stored in some JSON files, addressed by the Resolver Context or in the environment variables, but I'd prefer some native (or custom) node-based solution if it does exist.
Thank you.