DICOM @ OFFIS

JPEG baseline is a lossy (irreversible) compression. That means that the compressed image may not be "identical" from a medical point of view to the original one - the difference being the image quality.
In such cases DICOM requires the SOP Instance UID to be changed.

The overlay data should be a black/white bitmap, with one bit per pixel (equivalent to a DICOM image with Bits Allocated=1, Bits Stored=1, High Bit=0) and the same size as the main image.

Correct. Our CI system is a "nightly build" of the current development branch and will overwrite the old logs after a couple of days. The logs of the build that happened to be identical to 3.6.7 release are long gone.

Let's have a look: You are creating a DcmPixelData instance called "pixel_data" on the stack (for no obvious reason): DcmPixelData pixel_data = DcmPixelData(dcm_tag_pixel_data); Then you create a pointer that points to pixel_data: DcmElement* pixel_data_ptr = &pixel_data; Then you run findAndGetElem...

To add to what my colleagues already said, there is no such thing as a "16 bit JPEG", unless you consider the lossless JPEG encoding that nobody outside the medical world supports.
img2dcm expects an image using the Baseline lossy JPEG format (i.e. the JPEG format your camera or smart phone produces).

Yes, this is possible. libxml2, which is used by some DCMTK tools, can be compiled with character set conversion support based on GNU iconv or ICU. In that case linking against libxml2 causes the dependency on ICU.

DCMTK_PORTABLE_LINUX_BINARIES tries to create portable Linux binaries by linking all libraries statically, with the exception of glibc, which is linked dynamically. Glibc cannot be linked statically in a portable manner since the library will load additional shared objects at runtime, and this is li...

Yes, that is correct. Wildcard expansion works differently on Windows.

Yes, that is possible. All DCMTK tools can read the options from a command file instead of the command line. Just specify the name of the command line with a leading '@': findscu @commands.txt The file 'commands.txt' should be a simple text file that contains the command line options, separated by s...

The files in the libcharls folder are compiled into a separate library, named "libdcmtkcharls.a" on Linux, and "dcmtkcharls.lib" on Windows. You need to link against this library whenever you link against the static libdcmjpls library. DLLs automatically contain this dependency, static libraries do ...

artemmikheev wrote: ↑

Sun, 2023-02-26, 16:26

BTW, what happened to dcmsign.lib? The project for it is present in the source code, but when CMAKE generated the whole solution, the dcmsign project is missing from the solution.

You are compiling without OpenSSL support. In that case, the dcmsign library is empty.

My guess would be an incorrect presentation context ID used in the C-STORE-RQ message. Unfortunately, the dump output of our tools does not print this ID - perhaps something we should change.

Well, the reason why JPEG 2000 has never achieved widespread usage is the fact that the compression algorithm requires much more memory and time than, for example, classic JPEG. So in comparison to JPEG, JPEG 2000 will always be slow, and there is no way to avoid that. Of course there are faster and...

Well, a configuration of the printer that has different settings for different AETitles explains the problem...

There was no method of this name in DcmFileFormat in DCMTK 3.6.3. Is this perhaps something you (or a colleague) added by yourself?