DICOM @ OFFIS

In DICOM, the expected behavior of a storage SCU is to first check if an image can be transmitted in compressed form, and if this is not the case, then to silently decompress the image and transmit in uncompressed form. Apparently the SCU does not have a decoder for JPEG lossless, so this fails (and...

I apologize for the late response - somehow we have apparently missed this thread. I have created an issue in our bug tracker, see https://support.dcmtk.org/redmine/issues/1145. If you have meanwhile found further information whether this is related to a specific bug in oflog, a timing issue, networ...

Transmission of a DICOM image in JPEG lossless will only work if during association negotiation a presentation context is proposed and accepted where SOP Class is CT Image Storage and Transfer Syntax is JPEG Lossless, Non-Hierarchical, First-Order Prediction (Selection Value 1). This has nothing to ...

Thanks for letting us know. I will put it on the to-do-list to remove the __BORLANDC__ #ifdefs, which were intended for a rather ancient version of Borland C++.

Sorry, I will not be able to debug your code for you. What I can say is that apparently you are sending invalid data over the socket. DCMTK should not even be able to generate or send an attribute (0008,0052) with odd length.

You cannot use DIMSE_sendEchoResponse() in a class derived from DcmSCP. You should instead prepare the response message in a T_DIMSE_Message structure and send that using DcmSCP::sendDIMSEMessage(), which is protected (i.e. accessible in a derived class).

First of all, there is no documentation that describes all of the API changes from version to version. Some changes are typically necessary from release to release, but in many cases these are relatively small. Now, DCMTK 3.5.4 is almost 20 years old (it was published in 2005), therefore, it is hard...

I cannot say that I really understand what your code is doing. I suspect, though, that your function findContainerOfNode() returns a pointer to the wrong DcmItem instance. Note that a DICOM file (class DcmFileFormat) contains two different DcmItem instances, one for the meta-header (i.e. all attribu...

There is no easy way of replacing the JPEG library that is built into DCMTK (based on the IJG JPEG library version 6) with libjpeg-turbo. While both libraries share a common ancestor, the differences are big enough that replacing one by the other is not trivial. You will find in the DCMTK issue trac...

The steps all seem to be correct. My guess is that your self-signed CA certificate is lacking the X.509 extension that marks it as a CA certificate. When printing the content of the certificate with openssl x509 -in <filename.pem> -nooout -text , you should see the following X.509 extensions: X509v3...

For your information, I have fixed this issue today and committed the fix as commit #ae6352657. This will now run though our nightly builds and should become visible in the public git if no follow-up issues occur. The fix turned out to be fairly simple: diff --git a/oficonv/libsrc/citrus_iconv_none....

Sorry, at this point I will be unable to help you. The CMake output looks good, and I cannot say why the Android emulator does not become ready. Unfortunately, the developer of the Android port is not active in this project anymore. Other than this, I can only point you to the following document des...

You fail to mention the operating system on which you are developing. For now I will assume that you intend to compile on Windows. Note that we provide pre-compiled versions of all external libraries for various Visual Studio compilers and compiler settings. Most of these are static libraries, with ...

This looks like an incompatibility between an outdated CMake build script and a relatively new version of CMake. The error is caused by a cmake_minimum_required() statement in one of the CMake scripts, I guess somewhere in /Users/xxx/Library/Android/sdk/ndk/27.2.12479018/build/cmake. The statement p...

ANNOUNCEMENT Version 3.6.9 of the OFFIS DCMTK (DICOM toolkit) software is now available for public release. This release includes the following main changes over the previous version 3.6.8: DCMTK 3.6.9 builds correctly on older and up-to-date versions of GNU gcc (9.5.0 to 14.2.0), Clang (14.0.6 to 1...