storescu.exe and mpeg4

All other questions regarding DCMTK

Moderator: Moderator Team

Post Reply
Message
Author
rullbandspelare
Posts: 18
Joined: Fri, 2005-12-09, 11:40

storescu.exe and mpeg4

#1 Post by rullbandspelare »

Hi!
I am trying to store a mpeg4 dicom file (ts: 1.2.840.10008.1.2.4.103) with :
>storescu.exe -d -xf storescu.cfg VIDEO_MPEG4 -aet DEMO -aec DEMO demo.com 104 mpegtest.dcm
this works with mpeg2 videos (1.2.840.10008.1.2.4.100)

I have created a storescu.cfg with a VIDEO_MPEG4 profile, just like I did with mpeg2.

Thanks for any help!

Here is the debug:

D: $dcmtk: storescu v3.6.0 2011-01-06 $
D:
I: checking input files ...
D: Request Parameters:
D: ====================== BEGIN A-ASSOCIATE-RQ =====================
D: Our Implementation Class UID: 1.2.276.0.7230010.3.0.3.6.0
D: Our Implementation Version Name: OFFIS_DCMTK_360
D: Their Implementation Class UID:
D: Their Implementation Version Name:
D: Application Context Name: 1.2.840.10008.3.1.1.1
D: Calling Application Name: DEMO
D: Called Application Name: DEMO
D: Responding Application Name: resp. AP Title
D: Our Max PDU Receive Size: 16384
D: Their Max PDU Receive Size: 0
D: Presentation Contexts:
D: Context ID: 1 (Proposed)
D: Abstract Syntax: =VideoEndoscopicImageStorage
D: Proposed SCP/SCU Role: Default
D: Proposed Transfer Syntax(es):
D: 1.2.840.10008.1.2.4.103
D: Context ID: 3 (Proposed)
D: Abstract Syntax: =VideoMicroscopicImageStorage
D: Proposed SCP/SCU Role: Default
D: Proposed Transfer Syntax(es):
D: 1.2.840.10008.1.2.4.103
D: Context ID: 5 (Proposed)
D: Abstract Syntax: =VideoPhotographicImageStorage
D: Proposed SCP/SCU Role: Default
D: Proposed Transfer Syntax(es):
D: 1.2.840.10008.1.2.4.103
D: Requested Extended Negotiation: none
D: Accepted Extended Negotiation: none
D: Requested User Identity Negotiation: none
D: User Identity Negotiation Response: none
D: ======================= END A-ASSOCIATE-RQ ======================
I: Requesting Association
D: Constructing Associate RQ PDU
D: PDU Type: Associate Accept, PDU Length: 249 + 6 bytes PDU header
D: 02 00 00 00 00 f9 00 01 00 00 64 6f 73 65 73 74
D: 61 74 20 20 20 20 20 20 20 20 56 49 45 57 4d 45
D: 44 20 20 20 20 20 20 20 20 20 00 00 00 00 00 00
D: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
D: 00 00 00 00 00 00 00 00 00 00 10 00 00 15 31 2e
D: 32 2e 38 34 30 2e 31 30 30 30 38 2e 33 2e 31 2e
D: 31 2e 31 21 00 00 1f 01 00 00 00 40 00 00 17 31
D: 2e 32 2e 38 34 30 2e 31 30 30 30 38 2e 31 2e 32
D: 2e 34 2e 31 30 33 21 00 00 1f 03 00 00 00 40 00
D: 00 17 31 2e 32 2e 38 34 30 2e 31 30 30 30 38 2e
D: 31 2e 32 2e 34 2e 31 30 33 21 00 00 1f 05 00 00
D: 00 40 00 00 17 31 2e 32 2e 38 34 30 2e 31 30 30
D: 30 38 2e 31 2e 32 2e 34 2e 31 30 33 50 00 00 2f
D: 51 00 00 04 00 00 3f e0 52 00 00 11 31 2e 32 2e
D: 34 30 2e 30 2e 31 33 2e 31 2e 31 2e 31 55 00 00
D: 0e 64 63 6d 34 63 68 65 2d 31 2e 34 2e 33 34
D: Parsing an A-ASSOCIATE PDU
D: Transport connection: TCP/IP, unencrypted.
D: Association Parameters Negotiated:
D: ====================== BEGIN A-ASSOCIATE-AC =====================
D: Our Implementation Class UID: 1.2.276.0.7230010.3.0.3.6.0
D: Our Implementation Version Name: OFFIS_DCMTK_360
D: Their Implementation Class UID: 1.2.40.0.13.1.1.1
D: Their Implementation Version Name: dcm4che-1.4.34
D: Application Context Name: 1.2.840.10008.3.1.1.1
D: Calling Application Name: DEMO
D: Called Application Name: DEMO
D: Responding Application Name: DEMO
D: Our Max PDU Receive Size: 16384
D: Their Max PDU Receive Size: 16352
D: Presentation Contexts:
D: Context ID: 1 (Accepted)
D: Abstract Syntax: =VideoEndoscopicImageStorage
D: Proposed SCP/SCU Role: Default
D: Accepted SCP/SCU Role: Default
D: Accepted Transfer Syntax: 1.2.840.10008.1.2.4.103
D: Context ID: 3 (Accepted)
D: Abstract Syntax: =VideoMicroscopicImageStorage
D: Proposed SCP/SCU Role: Default
D: Accepted SCP/SCU Role: Default
D: Accepted Transfer Syntax: 1.2.840.10008.1.2.4.103
D: Context ID: 5 (Accepted)
D: Abstract Syntax: =VideoPhotographicImageStorage
D: Proposed SCP/SCU Role: Default
D: Accepted SCP/SCU Role: Default
D: Accepted Transfer Syntax: 1.2.840.10008.1.2.4.103
D: Requested Extended Negotiation: none
D: Accepted Extended Negotiation: none
D: Requested User Identity Negotiation: none
D: User Identity Negotiation Response: none
D: ======================= END A-ASSOCIATE-AC ======================
I: Association Accepted (Max Send PDV: 16340)
I: Sending file: mpegtest.dcm.bak
D: DcmItem::checkTransferSyntax() TransferSyntax="Little Endian Explicit"
D: DcmItem::checkTransferSyntax() TransferSyntax="Little Endian Explicit"
I: Transfer Syntax: LittleEndianExplicit ->
I: Sending Store Request: MsgID 1, (VVp)
D: ===================== OUTGOING DIMSE MESSAGE ====================
D: Message Type : C-STORE RQ
D: Message ID : 1
D: Affected SOP Class UID : VideoPhotographicImageStorage
D: Affected SOP Instance UID : 1.2.40.0.13.1.10.105.2.67.26872956.20160614114610923.3
D: Data Set : present
D: Priority : low
D: ======================= END DIMSE MESSAGE =======================
E: Store Failed, file: mpegtest.dcm:
E: 0006:020d DIMSE Failed to receive message
E: 0006:0212 DIMSE Unsupported transfer syntax: 1.2.840.10008.1.2.4.103
E: Store SCU Failed: 0006:020d DIMSE Failed to receive message
E: 0006:0212 DIMSE Unsupported transfer syntax: 1.2.840.10008.1.2.4.103
I: Aborting Association

J. Riesmeier
DCMTK Developer
Posts: 2504
Joined: Tue, 2011-05-03, 14:38
Location: Oldenburg, Germany
Contact:

Re: storescu.exe and mpeg4

#2 Post by J. Riesmeier »

$dcmtk: storescu v3.6.0 2011-01-06 $
It should be obvious that this old version of storescu does not (yet) support the newer transfer syntaxes like 1.2.840.10008.1.2.4.103. See error message at the end of the log output:

Code: Select all

E: 0006:0212 DIMSE Unsupported transfer syntax: 1.2.840.10008.1.2.4.103
Using a recent DCMTK snapshot should solve your problem. Also, I would propose to use dcmsend instead of of storescu since it does not require a (modified) configuration file.

rullbandspelare
Posts: 18
Joined: Fri, 2005-12-09, 11:40

Re: storescu.exe and mpeg4

#3 Post by rullbandspelare »

Thanks! Is working with latest toolkit.
BUT... I do not understand the Warnings I get when sending the object.
"W: DcmItem: Invalid Element (0000,0000) found in data set"
How can I get rid of them?


U:\dicom>dcmsend +v -d -aet SENDSCU -aec SENDSCP 10.10.10.34 104 ..\out\191212121212_20160628093314\mpg\test.dcm
D: $dcmtk: dcmsend v3.6.1 2016-02-16 $
D:
I: checking input files ...
D: adding DICOM file '..\out\191212121212_20160628093314\mpg\test.dcm'
D: getting SOP Class UID, SOP Instance UID and Transfer Syntax UID from DICOM file
D: DcmMetaInfo::checkAndReadPreamble() TransferSyntax="Little Endian Explicit"
D: trying to get SOP Class UID, SOP Instance UID and Transfer Syntax UID from meta-header
D: successfully added SOP instance 1.2.40.0.13.1.10.105.2.67.26872956.20160628093350833.3 to the transfer list
D: in total, there are 1 SOP instances to be sent, 0 invalid files are ignored
D: multiple associations allowed (option --multi-associations used)
D: preparing presentation context for SOP Class / Transfer Syntax: VideoPhotographicImageStorage / MPEG-4 AVC/H.264 BD-compatible High Profile / Level 4.1
D: transfer syntax uses a lossy compression but we are not allowed to decompress it, so we are not proposing any uncompressed transfer syntax
D: added new presentation context with ID 1
D: -----------------------------------------------------------------
D: starting association #1
I: initializing network ...
D: Configured a total of 1 presentation contexts for SCU
I: negotiating network association ...
I: Request Parameters:
I: ====================== BEGIN A-ASSOCIATE-RQ =====================
I: Our Implementation Class UID: 1.2.276.0.7230010.3.0.3.6.1
I: Our Implementation Version Name: OFFIS_DCMTK_361
I: Their Implementation Class UID:
I: Their Implementation Version Name:
I: Application Context Name: 1.2.840.10008.3.1.1.1
I: Calling Application Name: SENDSCU
I: Called Application Name: SENDSCP
I: Responding Application Name: resp. AP Title
I: Our Max PDU Receive Size: 16384
I: Their Max PDU Receive Size: 0
I: Presentation Contexts:
I: Context ID: 1 (Proposed)
I: Abstract Syntax: =VideoPhotographicImageStorage
I: Proposed SCP/SCU Role: Default
I: Proposed Transfer Syntax(es):
I: =MPEG4BDcompatibleHighProfile/Level4.1
I: Requested Extended Negotiation: none
I: Accepted Extended Negotiation: none
I: Requested User Identity Negotiation: none
I: User Identity Negotiation Response: none
I: ======================= END A-ASSOCIATE-RQ ======================
I: Requesting Association
D: setting network send timeout to 60 seconds
D: setting network receive timeout to 60 seconds
D: Constructing Associate RQ PDU
D: PDU Type: Associate Accept, PDU Length: 184 + 6 bytes PDU header
D: 02 00 00 00 00 b8 00 01 00 00 6c 75 6c 61 72 6b
D: 69 76 46 49 52 20 20 20 20 20 56 49 45 57 4d 45
D: 44 20 20 20 20 20 20 20 20 20 00 00 00 00 00 00
D: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
D: 00 00 00 00 00 00 00 00 00 00 10 00 00 15 31 2e
D: 32 2e 38 34 30 2e 31 30 30 30 38 2e 33 2e 31 2e
D: 31 2e 31 21 00 00 1f 01 00 00 00 40 00 00 17 31
D: 2e 32 2e 38 34 30 2e 31 30 30 30 38 2e 31 2e 32
D: 2e 34 2e 31 30 33 50 00 00 34 51 00 00 04 00 00
D: 80 00 52 00 00 14 31 2e 32 2e 38 34 30 2e 31 31
D: 33 37 30 34 2e 37 2e 30 2e 32 55 00 00 10 44 43
D: 4d 20 50 72 6f 2d 31 32 2e 31 2e 35 2e 30
D: Parsing an A-ASSOCIATE PDU
I: Association Parameters Negotiated:
I: ====================== BEGIN A-ASSOCIATE-AC =====================
I: Our Implementation Class UID: 1.2.276.0.7230010.3.0.3.6.1
I: Our Implementation Version Name: OFFIS_DCMTK_361
I: Their Implementation Class UID: 1.2.840.113704.7.0.2
I: Their Implementation Version Name: DCM Pro-12.1.5.0
I: Application Context Name: 1.2.840.10008.3.1.1.1
I: Calling Application Name: SENDSCU
I: Called Application Name: SENDSCP
I: Responding Application Name: SENDSCP
I: Our Max PDU Receive Size: 16384
I: Their Max PDU Receive Size: 32768
I: Presentation Contexts:
I: Context ID: 1 (Accepted)
I: Abstract Syntax: =VideoPhotographicImageStorage
I: Proposed SCP/SCU Role: Default
I: Accepted SCP/SCU Role: Default
I: Accepted Transfer Syntax: =MPEG4BDcompatibleHighProfile/Level4.1
I: Requested Extended Negotiation: none
I: Accepted Extended Negotiation: none
I: Requested User Identity Negotiation: none
I: User Identity Negotiation Response: none
I: ======================= END A-ASSOCIATE-AC ======================
I: Association Accepted (Max Send PDV: 32756)
I: sending SOP instances ...
D: sending SOP instance from file: ..\out\191212121212_20160628093314\mpg\test.dcm
D: DcmMetaInfo::checkAndReadPreamble() TransferSyntax="Little Endian Explicit"
D: DcmDataset::read() TransferSyntax="MPEG-4 AVC/H.264 BD-compatible High Profile / Level 4.1"
D: checking whether SOP Class UID and SOP Instance UID in dataset are consistent with transfer list
D: getting SOP Class UID, SOP Instance UID and Transfer Syntax UID from DICOM dataset
I: Sending C-STORE Request
D: ===================== OUTGOING DIMSE MESSAGE ====================
D: Message Type : C-STORE RQ
D: Presentation Context ID : 1
D: Message ID : 1
D: Affected SOP Class UID : VideoPhotographicImageStorage
D: Affected SOP Instance UID : 1.2.40.0.13.1.10.105.2.67.26872956.20160628093350833.3
D: Data Set : present
D: Priority : low
D: ======================= END DIMSE MESSAGE =======================
D: DcmDataset::read() TransferSyntax="Little Endian Implicit"
W: DcmItem: Invalid Element (0000,0000) found in data set
W: DcmItem: Invalid Element (0000,0002) found in data set
W: DcmItem: Invalid Element (0000,0100) found in data set
W: DcmItem: Invalid Element (0000,0120) found in data set
W: DcmItem: Invalid Element (0000,0800) found in data set
W: DcmItem: Invalid Element (0000,0900) found in data set
W: DcmItem: Invalid Element (0000,1000) found in data set
I: Received C-STORE Response
D: ===================== INCOMING DIMSE MESSAGE ====================
D: Message Type : C-STORE RSP
D: Presentation Context ID : 1
D: Message ID Being Responded To : 1
D: Affected SOP Class UID : VideoPhotographicImageStorage
D: Affected SOP Instance UID : 1.2.40.0.13.1.10.105.2.67.26872956.20160628093350833.3
D: Data Set : none
D: DIMSE Status : 0x0000: Success
D: ======================= END DIMSE MESSAGE =======================
I: Releasing Association
D: Cleaning up internal association and network structures
I:
I: Status Summary
I: --------------
I: Number of associations : 1
I: Number of pres. contexts : 1
I: Number of SOP instances : 1
I: - sent to the peer : 1
I: * with status SUCCESS : 1

J. Riesmeier
DCMTK Developer
Posts: 2504
Joined: Tue, 2011-05-03, 14:38
Location: Oldenburg, Germany
Contact:

Re: storescu.exe and mpeg4

#4 Post by J. Riesmeier »

"W: DcmItem: Invalid Element (0000,0000) found in data set"
This is a well-known issue in the most recent snapshot (February 2016), which has been fixed with this commit.

rbrakes
Posts: 4
Joined: Fri, 2006-03-03, 18:04

Invalid Element (0000,0000), was Re: storescu.exe and mpeg4

#5 Post by rbrakes »

Yeah, I'm seeing something similar with the latest snapshot. (See below).

Any idea when we can expect an updated snapshot? Especially with DICOM 2016c recently released?

tango.bruce> echoscu -aec MEV_TDS -v 192.168.250.168 3005
I: Requesting Association
I: Association Accepted (Max Send PDV: 16372)
I: Sending Echo Request (MsgID 1)
W: DcmItem: Invalid Element (0000,0000) found in data set
W: DcmItem: Invalid Element (0000,0002) found in data set
W: DcmItem: Invalid Element (0000,0100) found in data set
W: DcmItem: Invalid Element (0000,0120) found in data set
W: DcmItem: Invalid Element (0000,0800) found in data set
W: DcmItem: Invalid Element (0000,0900) found in data set
I: Received Echo Response (Success)
I: Releasing Association
tango.bruce>

J. Riesmeier
DCMTK Developer
Posts: 2504
Joined: Tue, 2011-05-03, 14:38
Location: Oldenburg, Germany
Contact:

Re: storescu.exe and mpeg4

#6 Post by J. Riesmeier »

Are you sure that you've downloaded the latest snapshot?
Any idea when we can expect an updated snapshot? Especially with DICOM 2016c recently released?
This has been released end of June and it also contains the usual support for DICOM 2016c. See: https://blog.jriesmeier.com/2016/06/16t ... rsion-361/

rbrakes
Posts: 4
Joined: Fri, 2006-03-03, 18:04

Re: storescu.exe and mpeg4

#7 Post by rbrakes »

Just got it! Thanks.

Post Reply

Who is online

Users browsing this forum: Bing [Bot], Google [Bot] and 1 guest