DICOM @ OFFIS

Of course, a crash should never happen ... To the original poster ("martinrame"): Which version of the DCMTK are you using? It is strongly recommended to use the current release (3.6.0) because it contains many bug fixes, also regarding the various scaling algorithms. What is the log output in verbo...

I never had any exception when processing CT images, so I guess that it is caused by your build system / compiler switches. In general, DCMTK does not use exceptions - apart from some internal exceptions in the new modules "oflog" and "dcmjpls".

Two general remarks: You should always check the return value when using a function/method. This is also true for the DCMTK. The 'pos' / 'itemNum' parameter of both findAndGetXXX methods is 0-based, so "1" is the second entry. And the definite answer to many if not most questions: Reading the docume...

Hmm, the name of this site is "DICOM @ OFFIS - Discussion Forum for OFFIS DICOM Tools", and the name of this forum is "DCMTK - General". I thought that this is self-evident :-) Is there any othre forum where I can ask about the Dicom Java Classes? This depends on which Java DICOM toolkit you are usi...

No, this forum is about DCMTK, a C/C++ DICOM toolkit. Of course, you could use JNI to wrap the main classes to Java (as demonstrated with the DICOMscope application many years ago).

Sorry, you are right. So, please forget the last sentence of my above posting

Basically, I would agree. However, if the customer really wants to use the DICOM print protocol for this purpose, this would of course be possible (as I wrote in my previous posting). A use case could be that the department has a DICOM paper printer that should also be used for ECG printouts.

If you would use the DicomImage class, the rendered output would always be unsigned, even for signed CT images.

DICOM Basic Print Management requires a pre-formatted bitmap, so you first have to convert the signal data (ECG Waveform) to a bitmap.
By the way, the same applies to SR documents - DICOM Basic Print Management is only defined for images/bitmaps.

Which project do you mean, DICOMscope?

performQuery() returns a status of good() if the query could be sent to the SCP, which is apparently the case in your example. The DIMSE status is available in the callback function - see DcmFindSCUDefaultCallback::callback().

You need to configure the (root) logger accordingly -- as described in the documentation. There are multiple ways to avoid any output to the console. One of them is the following (add this code to the beginning of your main function): log4cplus::SharedAppenderPtr nullapp(new log4cplus::NullAppender(...

Change the VR to "OB" and the length to "0xffffffff" (i.e. undefined) and the image might look like expected.

I've added an entry to our to-do list that we might add a new "compatibility option" to the DCMTK that allows for supporting such an incorrectly encoded DICOM image.

This is easy: The DICOM image file you've sent to us is corrupt (in many ways). The main issue is that the pixel data is not encoded in an encapsulated manner (sequence of pixel items) as it is required by the DICOM standard: (0002,0010) UI =JPEGLossless:Non-hierarchical-1stOrderPrediction # 22, 1 T...

I am not using software, I am rendering the image on UIImageView on iPad ... So, you are definitely using software :) Probably software that is written by yourself based on the DCMTK, right? W: computed (3356700) and stored (772057) pixel count differ do you have any idea what that means ? Yes, it ...