But as it seems OsiriX is the only really usefull one. In the meantime I have searched for other DICOM-Apps to test with those, too. The customised part is now implemented with some new “glue” code and it is this part that might require some fine tuning. In this case I cannot promise you a prompt resolution to the problem, especially considering that I am probably the only one in here without a job and who doesn’t receive any money for all this work that I am putting in.Ībout DCMTK, it’s not so much the version number that matters, as it is the way it is used: in OsiriX OS the source code is heavily customised (therefore “frozen”) and compiled into the project, in Osiri-LXIV it is a separate library module that will be easy to upgrade when updates of DCMTK become available.

If on the other hand OsiriX OS shows the same faulty behaviour as what you are reporting for Osiri-LXIV, we should probably consider it not a “bug” but a “new feature request”. If OsiriX OS works then we have a bug in Osiri-LXIV that should be relatively easy to fix.

Build OsiriX OS yourself with Xcode and test if the issue you are reporting appears there too.

This is the code base underlying Osiri-LXIV (even though we have surpassed it in some regards). Please download the open source 32-bit “OsiriX OS” project files from the Pixmeo site. Testing with OsiriX Lite 6.5 is of limited use in this case because it is not open source, but it is very useful as a reference when we want to implement new features for example by reverse engineering.

Osirix lite length tool not working