loading...

Recent progress of Aspose.Imaging

nnevod profile image Dmitry Matuzko ・2 min read

In this article I'll tell about recent notable improvements of Aspose.Imaging.

Fixed saving Baseline JPEG to Progressive.

Previously, in case you read an baseline JPEG image and tried to export it as progressive JPEG, you'd get an exception. Now this error is fixed and you can do it just fine like that:

using (Image image = Image.Load("interleaved.jpg"))
{
    JpegOptions saveOptions = new JpegOptions();
    saveOptions.CompressionType = JpegCompressionMode.Progressive;

    image.Save(dir + "interleaved_progressive.jpg", saveOptions);
}

Incorrect EMF creation.

Before, graphic primitive count in EMF's header was set incorrectly, leading to incorrect representation of the last added graphic primitive. The error has been fixed and EMFs are created correctly.

Dashed lines saved as solid when exporting to SVG.

When source containing dashed lines was saved to SVG - be it vector graphics file or newly created set of graphic primitives, they were exported to SVG as solid lines. As of Aspose.Imaging 18.9, this problem has been fixed for licensed mode. However, when operating without license, lines still get converted to solid ones. This problem should be resolved in Aspose.Imaging 18.10 release.

JPEG encoder optimisations.

JPEG DCT encoder has been optimised and displays up to 50% more performance (= up to 30% less time to encode).

DICOM losing color when exporting to BMP.

DICOM files with RGB color space that used lossless JPEG compression were exported as grayscale when exporting to BMP (actually, they were read as grayscale). Now this has been fixed and output JPEG should be correct.

That's all for now, stay tuned!

For more examples please visit the Aspose.Imaging GitHub page. There's also Twitter and Facebook pages for news on Aspose.Imaging.

Posted on by:

Discussion

pic
Editor guide