CT Image GPU renderer adds lot of white noise
See original GitHub issueHi,
For our custom DICOM viewer we use following libs:
"@cornerstonejs/core": "^0.16.3",
"@kitware/vtk.js": "24.18.7",
"wslink": "^1.8.2",
"gl-matrix": "^3.4.3”,
"cornerstone-wado-image-loader": "^4.2.1"
Unexpetedly cornerstone adds a lot of white to images while rendering (except first image in series):
But if you’re setting CPU render only - this “white” effect dissappears
cornerstone.setUseCPURendering(true)
What may cause that?
regards, –leo
Issue Analytics
- State:
- Created a year ago
- Reactions:2
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Volume rendering produces block of "white noise" - Support
I'm able to render volumes from other datasets like MRHead and CTChest with no problem. The dataset I'm trying to render is this...
Read more >Chapter 39. Volume Rendering Techniques - NVIDIA Developer
Direct volume rendering methods generate images of a 3D volumetric data set without explicitly extracting geometric surfaces from the data (Levoy 1988).
Read more >Freesync Issue - Static noise image : r/Amd - Reddit
Story: HDCP was giving me a static noise image with Ultimate engine ON(had no clue it was HDCP). With standard engine there was...
Read more >Image noise - Rosetta Code
Generate a random black and white 320x240 image continuously, showing FPS (frames per second).
Read more >Exposure Render: An Interactive Photo-Realistic Volume ...
We present a re-usable GPU-based interactive direct volume renderer that ... [8], introducing translucency and caustics, at the cost of static lighting.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@toropok This might have been fixed by 0.16.8
@toropok Is there any chance you can post the anonymized DICOM file for us to test and fix?