Search found 7 matches
- Mon, 2008-10-20, 14:23
- Forum: DCMTK - General
- Topic: Levelling on images containing VOI LUTs
- Replies: 3
- Views: 3826
- Wed, 2008-10-08, 08:24
- Forum: DCMTK - General
- Topic: Levelling on images containing VOI LUTs
- Replies: 3
- Views: 3826
Levelling on images containing VOI LUTs
Hi all, I have a question regarding levelling on images containing VOI LUTs. As of PS 3.3 2008 C.11.2.1.2 p.881 it is not possible to apply VOI LUTs and windows at the same time. This seems reasonable to me. But is there a possibility in DCMTK to alter the brightness/contrast or output-range (window...
- Wed, 2007-08-01, 08:50
- Forum: DCMTK - General
- Topic: Corrupt images after calling writeImageToDataset()
- Replies: 2
- Views: 3807
- Wed, 2007-08-01, 08:48
- Forum: DCMTK - General
- Topic: Corrupt images after calling writeImageToDataset()
- Replies: 2
- Views: 3807
Corrupt images after calling writeImageToDataset()
Hi there! Images loaded with the option CIF_MayDetachPixelData are corrupt after calling writeImageToDataset() and saving them again. This happens at least when the following conditions are met: BitsAllocated = 16 BitsStored = 16 HighBit = 15 RescaleSlope > 1 Loading such a file and saving it produc...
- Mon, 2006-09-18, 08:48
- Forum: DCMTK - General
- Topic: Bad memory access in DiOverlayPlane
- Replies: 2
- Views: 3396
Bad memory access in DiOverlayPlane
Hi there! When dealing with 1Bit Overlay Planes from Tag (0x6000,0x3000), DCMTK 3.5.4 crashes within DiOverlayPlane::getNextBit() in diovpln.h. The error results from DiOverlayPlane::reset(). StartPtr always points to the start of the current frame while BitPos counts from start of Data. The result ...
- Mon, 2006-08-21, 12:16
- Forum: DCMTK - General
- Topic: DicomImageClass::rangeToBits adds 1 (DCMTK 3.5.4)
- Replies: 3
- Views: 4048
- Mon, 2006-08-21, 08:46
- Forum: DCMTK - General
- Topic: DicomImageClass::rangeToBits adds 1 (DCMTK 3.5.4)
- Replies: 3
- Views: 4048
DicomImageClass::rangeToBits adds 1 (DCMTK 3.5.4)
Hi there! DicomImageClass::rangeToBits uses tobits from diutils.h to calculate the number of bits necessary for a specific value. Is the adding of 1 to the result of tobits intended? Because this leads to a higher number of bits than I expect. Or am I just misinterpreting the functionality of this m...