DICOM @ OFFIS

Hi, yes the OW/OB issues points at some unusual pixel data setup used. You can try the following to fix it: Use dcmcjpeg <input_file> <output_file> to create JPEG lossless, and then dcmdjpeg <output_file> <result_file> to decompress it again (thus not loosing quality). IIRC DCMTK will then use only ...

Hi, setting quality factor to 100 will not make JPEG Baseline lossless. Probably it's better to fix the source image. Also maybe the problem in the image is just disguised by applying JPEG Baseline transfer syntax, so you might store "garbage" to your PACS as well. Does dcmcjpeg gives some...

P.S: Well, I tried this and actually in dcmodify this does not work (loads fully into memory instead). Anyway, maybe Jörg or Marco know the best way to handle your problem.

Hi, unfortunately there is no such class in DCMTK. However, I think you could use DcmElement::createValueFromTempFile() in order to insert pixel data from a pixel data file stored on disk. This means you would write all your pixel data to disk in the format that it will later have inside the Pixel D...

Hi,

no, there is no specific IOD for this task. In DICOM there is so far: Encapsulated PDF, Enc. CDA, Enc. STL, Enc. OBJ and Enc. MTL. The only way to encapsulate a ZIP file would be private data, and/or using the Raw Data IOD.

Best regards,
Michael

As Jörg said, it is all "said" in dcm2pnm. By including diregist.h support of color images is automatically enabled. The API calls stay the same as without diregist.h.

You only have to follow the lines dcm2pnm::905 ff.

Hi Jingkun,

some general info how to insert private data can be found in our Howtos: https://support.dcmtk.org/redmine/proje ... rivateData

Best regards,
Michael

Hi,

Mh, hard to say, looks like a network problem or problem with dicomserver.co.uk. Probably you should check the server logs here: https://dicomserver.co.uk/logs/ when doing this request.

BR,
Michael

Yes, look into dcmnet/apps/getscu.cc how to do that.

BR, Michael

That means that movescu has never been connected to the PACS or (in your case if you could retrieve the images) that the server hung up the connection to movescu. Maybe you can see the reason using --debug on movescu but probably its an error in the server.

Hi, storescp per default only accepts uncompressed images. However, all images > 4 GB cannot be sent uncompressed. Try the following to also allow the sender to send in JPEG Lossless: --prefer-lossless If this does not work, try (not together, just one after another): --prefer-rle --prefer-mpeg2 --p...

Hi,

use --debug option on storescp which might show more details on what goes wrong.

BR,
Michael

The PACS tries to send images to 213.74.187.34:104, see the error message it returns in your first posting.

Hi, I guess your client is the one with IP 213.74.187? Did you start a storage server as pointed out above the code? and downloads them (Retrieve). For this last step, a separate Storage SCP like storescp is needed which actually receives the study images. If not, try to start it using storescp -v 1...

But storescp does not change the compression of the image?