Hello All,
Basically, we have been using dcmdump and dump2dcm to construct cine-loop from still images by extracting stills raw data files and binary appending them then construct the loop out of the final raw data file, it's been very successful and working fine till we got some CR images which our output loop is completely busted.
Here is the commands we use:
1# below is to extract raw data file and dcm header
dcmdump "d:\dcm\dx.1.2.410.200045.3.20170708.388.1.0.dcm" +L +W d:\medstreaming\demomode\dbRepository\2017\Jul08\2cc6c01e-4f50-4cbb-bcd0-853a8ab13de3 > "d:\dcm\dx.1.2.410.200045.3.20170708.388.1.0.txt"
2# below is to generate loop out of appended raw data files plus its header.
dump2dcm.exe +l 999999 d:\dcm\CR.1.3.6.1.4.1.27251.9.2.1.20170717130555.627803051.txt d:\dcm\CR.1.3.6.1.4.1.27251.9.2.1.20170717130555.627803051.dcm
The generated loop is busted and it looks like for a single frame is turned upside down.
This always happens after the second frame.
Please help!!!
Frame #1 (Good):
https://drive.google.com/file/d/0B9ZG2- ... NlVlU/view
Frame #2 (Good):
https://drive.google.com/file/d/0B9ZG2- ... dfalk/view
Frame #3 busted:
https://drive.google.com/file/d/0B9ZG2- ... VES2s/view
Issue with constructing cine loop from still images
Moderator: Moderator Team
-
- OFFIS DICOM Team
- Posts: 1444
- Joined: Tue, 2004-11-02, 17:22
- Location: Oldenburg, Germany
- Contact:
Re: Issue with constructing cine loop from still images
Perhaps your second frame image contains trailing "garbage" bytes at the end of the pixel data element, which would cause the effect you describe. You should perhaps compare the size of the PixelData element with the expected size (Rows * Columns * (BitsAllocated+7)/8). If the real size is larger, there's your problem.
Who is online
Users browsing this forum: Baidu [Spider] and 1 guest