Printable View
Hello,
I have one remaining image in my baseline (testing framework) I cannot
read :
[url]http://www.creatis.insa-lyon.fr/~malaterre/jpeg/gdcm-JPEG-LossLessThoravision.dcm[/url]
Could someone please let me know if they manage to read it ? If so
using which jpeg codec ? (the more information the better :)
Thanks
Mathieu
Hi Mathieu
I had no trouble reading this image using either the Stanford
PVRG codec or the Sun Java JAI JIIO codecs that both support
lossless JPEG.
This presupposes that the compressed bitstream is first
unencapsulated and defragmented, for which I used either
dctoraw from my dicom3tools or my Pixelmed Java DICOM
toolkit.
Osirix, which I seem to recall uses patched IJG, had no
trouble with it either.
Is it the encapsulation into multiple fragments (Items) that
is perhaps causing you trouble ?
David
Mathieu Malaterre wrote:[color=blue]
> Hello,
>
> I have one remaining image in my baseline (testing framework) I
> cannot read :
>
> [url]http://www.creatis.insa-lyon.fr/~malaterre/jpeg/gdcm-JPEG-LossLessThoravision.dcm[/url]
>
>
> Could someone please let me know if they manage to read it ? If so
> using which jpeg codec ? (the more information the better :)
>
> Thanks
> Mathieu[/color]
That's excellent news, I was a little worried this was due to some weird
bug in the jpeg compression. I guess I just need to figure out what is
going wrong in our side.
thanks again, that's all I needed
Mathieu
Ps: and yes osirix uses ijg (well at least source code is shipped with
ijg source)
David Clunie wrote:[color=blue]
> Hi Mathieu
>
> I had no trouble reading this image using either the Stanford
> PVRG codec or the Sun Java JAI JIIO codecs that both support
> lossless JPEG.
>
> This presupposes that the compressed bitstream is first
> unencapsulated and defragmented, for which I used either
> dctoraw from my dicom3tools or my Pixelmed Java DICOM
> toolkit.
>
> Osirix, which I seem to recall uses patched IJG, had no
> trouble with it either.
>
> Is it the encapsulation into multiple fragments (Items) that
> is perhaps causing you trouble ?
>
> David
>
> Mathieu Malaterre wrote:
>[color=green]
>> Hello,
>>
>> I have one remaining image in my baseline (testing framework) I
>> cannot read :
>>
>> [url]http://www.creatis.insa-lyon.fr/~malaterre/jpeg/gdcm-JPEG-LossLessThoravision.dcm[/url]
>>
>>
>> Could someone please let me know if they manage to read it ? If so
>> using which jpeg codec ? (the more information the better :)
>>
>> Thanks
>> Mathieu[/color]
>
>[/color]
Mathieu Malaterre <malatNOSP@Mfree.fr> wrote in message news:<G9Acd.8428$JS4.7330@twister.nyroc.rr.com>...[color=blue]
> That's excellent news, I was a little worried this was due to some weird
> bug in the jpeg compression. I guess I just need to figure out what is
> going wrong in our side.
>
> thanks again, that's all I needed
> Mathieu
> Ps: and yes osirix uses ijg (well at least source code is shipped with
> ijg source)
>
> David Clunie wrote:[/color]
Our DICOM Viewer could read it. This Viewer is base on OFFIS DCMTK.3.5.3.
It's a great DICOM Tool Kit. You could refer this toolkit.
pingyingtu wrote:[color=blue]
> Mathieu Malaterre <malatNOSP@Mfree.fr> wrote in message news:<G9Acd.8428$JS4.7330@twister.nyroc.rr.com>...
>[color=green]
>>That's excellent news, I was a little worried this was due to some weird
>>bug in the jpeg compression. I guess I just need to figure out what is
>>going wrong in our side.
>>
>>thanks again, that's all I needed
>>Mathieu
>>Ps: and yes osirix uses ijg (well at least source code is shipped with
>>ijg source)
>>
>>David Clunie wrote:[/color]
>
>
> Our DICOM Viewer could read it. This Viewer is base on OFFIS DCMTK.3.5.3.
> It's a great DICOM Tool Kit. You could refer this toolkit.[/color]
I believe you, the thing is that we wanted a lighter dicom parser (only
io implementation, no communication), and it needed to be swig wrap in
python... so we reinvented the wheel -for now the wheel is square :) -
Mathieu
Ps: also I didn't like the fact they copy/duplicate the ijg in the
source tree :P