DICOM @ OFFIS

Look at this HowTo.

This is achieved by the function DCMSCU::addPresentationContext() and proposing the jpeg8 transfer syntax in one of the transfer syntaxes of the presentation context. Look at dcmsend as an example in the last DCMTK snapshot.

Hello, I tried to view the images with Sante DICOM Viewer the result was fine and as expected. I compared your output DICOM image with the output of the img2dcm and they are using the same photometric interpretation color model YBR_FULL_422. So, it seems the problem is in the Synedra viewer which do...

I have tested on my machine to compress a DICOM file and to use DcmElement::calcElementLength() to calculate the DICOM pixel data length before and after compression and worked fine with me. Your code portion does not show how did you use the function calcElementLength(). Make sure that you load all...

Can you show your tested source code in order to help you finding the problem?

Read this FAQ.

The uncompressed pixel data length can be manually computed as it equals rows * columns * bits allocated * number of frames * number of samples. Automatically, you can just call the function DcmElement::calcElementLength() to calculate the length of the pixel data DICOM attribute before and after co...

Hello, According to DICOM part 11, there are media storage application profiles which specify a selection of choices including the supported SOP class UID and the transfer syntax of the icon images. The default profile is the general purpose profile which does not support compression transfer sytaxe...

Hi, after you fill in the pixel data manually, you should call the function chooseRepresentation() to compress the pixel data and then call the function saveFile() to save the dataset with the compressed transfer syntax. So, you should call the line status = dataset->chooseRepresentation(EXS_JPEGPro...

After loading the dataset and calling the chooseRepresentation() function you don't need this line of code you can just save the dataset with the same chosen transfer syntax.

I don't see a problem in this portion of your code but a problem could happen if you do not release the store association used for receiving the DICOM instances before starting a new association request for forwarding those instances to a remote destination.

A workaround to solve this problem is to use the option --propose-jpeg8 in dcmqrscp and let movescu prefer it using the option --prefer-jpeg8 which will avoid the need to convert the file on the fly from the actual transfer syntax to accepted transfer syntax. This will let you send the study with co...

Look at this HowTo

The series description attribute is optional key if you query on the series level using the patient root Q/R information model (see DICOM Part 4 C.6.1.1.4). A C-FIND SCP may not support the existence of an optional key, or support its existence in the find response but without supporting matching it...

look at this post