Hello,
I am trying to understand the behavior of camera cache imported with the sub layer node (tried abc and usd), the camera has been exported from maya where it was timecoded at 25 fps. Houdini is set by default at 24 fps in the animation options, therefore i though that by changing to 25fps the camera cache would behave correctly, but it is not the case. to make the camera having the same animated frame range than maya, I needed to remap the speed of the camera sublayer node from 1 to the value of 25/24=1.0416.
So it appears that regardless the fps global settings value the loaded cache is always interpreted at 24fps, is this correct? do the global fps option affect the lop nodes at all?
how do I tell to the sublayer node, that the cache I am loading is timecoded at 25fps and not 24fps? should it be automatic?
Cheers,
R.
houdini 18.5.696
fps global options and caches
4979 4 1-
- Ruspa
- Member
- 30 posts
- Joined: Feb. 2021
- Offline
-
- mtucker
- Staff
- 4565 posts
- Joined: July 2005
- Offline
-
- Andy_23
- Member
- 918 posts
- Joined: March 2014
- Offline
-
- jsmack
- Member
- 8177 posts
- Joined: Sept. 2011
- Offline
Andy_23
This seems related to issues I had with importing Alembics onto the stage. They always came in at 24fps. I needed to use a configure layer LOP and set the FPS explicitly. The global FPS setting doesn't seem to affect imported layers. Again, this was with Alembics only.
That's because the alembic usd plugin has the framerate hardcoded as 24fps.
-
- Ruspa
- Member
- 30 posts
- Joined: Feb. 2021
- Offline
Thanks everyone for the answers,
the usd file from maya does say:
#usda 1.0
(
endTimeCode = 1284
framesPerSecond = 25
metersPerUnit = 1
startTimeCode = 1001
timeCodesPerSecond = 25
upAxis = "Y"
)
ive also tried to convert the maya abc into usd with solaris, the result (the data) is the same.
in both cases, when I am loading the usd file into solaris the result is not correct. but by assigning the a configure layer and forcing it to 25fps it "seems" doing the job. Said that, the viewport is not really consistent in visualizing the result, which brought me a few times to misjudgment, by changing properties/values on the configure layer node, at times, the node does not update the viewport.
the usd file from maya does say:
#usda 1.0
(
endTimeCode = 1284
framesPerSecond = 25
metersPerUnit = 1
startTimeCode = 1001
timeCodesPerSecond = 25
upAxis = "Y"
)
ive also tried to convert the maya abc into usd with solaris, the result (the data) is the same.
in both cases, when I am loading the usd file into solaris the result is not correct. but by assigning the a configure layer and forcing it to 25fps it "seems" doing the job. Said that, the viewport is not really consistent in visualizing the result, which brought me a few times to misjudgment, by changing properties/values on the configure layer node, at times, the node does not update the viewport.
-
- Quick Links


