Rodrigo Martin
RodrigoMartin
About Me
EXPERTISE
Generalist
INDUSTRY
Film/TV
Connect
LOCATION
Madrid,
Spain
WEBSITE
Houdini Skills
ADVANCED
Procedural Modeling | Digital Assets | VEX
INTERMEDIATE
Environments | Solaris | Karma | PDG | Python
Availability
Not Specified
Recent Forum Posts
Lop Import Camera performance issues. March 10, 2025, 8:59 a.m.
replying to myself in case someone in the future find this useful:
I've found a workaround to the python bottleneck using VEX, reading with usd_attrib the values from the camera that I need to read (horizontal aperture, focal length and vertical aperture) storing this on points (1 point per camera) and then it's easy to read this values from the rest of the network, (including the lop import camera using a multiparm with the point values in a spare node)
I got a reduction in time from 15 seconds to 1.5 it's still far from what you get using legacy cameras in OBJ (around 0.45 seconds) but it's much better than using the default lop import camera python way.
I've found a workaround to the python bottleneck using VEX, reading with usd_attrib the values from the camera that I need to read (horizontal aperture, focal length and vertical aperture) storing this on points (1 point per camera) and then it's easy to read this values from the rest of the network, (including the lop import camera using a multiparm with the point values in a spare node)
I got a reduction in time from 15 seconds to 1.5 it's still far from what you get using legacy cameras in OBJ (around 0.45 seconds) but it's much better than using the default lop import camera python way.
Lop Import Camera performance issues. March 10, 2025, 5:38 a.m.
Hi everyone,
I have a question related to the node Lop Import Camera in OBJ. I've been doing some VEX dependant of camera view and positions, and I started working with normal OBJ cameras, but then I tried with USD cameras importing them to OBJ with the lop import camera nodes, and found that the cook times raised a lot.
I saw that the lop import camera uses python to read the values from the usd camera, so I tried removing them and got times down again.
Just for some context, I'm doing a multicamera prune in sops using the lop import camera to read this cameras in obj. Mainly using toNDC VEX function to read positions on each frame and then work with that data to prune points.
Is there a better way to do this than lop import camera + toNDC? Right now the bottleneck is the python scripts on the camera parms, so any improvements on that would be awesome!
As always thanks guys for reading me!
I have a question related to the node Lop Import Camera in OBJ. I've been doing some VEX dependant of camera view and positions, and I started working with normal OBJ cameras, but then I tried with USD cameras importing them to OBJ with the lop import camera nodes, and found that the cook times raised a lot.
I saw that the lop import camera uses python to read the values from the usd camera, so I tried removing them and got times down again.
Just for some context, I'm doing a multicamera prune in sops using the lop import camera to read this cameras in obj. Mainly using toNDC VEX function to read positions on each frame and then work with that data to prune points.
Is there a better way to do this than lop import camera + toNDC? Right now the bottleneck is the python scripts on the camera parms, so any improvements on that would be awesome!
As always thanks guys for reading me!
How to set a button strip menu tokens with python. Sept. 4, 2023, 6:52 a.m.
Hi! I am trying to make a button that updates the tokens in a button strip when pressed, right now I have made this code in the action button of the parameter, but it gives me the error "Invalid size"
the menuItems consist of a list of strings, for example:so it contains labels and tokens.
the menuItems consist of a list of strings, for example:
["cluster1","cluster1","cluster2","cluster1"]
import hou pos = 1 menuItems = kwargs['node'].node("VALUES").geometry().attribValue("clusterList" + str(pos)) kwargs['parmtuple'].set((menuItems))