[quote=“spiderman”]Thanks again, valley,
dcmtk works for the most part. I do have problems with some specific dicom formats, though (unable to render).
That’s quite unusual. Contact the developers on the support forum. They’re busy guys and you wont get a ton of feedback, but they’re still very helpful, given the complexity of the subject, and the fact that DCMTK is free. If there’s limitations in DCMTK they seem to be fairly aggressive about resolving them too.
In general, most rendering issues come down to not always picking the right part of the toolkit for the given problem.
I personally don’t use any of their rendering code, because I need a lot of access to raw pixel values. It’s essential to me to know the hounsfield values in CT images, for example. Typically radiologists don’t want to bothered with that kind of thing, and simply want a correctly scaled image suitable for viewing. Most of DCMTK is set-up primarily for the purpose of getting data in a standard form as quickly as possible. Fortunately, DCMTK does allow you to get pixel values in a modality corrected form, before display transform LUTs have been applied. This means you can pretty much get what ever you need out of the image, but don’t need to worry about inverse monochrome, or slope/intercept style issues.
Here’s a quick and dirty preview window that took a few minutes to put together - after I figured out how to compile the stuff [/quote]
I personally love the combination of JUCE and DCMTK. I’m pretty sure they’ll work well for you too.