Rocksolid Light

Welcome to RetroBBS

mail  files  register  newsreader  groups  login

Message-ID:  

Science and religion are in full accord but science and faith are in complete discord.

devel / comp.protocols.dicom / Re: Zessis OPT files(J2K) can not decoding.....

SubjectAuthor
* Re: Zessis OPT files(J2K) can not decoding.....Dean
`- Re: Zessis OPT files(J2K) can not decoding.....kenz bensmaine

1
Re: Zessis OPT files(J2K) can not decoding.....

<80d2935b-b5a2-4001-921e-c76a06b3523fn@googlegroups.com>

  copy mid

https://www.rocksolidbbs.com/devel/article-flat.php?id=384&group=comp.protocols.dicom#384

  copy link   Newsgroups: comp.protocols.dicom
X-Received: by 2002:a05:620a:56b:b0:62c:eff4:fe8d with SMTP id p11-20020a05620a056b00b0062ceff4fe8dmr13761575qkp.459.1647905721987;
Mon, 21 Mar 2022 16:35:21 -0700 (PDT)
X-Received: by 2002:a05:620a:e18:b0:67d:7fcb:6244 with SMTP id
y24-20020a05620a0e1800b0067d7fcb6244mr14216436qkm.42.1647905721812; Mon, 21
Mar 2022 16:35:21 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.protocols.dicom
Date: Mon, 21 Mar 2022 16:35:21 -0700 (PDT)
In-Reply-To: <39068f6b-327a-4000-8c42-c0e834fa77f9@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=203.10.55.12; posting-account=iMP6ewoAAACuBC7kVxG8Zzb9qkyPpf0B
NNTP-Posting-Host: 203.10.55.12
References: <7eb52ec6-1be3-491a-aabe-5024419fe552@googlegroups.com>
<7f8fb70e-fc75-423c-9209-df7c8beeffd7@googlegroups.com> <39068f6b-327a-4000-8c42-c0e834fa77f9@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <80d2935b-b5a2-4001-921e-c76a06b3523fn@googlegroups.com>
Subject: Re: Zessis OPT files(J2K) can not decoding.....
From: scaram@gmail.com (Dean)
Injection-Date: Mon, 21 Mar 2022 23:35:21 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 35
 by: Dean - Mon, 21 Mar 2022 23:35 UTC

On Thursday, February 15, 2018 at 8:39:16 PM UTC+11, anoo...@gmail.com wrote:
> On Monday, October 26, 2015 at 3:05:16 PM UTC+5:30, Mathieu Malaterre wrote:
> > On Monday, October 26, 2015 at 7:56:42 AM UTC+1, summy00 wrote:
> > > it's J2K encoded, but I can't find any way to decode it, anyone can help me?
> > >
> > > files download: http://1drv.ms/1MelGwX
> >
> > I've only looked at: 5MRMJPPWOZ1M3NZ0MGH6RBUKSD91663S27IOLS4X2ZU.EX.DCM
> >
> > I can see the Pixel Data Fragments ends with FF D9 (EOI/EOC) which suspiciously looks like a JPEG encoded stream. However since there is no header, there is no way to know if this is JPEG (ITU 81), JPEG-LS, JPEG-XR and/or JPEG 2000. Technically since the DICOM header states that the encoding is irreversible it will be nearly impossible to craft a JPEG 2000 header before the (potential) SOD marker, since there so many possible parameters.
> >
> > Please check with your vendor for a proper exporting tool. And or get the DICOM conformance statement. But really the DICOM files contains so many errors (private attribute without private creators...) that it does not make sense to support those files at this point.
> >
> > I know Zeiss offer decent documentation for there private file formats, so you should really consider this path if you want to inspect your data.
> >
> > 2cts
> > -M
> I am facing the similar problem. Please help me to read .EX.DCM file.

For anyone else stumbling across this issue, I've figured out how to unscramble the obfuscated pixel data here: https://github.com/pydicom/pydicom/discussions/1618

Re: Zessis OPT files(J2K) can not decoding.....

<c0d428cc-d61a-405c-9359-e20a84afd3b4n@googlegroups.com>

  copy mid

https://www.rocksolidbbs.com/devel/article-flat.php?id=386&group=comp.protocols.dicom#386

  copy link   Newsgroups: comp.protocols.dicom
X-Received: by 2002:a05:622a:c3:b0:2e3:4bd0:16c2 with SMTP id p3-20020a05622a00c300b002e34bd016c2mr7302437qtw.575.1648232001746;
Fri, 25 Mar 2022 11:13:21 -0700 (PDT)
X-Received: by 2002:ac8:7fc1:0:b0:2e1:e519:93d5 with SMTP id
b1-20020ac87fc1000000b002e1e51993d5mr10691623qtk.508.1648232001478; Fri, 25
Mar 2022 11:13:21 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.protocols.dicom
Date: Fri, 25 Mar 2022 11:13:21 -0700 (PDT)
In-Reply-To: <80d2935b-b5a2-4001-921e-c76a06b3523fn@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=2a01:cb1c:56c:af00:739:3a52:8dbe:f177;
posting-account=s6pTKgoAAACIa0TOOlsSkmTV38hmr2Eo
NNTP-Posting-Host: 2a01:cb1c:56c:af00:739:3a52:8dbe:f177
References: <7eb52ec6-1be3-491a-aabe-5024419fe552@googlegroups.com>
<7f8fb70e-fc75-423c-9209-df7c8beeffd7@googlegroups.com> <39068f6b-327a-4000-8c42-c0e834fa77f9@googlegroups.com>
<80d2935b-b5a2-4001-921e-c76a06b3523fn@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <c0d428cc-d61a-405c-9359-e20a84afd3b4n@googlegroups.com>
Subject: Re: Zessis OPT files(J2K) can not decoding.....
From: kenz.bensmaine@gmail.com (kenz bensmaine)
Injection-Date: Fri, 25 Mar 2022 18:13:21 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 39
 by: kenz bensmaine - Fri, 25 Mar 2022 18:13 UTC

Le mardi 22 mars 2022 à 00:35:23 UTC+1, Dean a écrit :
> On Thursday, February 15, 2018 at 8:39:16 PM UTC+11, anoo...@gmail.com wrote:
> > On Monday, October 26, 2015 at 3:05:16 PM UTC+5:30, Mathieu Malaterre wrote:
> > > On Monday, October 26, 2015 at 7:56:42 AM UTC+1, summy00 wrote:
> > > > it's J2K encoded, but I can't find any way to decode it, anyone can help me?
> > > >
> > > > files download: http://1drv.ms/1MelGwX
> > >
> > > I've only looked at: 5MRMJPPWOZ1M3NZ0MGH6RBUKSD91663S27IOLS4X2ZU.EX.DCM
> > >
> > > I can see the Pixel Data Fragments ends with FF D9 (EOI/EOC) which suspiciously looks like a JPEG encoded stream. However since there is no header, there is no way to know if this is JPEG (ITU 81), JPEG-LS, JPEG-XR and/or JPEG 2000. Technically since the DICOM header states that the encoding is irreversible it will be nearly impossible to craft a JPEG 2000 header before the (potential) SOD marker, since there so many possible parameters.
> > >
> > > Please check with your vendor for a proper exporting tool. And or get the DICOM conformance statement. But really the DICOM files contains so many errors (private attribute without private creators...) that it does not make sense to support those files at this point.
> > >
> > > I know Zeiss offer decent documentation for there private file formats, so you should really consider this path if you want to inspect your data..
> > >
> > > 2cts
> > > -M
> > I am facing the similar problem. Please help me to read .EX.DCM file.
> For anyone else stumbling across this issue, I've figured out how to unscramble the obfuscated pixel data here: https://github.com/pydicom/pydicom/discussions/1618

Wow thanks for the incredible link!
Very helpful!
Thanks again

1
server_pubkey.txt

rocksolid light 0.9.81
clearnet tor