Rendering of DICOM image failed with more than 4 volumes since version 12

Support
21

Right, but only for specific encodings - quoting from the same page as you linked above:

The value shall be appropriate to the compression Transfer Syntax used, if any, and shall be MONOCHROME2 or RGB for uncompressed or lossless compressed Transfer Syntaxes that do not have defined color space transformations, YBR_ICT or RGB for irreversible JPEG 2000 Transfer Syntaxes, YBR_RCT or RGB for reversible JPEG 2000 Transfer Syntaxes, and YBR_FULL_422 or RGB for JPEG lossy compressed Transfer Syntaxes.

What is the value of TransferSyntaxUID in your case?

22

The metadata does not contain the field (0002,0010) Transfer Syntax UID. Maybe it’s because of the multivolume sequence.

24

The link you shared does not work for me - it says the file is not available.

You would need to check that field in the original DICOM files - not in the node loaded into Slicer.

25

I know, I thought I’m sending it to Steve only. I have sent him a new link.

26
(0002,0010) UI TransferSyntaxUID 1.2.840.10008.1.2.4.90
27

That corresponds to lossless JPEG2000 compression (see 8.7.3.3.2 Compressed Bulk Data Media Types), so the value indeed appears to be valid. Maybe there is an issue with JPEG2000 support… If your goal is to load the data, I would probably try to convert DICOM to a sequence of volumes outside of Slicer, perhaps using dcm2niix - it might be easier to debug this way.

28

I will try it out, but it’s not important for me, as I see no issues in the app. I think it’s because of the handling of the multivolume sequence.

The errors are displayed in the console as soon I open the DICOM browser, without any selection. Before I thought it’s first after I select the Multiphase sequence, because of the 9 errors.

E: invalid value for ‘PhotometricInterpretation’ (YBR_RCT)