Thank you very much for such a quick reply.
In the mean time I indeed added TransferSyntax.JPEGLosslessSV1
to AssociationAcceptor and was able to receive and view my
JPEG Lossless file all right !
Have not tried transmitting it yet...
I really think your toolkit is really a great contribution to Dicom
community. I tried dcm4che briefly, but I am much more happy with
--- In firstname.lastname@example.org, David Clunie <dclunie@...> wrote:
> Hi John
> johnk269 wrote:
> > Are the Sun JAI I/O native codes only required for pixelmed image
> > browser to be able to open JPEG Lossless or are they also required
> > for Pixelmed StorageSOPClassSCP based Store SCP?
> > What could be the main reason for Store SCP to reject transfer syntax
> > 1.2.840.10008.1.2.4.70?
> The compressed transfer syntaxes are supported for file
> read and write only at present.
> I have not gotten around to adding support for these in
> the network utilities like StorageSOPClassSCU and
> StorageSOPClassSCP, since to do so requires some
> additional logic to check whether or not one can
> convert from one to the other (e.g., whether or not
> one should store an incoming compressed transfer syntax
> as is, or try to decompress it, and vice versa on
> retrieval, depending on whether or not the codecs are
> available and whether or not one wants to decompress
> lossy data).
> It would be near trivial to add the additional transfer
> syntaxes to the transfer syntax acceptance code, and
> to store the datasets to disk, but not trivial to deal
> with the issues associated with having to regurgitate
> compressed data, or not, as the case may be, in a manner
> that is compliant with the rules of the standard in
> Part 5 (which essentially state that you must be able
> to decompress them).
> Mostly my laziness can be attributed to the fact that the
> JIIO native codecs are not supported on my primary development
> platform, which is a Mac.