Search found 1292 matches

by Marco Eichelberg
Tue, 2021-04-06, 15:30
Forum: DCMPRINT
Topic: DCMTK + DCMPRINT : LNK2019 errors
Replies: 12
Views: 510

Re: DCMTK + DCMPRINT : LNK2019 errors

Possible. You might want to check the command line options used to build DCMTK and compare these with the settings of your own project. There are some command line options that are mutually incompatible, such as /Gd, /Gr, /Gv, /Gz , which change the calling conventions (e.g. __thiscall, __fastcall, ...
by Marco Eichelberg
Tue, 2021-04-06, 14:59
Forum: DCMPRINT
Topic: DCMTK + DCMPRINT : LNK2019 errors
Replies: 12
Views: 510

Re: DCMTK + DCMPRINT : LNK2019 errors

Then it's probably the link order. The libraries needed for the print client should be specified in this order:

Code: Select all

dcmprint.lib
dcmimage.lib
dcmimgle.lib
dcmnet.lib
dcmtls.lib
dcmdata.lib
oflog.lib
ofstd.lib
by Marco Eichelberg
Tue, 2021-04-06, 14:52
Forum: DCMPRINT
Topic: How to pass image layout to Print SCP server
Replies: 1
Views: 234

Re: How to pass image layout to Print SCP server

In order to do this with the tcpprt command line tool, you first need to change the configuration file (tcpprt.cfg). As a starting point, you can change this line, which is below the [[AUTO-1]] headline: ImageDisplayFormat = STANDARD\1,1 into ImageDisplayFormat = STANDARD\2,2 and then run tcpprt wit...
by Marco Eichelberg
Tue, 2021-04-06, 14:45
Forum: DCMPRINT
Topic: Does Print SCP support 12/16 Bit allocated dicom images
Replies: 1
Views: 205

Re: Does Print SCP support 12/16 Bit allocated dicom images

Sorry for the late reply - apparently I missed this forum for quite some time. The print server in the DCMPRINT module (tcpsrv) does support both 8 bit images (BitsAllocated = 8, BitsStored = 8) and 12 bit images (BitsAllocated = 16, BitsStored = 12); these are the two image types defined in DICOM G...
by Marco Eichelberg
Tue, 2021-04-06, 14:38
Forum: DCMPRINT
Topic: DCMTK + DCMPRINT : LNK2019 errors
Replies: 12
Views: 510

Re: DCMTK + DCMPRINT : LNK2019 errors

The error message indeed indicates that the linker cannot resolve some symbols, either because a library is missing, or because the link order is incorrect. The symbols reported in the error message are present in the ofstd library (ofstd.lib), and I cannot see that library in the list of library de...
by Marco Eichelberg
Sun, 2021-03-28, 16:05
Forum: DCMTK - General
Topic: My client-side DCMTK TLS code broke after upgrading to 3.6.4.
Replies: 2
Views: 273

Re: My client-side DCMTK TLS code broke after upgrading to 3.6.4.

The TLS error message indicates that during the TLS handshake no signature algorithm could successfully be negotiated. In order to troubleshoot this issue in detail, you should capture a detailed log of the TLS handshake. You can do this for example using the "tshark" tool, which is part of the Wire...
by Marco Eichelberg
Sun, 2021-03-28, 15:56
Forum: DCMTK - General
Topic: Convert 12/16 bit dicom images to 8 bit dicom images
Replies: 1
Views: 292

Re: Convert 12/16 bit dicom images to 8 bit dicom images

First of all, DCMTK 3.6.0 is really ancient now, being released in 2011, i.e. 10 years ago, and I would encourage you to migrate to a newer release. One way of converting 12/16 bit DICOM images to 8 bit DICOM would be to apply a (lossless) JPEG compression with dcmcjpeg, followed by a decompression....
by Marco Eichelberg
Fri, 2021-03-05, 10:09
Forum: DCMPRINT
Topic: Print SCU (tcpprt) using command line arguments without config(tcpprt.cfg) file
Replies: 1
Views: 212

Re: Print SCU (tcpprt) using command line arguments without config(tcpprt.cfg) file

In brief, you cannot. While the API of the underlying library of course allows the developer to set these attributes without reading a configuration file, the command line print client is designed to read configuration data from file (that is, unless you use the text-based interactive user interface...
by Marco Eichelberg
Mon, 2021-03-01, 09:49
Forum: DCMTK - Installation
Topic: Precompiled dcmtk-tls raises glibc error on Ubuntu (different versions)
Replies: 6
Views: 486

Re: Precompiled dcmtk-tls raises glibc error on Ubuntu (different versions)

This is just a guess, but I believe that even statically linked binaries on Linux will load some glibc code from shared objects (I think the linker warns about this). The name of the error location (dl-call-libc-early-init.c) seems to indicate that the error is related to the loading of libc code fr...
by Marco Eichelberg
Tue, 2021-02-23, 09:09
Forum: DCMTK - General
Topic: dcm image can not be open while dcmdump works well
Replies: 1
Views: 240

Re: dcm image can not be open while dcmdump works well

This is not a valid DICOM image. In every DICOM image, the image pixel data is stored in attribute (7FE0,0010) PixelData, independent of the encoding (transfer syntax) used. As you can see, in this file there is no attribute (7FE0,0010), thus it's not valid DICOM. What the vendor has done here is th...
by Marco Eichelberg
Fri, 2021-02-05, 19:51
Forum: DCMTK - General
Topic: DICOMDIR created using dcmmkdir not working to open with EchoPAC
Replies: 1
Views: 361

Re: DICOMDIR created using dcmmkdir not working to open with EchoPAC

The DICOM directory file MUST be named "DICOMDIR" and must be located in the root directory of the storage media. If the file on the USB stick is named "TESTDIR", then the stick will not be recognized as a DICOM storage medium.
by Marco Eichelberg
Fri, 2021-02-05, 16:36
Forum: DCMTK - General
Topic: bug in DcmFileFormat::writeJson
Replies: 2
Views: 299

Re: bug in DcmFileFormat::writeJson

The bug fix has been committed now in commit #d03f56b1e and should appear in the public git in a couple of days. Here's the diff log: --- a/dcmdata/libsrc/dcfilefo.cc +++ b/dcmdata/libsrc/dcfilefo.cc @@ -245,10 +245,10 @@ OFCondition DcmFileFormat::writeJson(STD_NAMESPACE ostream &out, if (metinf) {...
by Marco Eichelberg
Mon, 2021-02-01, 14:00
Forum: DCMTK - General
Topic: N-Action module - affected sop instance value issue
Replies: 1
Views: 319

Re: N-Action module - affected sop instance value issue

Sorry for the late reply. ".840.10008.1.20.1.1" is not a valid UID, and, presuming that you refer to Storage Commitment, "1.2.840.10008.1.20.1.1" would be the correct SOP Instance UID. I would suggest that you take a network capture with Wireshark and check whether the incorrect UID is sent by the S...
by Marco Eichelberg
Mon, 2021-02-01, 13:47
Forum: DCMTK - General
Topic: bug in DcmFileFormat::writeJson
Replies: 2
Views: 299

Re: bug in DcmFileFormat::writeJson

Thank you for the bug report. I can confirm that I was able to reproduce it. I have no idea how this managed to slip through - I am fairly certain that I had fixed that error before.
by Marco Eichelberg
Mon, 2021-02-01, 13:45
Forum: DCMTK - General
Topic: Not able to load a single DICOM file
Replies: 10
Views: 651

Re: Not able to load a single DICOM file

The problem here is that the file is not a valid DICOM file - the encoding of the sequences is not correct. You can use the following call to fix the file: dcmconv --replace-wrong-delim --ignore-parse-errors <infile> <outfile> If you want to include that functionality into your own code,dcmconv maps...