Ah, yes, that’s not right. It looks like this issue, recently reported also for Phillips data. If that’s the case, the fix is just waiting to merge as part of the pull request I linked to above. If you’re happy to share the data with me, I can take a look.
What I hadn’t realised was that this wasn’t an issue with 3.0.2 – I’ll look into what changed between the two versions to figure out what we did differently. I have a battery of test data that I use to verify that everything works as expected when I make changes to the DICOM handling, so I’m surprised I wouldn’t have picked this up if there had been such an obvious a regression… 