Rocksolid Light

Welcome to RetroBBS

mail  files  register  newsreader  groups  login

Message-ID:  

Pray to God, but keep rowing to shore. -- Russian Proverb

devel / comp.protocols.dicom / Re: 1.2.840.10008.1.2.4.51 with 8 bit YBR_FULL_422 color images

SubjectAuthor
* 1.2.840.10008.1.2.4.51 with 8 bit YBR_FULL_422 color imageskuldip...@gmail.com
`- Re: 1.2.840.10008.1.2.4.51 with 8 bit YBR_FULL_422 color imageskuldip...@gmail.com

1
1.2.840.10008.1.2.4.51 with 8 bit YBR_FULL_422 color images

<fc35846b-378f-480f-98b8-cfdc2bdbb21dn@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: comp.protocols.dicom
X-Received: by 2002:ac8:5510:: with SMTP id j16mr3129862qtq.664.1639760040208;
Fri, 17 Dec 2021 08:54:00 -0800 (PST)
X-Received: by 2002:a05:6214:246d:: with SMTP id im13mr3139258qvb.44.1639760039870;
Fri, 17 Dec 2021 08:53:59 -0800 (PST)
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, 17 Dec 2021 08:53:59 -0800 (PST)
Injection-Info: google-groups.googlegroups.com; posting-host=165.225.59.63; posting-account=5rhYWAoAAAAuJKgYx9xP_f9UnoUMD6Qe
NNTP-Posting-Host: 165.225.59.63
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <fc35846b-378f-480f-98b8-cfdc2bdbb21dn@googlegroups.com>
Subject: 1.2.840.10008.1.2.4.51 with 8 bit YBR_FULL_422 color images
From: kuldiprindani@gmail.com (kuldip...@gmail.com)
Injection-Date: Fri, 17 Dec 2021 16:54:00 +0000
Content-Type: text/plain; charset="UTF-8"
Lines: 14
 by: kuldip...@gmail.com - Fri, 17 Dec 2021 16:53 UTC

We have a question whether DICOM transfer syntax 1.2.840.10008.1.2.4.51 ( Lossy 12 bit image compression) - can it be also be used for decompressing 8 bit YBR_FULL_422 color images?

We have this question (& confusion) because of below weird findings from test

Some of 8bit YBR_FULL_422 color images are grayed out after passing thru 1.2.840.10008.1.2.4.50 (JPEG baseline 8bit) de-compressor but they are displayed correctly when using 1.2.840.10008.1.2.4.51 (12 Bit Image Compression).
but within same study images with same properties 8bit YBR_FULL_422 are displayed fine after passing thru 1.2.840.10008.1.2.4.50 (JPEG baseline 8bit) de-compressor.

overall we found during test 1.2.840.10008.1.2.4.51 (12 bit) works always.

I know immediate comment here would you to rely on transfer syntax of image but in one of our legacy product we are forced to rely on a private tag to determine image compression.

I'm looking for comment from JPEG de-compression point of view if 1.2.840.10008.1.2.4.51 (12 bit) can take care of 8 bit & 12 bit both.

Thanks.

Re: 1.2.840.10008.1.2.4.51 with 8 bit YBR_FULL_422 color images

<07891ed3-e386-418f-a26a-e73b0d794d4en@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: comp.protocols.dicom
X-Received: by 2002:a05:6214:2522:: with SMTP id gg2mr4511537qvb.127.1639778704842;
Fri, 17 Dec 2021 14:05:04 -0800 (PST)
X-Received: by 2002:ac8:7d87:: with SMTP id c7mr4321396qtd.501.1639778704527;
Fri, 17 Dec 2021 14:05:04 -0800 (PST)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!border1.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, 17 Dec 2021 14:05:04 -0800 (PST)
In-Reply-To: <fc35846b-378f-480f-98b8-cfdc2bdbb21dn@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=165.225.59.63; posting-account=5rhYWAoAAAAuJKgYx9xP_f9UnoUMD6Qe
NNTP-Posting-Host: 165.225.59.63
References: <fc35846b-378f-480f-98b8-cfdc2bdbb21dn@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <07891ed3-e386-418f-a26a-e73b0d794d4en@googlegroups.com>
Subject: Re: 1.2.840.10008.1.2.4.51 with 8 bit YBR_FULL_422 color images
From: kuldiprindani@gmail.com (kuldip...@gmail.com)
Injection-Date: Fri, 17 Dec 2021 22:05:04 +0000
Content-Type: text/plain; charset="UTF-8"
Lines: 21
 by: kuldip...@gmail.com - Fri, 17 Dec 2021 22:05 UTC

On Friday, December 17, 2021 at 10:54:01 AM UTC-6, kuldip...@gmail.com wrote:
> We have a question whether DICOM transfer syntax 1.2.840.10008.1.2.4.51 ( Lossy 12 bit image compression) - can it be also be used for decompressing 8 bit YBR_FULL_422 color images?
>
> We have this question (& confusion) because of below weird findings from test
>
> Some of 8bit YBR_FULL_422 color images are grayed out after passing thru 1.2.840.10008.1.2.4.50 (JPEG baseline 8bit) de-compressor but they are displayed correctly when using 1.2.840.10008.1.2.4.51 (12 Bit Image Compression).
> but within same study images with same properties 8bit YBR_FULL_422 are displayed fine after passing thru 1.2.840.10008.1.2.4.50 (JPEG baseline 8bit) de-compressor.
>
> overall we found during test 1.2.840.10008.1.2.4.51 (12 bit) works always.
>
> I know immediate comment here would you to rely on transfer syntax of image but in one of our legacy product we are forced to rely on a private tag to determine image compression.
>
> I'm looking for comment from JPEG de-compression point of view if 1.2.840.10008.1.2.4.51 (12 bit) can take care of 8 bit & 12 bit both.
>
> Thanks.

I did more investigation on this and found issue is related to offsetting read from Start of image (SOI) marker in JPEG de-compression.
so if SOI is not offset then we are seeing graying image due to I believe bad input to de-compressor otherwise not.

Can you someone comment on SOI if it is mandatory in JPEG image.

Thanks.

1
server_pubkey.txt

rocksolid light 0.9.81
clearnet tor