Loading ...
Sorry, an error occurred while loading the content.

Re: [pixelmed_dicom] Acceptable Transfer Syntaxes?

Expand Messages
  • Bill Peterson
    I like to ask a slightly different question about this same topic. If I only want to read/edit/save the meta data header, can I accomplish these steps without
    Message 1 of 6 , May 7, 2007
    View Source
    • 0 Attachment
      I like to ask a slightly different question about this same topic.  If I only want to read/edit/save the meta data header, can I accomplish these steps without knowing  or altering the transfer syntax and the pixel data?

      Thanks.

      Bill

      ----- Original Message ----
      From: Bill Peterson <billkinetix@...>
      To: pixelmed_dicom@yahoogroups.com
      Sent: Monday, May 7, 2007 10:28:09 AM
      Subject: Re: [pixelmed_dicom] Acceptable Transfer Syntaxes?

      I understand.  Thank you.

      Bill.

      ----- Original Message ----
      From: David Clunie <dclunie@dclunie. com>
      To: pixelmed_dicom@ yahoogroups. com
      Sent: Sunday, May 6, 2007 8:49:58 AM
      Subject: Re: [pixelmed_dicom] Acceptable Transfer Syntaxes?

      No.

      The compressed transfer syntaxes are supported for reading
      only at the moment, since they were added to support a display
      use case.

      David

      Bill Peterson wrote:

      > Thanks.
      >
      > Does AttributeList. write() also supports the same list below?
      >
      > Bill
      >
      > ----- Original Message ----
      > From: David Clunie <dclunie@dclunie. com>
      > To: pixelmed_dicom@ yahoogroups. com
      > Sent: Friday, May 4, 2007 5:43:55 PM
      > Subject: Re: [pixelmed_dicom] Acceptable Transfer Syntaxes?

      >
      > Hi Bill
      >
      >
      >
      > billkinetix wrote:
      >
      >
      >
      >> I did some searching before asking this question. I still had
      >
      >> questions though.
      >
      >
      >> What Transfer Syntaxes does PixelMed support or not support? Are the
      >
      >> supported Transfer Syntaxes for both importing and exporting? I
      >
      >> believe I do understand that the JIIO codecs is required to support
      >
      >> specific compression. Is there anything else needed for this specific
      >
      >> purpose?
      >
      >
      >
      > The network code supports the uncompressed transfer syntaxes,
      >
      > deflate and bzip2 only, and will not currently negotiate anything
      >
      > else.
      >
      >
      >
      > In addition, the attribute list reading code will support various
      >
      > compressed transfer syntaxes as listed below; this capability
      >
      > was added only to support the ability to display compressed
      >
      > files received from various sources other than over the network.
      >
      >
      >
      > The reason this is not integrated with the network code is the
      >
      > requirement to be able to transform from compressed to uncompressed
      >
      > and back again depending on what is negotiated; since the JIIO
      >
      > codecs would be needed for this but are not available for every
      >
      > platform, I have not prioritized adding this capability.
      >
      >
      >
      > Obviously it would be possible for anyone to tweak their own
      >
      > association negotiation to accept these (or other) transfer
      >
      > syntaxes if they were willing to violate the requirement that
      >
      > translation be possible, and had a reason to be able to store
      >
      > and regurgitate but not convert these.
      >
      >
      >
      > These are what AttributeList. read() currently supports:
      >
      >
      >
      > JPEGBaseline
      >
      > JPEGExtended
      >
      > JPEG2000
      >
      > JPEG2000Lossless
      >
      > JPEGLossless
      >
      > JPEGLosslessSV1
      >
      > JPEGLS
      >
      > JPEGNLS
      >
      >
      >
      > Note that you could extend this list pretty easily, but that there
      >
      > are some dependencies in EncapsulatedInputSt ream on the marker
      >
      > syntax used by JPEG to detect ends of frames (since frames can
      >
      > span fragments).
      >
      >
      >
      > David




      Ahhh...imagining that irresistible "new car" smell?
      Check out new cars at Yahoo! Autos.



      Ahhh...imagining that irresistible "new car" smell?
      Check out new cars at Yahoo! Autos.
    Your message has been successfully submitted and would be delivered to recipients shortly.