Hi Katrin,
This should be better in tomorrow's build. Please let us know if we've still got it wrong.
Thanks,
Found 662 posts.
Search results Show results as topic list.
Solaris and Karma » Scene index plugins
- mark
- 2593 posts
- Offline
Solaris and Karma » Karma mipmap textures memory usage optimisation
- mark
- 2593 posts
- Offline
Having tiled mipmapped files means that the renderer only loads the portions of the texture that are required for rendering. So this saves on I/O.
Even if you have a 21K x 21K texture (https://visibleearth.nasa.gov/images/73909/december-blue-marble-next-generation-w-topography-and-bathymetry), if it's tiled and mip-mapped, the renderer will only load the portions of the image it needs to render. If you used the .png or .jpg as a texture, then the entire image would have to be read by the renderer.
Even if you have a 21K x 21K texture (https://visibleearth.nasa.gov/images/73909/december-blue-marble-next-generation-w-topography-and-bathymetry), if it's tiled and mip-mapped, the renderer will only load the portions of the image it needs to render. If you used the .png or .jpg as a texture, then the entire image would have to be read by the renderer.
Solaris and Karma » Karma mipmap textures memory usage optimisation
- mark
- 2593 posts
- Offline
Looking at render stats should help figure out where memory is being used up. With verbosity, the log should show how much memory was used by .rat files and by primvars (including displacement memory). Displacement memory should be better in H19.5.
- .rat files are always MIP Mapped. I don't think there are any tools to extract a specific MIP level.
-
- karma uses the screen space of the surface to determine the mip levels automatically. The shading quality can be adjusted using the shading quality multiplier in the render settings.
- For debugging mip maps, it's probably best to use .exr files since it's easy to create a map that has different diagnostics on each MIP level
- loading a .rat file in mplay will only display the largest MIP level.
- .rat files are always MIP Mapped. I don't think there are any tools to extract a specific MIP level.
-
imaketx
can be used to make mipmapped .exr or .rat files (or even .tif files). The advantage of .exr is that there are a lot of other tools that can be used (for example houdini ships with hoiiotool
- the OIIO Swiss-army knife utility). The disadvantage of mipmapped .exr files is that they are 16 bit float images, so you can't create an 8-bit texture for example.- karma uses the screen space of the surface to determine the mip levels automatically. The shading quality can be adjusted using the shading quality multiplier in the render settings.
- For debugging mip maps, it's probably best to use .exr files since it's easy to create a map that has different diagnostics on each MIP level
- loading a .rat file in mplay will only display the largest MIP level.
Solaris and Karma » Cryptomatte data from a 3rd party render delegate
- mark
- 2593 posts
- Offline
This is discussed a little bit in https://www.sidefx.com/docs/hdk/_h_d_k__u_s_d_hydra.html#HDK_USDHydraHusk [www.sidefx.com]
Hopefully that helps you get started.
The interface has changed for the next version of Houdini though so that there are no dependencies on the Houdini USD Bridge.
Hopefully that helps you get started.
The interface has changed for the next version of Houdini though so that there are no dependencies on the Houdini USD Bridge.
Edited by mark - June 28, 2022 09:22:42
Technical Discussion » How to read EXR metadata/header attribs?
- mark
- 2593 posts
- Offline
You can also use `iinfo -v foo.exr` to read all the metadata. In a future version of Houdini there's also the `-J` option to output in JSON.
Houdini also ships with
Houdini also ships with
hoiiotool
(a version of OIIO tool compiled against the Houdini version of OIIO).
Edited by mark - June 28, 2022 08:46:15
Solaris and Karma » Motion vector AOV in Karma
- mark
- 2593 posts
- Offline
I think you'll find that this will have a much improved workflow in the next major version of Houdini.
Solaris and Karma » .rat vs .exr in Karma
- mark
- 2593 posts
- Offline
There shouldn't be that much of a difference. .rat format supports different bit depths (8 bit integer, 32 bit float), while .exr is typically 16 bit float. Karma uses OpenImageIO for .exr textures, so it might be easier to troubleshoot texture issues. Performance wise, there shouldn't be that much of a difference.
Technical Discussion » Karma multiple checkpoint outputs (e.g. image.$SAMPLE.exr)?
- mark
- 2593 posts
- Offline
Technical Discussion » Karma timed renders
- mark
- 2593 posts
- Offline
karma --timelimit 300 foo.usd
This works with all render delegates (and not all render delegates provide percentage complete).
Solaris and Karma » Solaris - EXR Matrix Metadata
- mark
- 2593 posts
- Offline
This seems to work for me. With the attached .usd scene, I see the following when running
Please submit a bug with a reproducible test case if need be.
P.S. Adding slashes to metadata keys doesn't create valid USD (unless I'm mistaken):
iinfo -v output.exr
...
info:totalUTime (type double):= 7.324608
m4d (type m44d):= [
1, 0, 0, 0,
0, 2, 0, 0,
0, 0, 1, 0,
0.5, 0.2, -0.3, 1
]
pi (type float):= 3.1415
renderMemory (type double):= 1.3605591e+08
renderMemory_s (type string):= "129.75 MB"
Please submit a bug with a reproducible test case if need be.
P.S. Adding slashes to metadata keys doesn't create valid USD (unless I'm mistaken):
custom matrix4d driver:parameters:OpenEXR:exr/rs/camera/transform = (...
Edited by mark - March 16, 2022 15:37:51
Solaris and Karma » Mipmapped textures and Karma
- mark
- 2593 posts
- Offline
If you run imaketx on the source .png file and create a .tx file, the .tx file will not be stored as a .png file.
And it will be tiled and mip-mapped (as a .tif file). And it will work well with Karma.
% maketx foo.png -o foo.tx
% iinfo foo.tx
File: ./foo.tx (TIFF format)
Resolution: 256 x 256
Data: 8 bit integer
Color Model: RGBA
...
Edited by mark - Feb. 24, 2022 16:32:13
Solaris and Karma » Mipmapped textures and Karma
- mark
- 2593 posts
- Offline
Karma works best with mip-mapped .exr or .rat files which can be created with imaketx. For tiled, mip-mapped .exr files, you can also use tools like maketx or txmake. Karma should also work with tiled, mip-mapped .tif textures.
If you have .png or .jpg files as textures, there are two modes that karma can use to process these. Both of these modes will use significantly more memory and probably take longer for time to first pixel. So tiled, mip-mapped textures are better.
The default mode is to use OpenImageIO for texturing. There are a lot of ways to control auto-mip generation, cache, tiling etc. (see https://openimageio.readthedocs.io/en/latest/imagecache.html [openimageio.readthedocs.io] and setting the OPENIMAGEIO_IMAGECACHE_OPTIONS environment variable).
The other mode is to use Houdini's internal texture filtering, which can be enabled by setting
If you have .png or .jpg files as textures, there are two modes that karma can use to process these. Both of these modes will use significantly more memory and probably take longer for time to first pixel. So tiled, mip-mapped textures are better.
The default mode is to use OpenImageIO for texturing. There are a lot of ways to control auto-mip generation, cache, tiling etc. (see https://openimageio.readthedocs.io/en/latest/imagecache.html [openimageio.readthedocs.io] and setting the OPENIMAGEIO_IMAGECACHE_OPTIONS environment variable).
The other mode is to use Houdini's internal texture filtering, which can be enabled by setting
HOUDINI_ENABLE_EXR_TEXTURE=0
.
Solaris and Karma » Mtlx Transform Normal
- mark
- 2593 posts
- Offline
Solaris and Karma » Using a primvar string to give a texture path
- mark
- 2593 posts
- Offline
Solaris and Karma » Using a primvar string to give a texture path
- mark
- 2593 posts
- Offline
There's been a bit of discussion in the MaterialX group about texture variation. The issue with MaterialX is that they need to be able to enumerate all textures prior to rendering for some renderers (like GL), so driving a texture with a primvar is not really feasible.
When using Karma and MaterialX, you can intermix Usd Preview nodes and MaterialX nodes (this may not be documented, but it's true). So, you should be able to feed a Usd Primvar reader into a Usd UV Texture then feed that into a Mtlx Standard Surface. This should work with both CPU and XPU.
P.S. It will not work with other renderers though.
When using Karma and MaterialX, you can intermix Usd Preview nodes and MaterialX nodes (this may not be documented, but it's true). So, you should be able to feed a Usd Primvar reader into a Usd UV Texture then feed that into a Mtlx Standard Surface. This should work with both CPU and XPU.
P.S. It will not work with other renderers though.
Edited by mark - Feb. 12, 2022 16:34:36
Technical Discussion » Material X random node?
- mark
- 2593 posts
- Offline
Solaris and Karma » Camera Projections in Karma
- mark
- 2593 posts
- Offline
Solaris and Karma » MaterialX online library
- mark
- 2593 posts
- Offline
markIt looks like there's been an update to the AMD MaterialX library. The materials work a lot better in Solaris out of the box now. You should be able to just load them up using a File LOP. There may be some organizational things like paths to textures or shader names which might need some slight adjustment, but the materials are now way more compatible with Solaris.
The dev team is currently looking into this and hopefully will have some answers for you soon.
Technical Discussion » Karma Motion Blur way to strong / weird
- mark
- 2593 posts
- Offline
chfUsd expects the velocity primvar to be named
I am using velocity blur. But it doesn't work on packed primitives.
Made a quick setup to sandbox the issue.
No matter what I do, Motion blur only works if I unpack the transformed geometry before importing it into solaris/karma world.
velocities
. If you stick an Attribute Rename SOP before /obj/karma_test/output0
, the instance will pick up velocity properly and you should see motion blur. This is not obvious at all. It took a bit of debugging on my end to actually track this down.The other thing which I see you attempted was to use "Unpack" in
/stage/sopimport1
. This uncovered a bug in Karma. This should be fixed in tomorrow's daily build. So leaving the v
attribute alone, but choosing Unpack in the SOP import should work in tomorrow's build.
Technical Discussion » Karma Motion Blur way to strong / weird
- mark
- 2593 posts
- Offline
It almost looks like the topology might be changing frame to frame. Are you using velocity blur?
-
- Quick Links