Getting "non zero frame specified for single frame encapsulated pixel data" for file with > 1 frames about dicomparser HOT 9 CLOSED

According to the DICOM spec:

Decoders of encapsulated pixel data, whether Single Frame or Multi-Frame, need to accept both an empty Basic Offset Table (zero length) and a Basic Offset Table filled with 32 bit offset values.

and also:

If the object allows multi-frame images in the pixel data field, then each frame shall be encoded separately. Each fragment shall contain encoded data from a single-frame image.

from dicomparser.

Here is a POC fix: https://gist.github.com/cancan101/b888ed5d1163ec954966432c5aa505ae/revisions

from dicomparser.

Can you check 1.5.1 to see if this is now fixed? Thanks

from dicomparser.

After thinking about this further, I decided to deprecate the readEncapsulatedPixelData() because it does not work properly for multi-frame instances with empty basic offset table. I have added two new functions readEncapsulatedPixelDataFromFragments() and readEncapsulatedImageFrame() which should be used instead. The logic to deal with empty basic offset table instances is now the responsibility of the user of the library. I will be updating cornerstoneWADOImageLoader to use these new APIs and support your use case of empty basic offset table mutli-frame ultrasound. Feedback welcome!

from dicomparser.

Right now I am using:

const image = await cornerstone.loadAndCacheImage(
  `${this.imageId}?frame=${this.frameIndex}`
);
this.stack[this.frameIndex] = image;
cornerstone.displayImage(this.node, this.stack[this.frameIndex]);

and I am using the cornerstoneWADOImageLoader, so I guess it will just work for me?

from dicomparser.

Not until I update cornerstoneWADOImageLoader to use the new functions(). If you want to try it out, change decodeJPEGBaseline8bit.js line 38 to:
var encodedPixelData = dicomParser.readEncapsulatedPixelDataFromFragments(dataSet, dataSet.elements.x7fe00010, frame);

from dicomparser.

OK get latest dicomParser and cornerstoneWADOImageLoader and let me know how it goes

from dicomparser.

cancacn101 - did this resolve your issue?

from dicomparser.

Yes.

from dicomparser.