DICOM @ OFFIS

As far as I know, the img2dcm tool (and the underlying class library) does not convert the color model of the input image. It just feeds the JPEG stream into a DICOM image (and sets the header fields appropriately). Also, JPEG images with RGB color model are not that usual because the compression ra...

getOutputData() renders an output image with the given parameters from the internally stored pixel data (intermediate representation), i.e. a new memory buffer is allocated internally (and freed automatically for the next call or during destruction).

Are you sure that your JPEG image uses RGB? What does img2dcm produce for this particular image? There is another problem that is the transfer syntax of the converted dicom image is "Transfer Syntax UID=1.2.840.10008.1.2.4.50", so I can't transfer it to PACS using storscu. Of course, you c...

Internally, the DicomImage class stores color images as three separate planes, one for each color component (R-G-B). I'm not sure whether QImage supports this format. And, as I said before: I would not recommend to use the internal pixel data representation directly. If you don't need the DicomImage...

Thank you for the report. DCMTK snapshots are not tested with MinGW/MSYS. Releases are, but DCMTK 3.6.0 did not yet use libiconv. Could you please test the following patch with your system: --- ofstd/libsrc/ofchrenc.cc 17 Nov 2011 16:13:19 -0000 1.10 +++ ofstd/libsrc/ofchrenc.cc 27 Feb 2012 07:32:33...

Re. 1: No, DCMJP2K does not support JPIP. This protocol is part of the JPEG 2000 standard (a different part though) and referenced by the DICOM standard, but we do not (yet) support it. Re. 3: DICOM protocol does not support streaming. This is the reason why JPIP was introduced as a separate DICOM t...

but the buffer that I need to allocate must be valid for all the QImage life. Ok, but you do not need to re-allocate the memory buffer each time you call getOutputData(). This only has to be done once for each image (of a particular size). I'm not sure about the Qt-related part of your question bec...

Why don't you use the getOutputData() method where you can provide an externally allocated and managed memory buffer?

Unfortunately, I don't know what the requirements for your "Canvas Image" are because you never told us. I'm sorry but I still have no idea what you are talking about. What about providing more background information?

Thank you for pointing this out. This enhancement is also part of the new DCMTK snapshot we've just released.

Why don't you then store a copy of the original getOutputData() result and delete the DicomImage?

You wrote in a previous posting:

I think this is the correct array of all three RGB planes....but I can't use the getDataArrayPtr().

Why can't you do that?

Why don't you use getOutputData()? This is what the DicomImage is for: rendering of DICOM images.

No, getInterData() returns a pointer to an DiPixel object which has various get methods. For color images, you get direct access to the internal pixel data array: /// pointer to pixel data (3 components) T *Data[3]; I know that I already wrote that many times in other similar postings: getInterData(...

On a related note, can you suggest *any* publicly available DICOM SR viewer? Unfortunately, I can't. Of course, there are a couple of general purpose DICOM SR viewers like the one that is part of DICOMscope , which is basically using the HTML output of dsr2html. However, the output might not be app...

I'm sorry but I don't understand the background of your question. Basically, getInterData() also allows for accessing color (RGB) images. However, I'm not sure that I would recommend that depending on your use case.