Project

General

Profile

Actions

Bug #583

open

Fix support for JPIP transfer syntaxes

Added by Jörg Riesmeier almost 12 years ago. Updated 8 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Library and Apps
Target version:
Start date:
2013-11-29
Due date:
% Done:

50%

Estimated time:
Module:
Operating System:
Compiler:

Description

Although JPIP is currently not supported by the DCMTK, the current implementation of the associated transfer syntaxes results in strange (funny?) behavior. This is because the definitions in "dcxfer.cc" use EJE_NotEncapsulated for UID_JPIPReferencedTransferSyntax and UID_JPIPReferencedDeflateTransferSyntax, which is also used for the three uncompressed transfer syntaxes. See email from Mathieu Malaterre (sent on 2013-11-27).

It's probably a good idea to introduce a new enum value for JPIP-based transfer syntaxes and to add new methods to the DcmXfer class. Also the complete source code of the DCMTK should be checked for the use of isEncapsulated() and isNotEncapsulated(), which are currently used for a binary decision only.

Another issue with the deflated variant should also be fixed: "dcmconv +td jpip.dcm jpip_zip.dcm" should result in a file with the transfer syntax "JPIP Referenced Deflate" instead of "Deflated Explicit VR Little Endian".

Actions #1

Updated by Marco Eichelberg over 8 years ago

Update: the "funny" behaviour reported by Mathieu Malaterre is that storescu will read an image file in JPIP transfer syntax (which is lacking the pixel data and instead contains a pixel data URL) and will send it e.g. in Explicit VR Little Endian without any error message, producing an invalid DICOM object at the receiver side.

Actions #2

Updated by Marco Eichelberg over 8 years ago

  • Target version changed from 3.6.2 to 3.6.3
Actions #3

Updated by Marco Eichelberg almost 8 years ago

  • Target version deleted (3.6.3)
Actions #5

Updated by Michael Onken over 5 years ago

  • Priority changed from Normal to Low
Actions #6

Updated by Jörg Riesmeier over 1 year ago

  • Priority changed from Low to Normal
  • % Done changed from 0 to 50

The "invalid" conversion with dcmconv has been forbidden with commit 08ece95ad0.

The DcmXfer class has been largely revised and enhanced with commit 98727144c.

However, the "invalid" conversion during network transfer (e.g. using storescu) is still possible.

Actions #7

Updated by Jörg Riesmeier about 1 year ago

  • Target version set to 3.7.1+
Actions #8

Updated by Jörg Riesmeier 8 months ago

  • Target version changed from 3.7.1+ to 3.7.0
Actions

Also available in: Atom PDF