Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Encoder/Decoder feature set. #7

Open
JimBobSquarePants opened this issue Jan 20, 2016 · 3 comments
Open

Encoder/Decoder feature set. #7

JimBobSquarePants opened this issue Jan 20, 2016 · 3 comments

Comments

@JimBobSquarePants
Copy link

Hi there,

Is there a feature set listed anywhere that compares the jpeg encoder/decoder functionality against libjpeg.

I'm currently writing a cross-platform imaging library ImageProcessor and I have run into performance issues with the current encoder I am using so I am looking for alternatives.

I'm also wondering how many of the issues listed on Google code are still relevent?

Many Thanks

James

@anders9ustafsson
Copy link
Collaborator

Hi James,

Many thanks for asking! I've taken a quick glance at ImageProcessor in the past and it looks impressive.

Unfortunately, neither Brian nor I are actively developing this library right now. Brian forked it from Google Code a few years ago and set up the NuGet package, I added PCL functionality to allow the library to be used cross-platform. Since then we have accepted a few pull requests from other contributors, that's all.

I also do not have any really good overview of supported features. Personally, from my medical image perspective, my main concern has been that FluxJpeg only supports 8-bit images, but that is probably not a big issue for a general image processing framework.

The issues list on Google Code is also no up-to-date, but I cannot say up-front what is fixed and what is not. Ideally we should of course import the list and tick off the fixed items... In due time :-)

From a development activity and completeness perspective LibJpeg.Net is probably a safer bet right now. On the other hand, that library is not cross-platform, right? It should be relatively easy to turn it into a PCL library though; there is already a Silverlight version that excludes the System.Drawing references.

Best regards,
Anders @ Cureos

@anders9ustafsson
Copy link
Collaborator

@JimBobSquarePants You woke the issue importer in me :-) The open Google Code issues have now been transferred to this repository. When I have the time I will go through each one in detail and close those that are completed or invalid.

@JimBobSquarePants
Copy link
Author

Hi Anders,

Thanks for your swift reply.

LibJpeg.Net is actually what I am using just now, albeit embedded within my own codebase. Unfortunately it's horribly slow taking 5-6 seconds to decode/encode a (3648 x 2736) image when System.Drawing can do it in ~400ms. Compounding this the code is nigh on unreadable making it incredibly difficult to optimise. The code here is much easier to follow.

Digging through your source code I cant find any reference to progressive Jpeg's though and I would like to support as much of the Jpeg standard as possible Looks like I have a spec to read...

Very glad to see you've imported the issues! That's great to see:)

Cheers

James

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants