TheCallSign / fjcore

Automatically exported from code.google.com/p/fjcore
0 stars 0 forks source link

Hierarchical JPEG Support #3

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
How hard would it be to add hierarchical JPEG support?
Is hierarchical Jpeg part of the "baseline" spec?

Happy to help if possible.

Original issue reported on code.google.com by michael....@gmail.com on 3 Mar 2009 at 7:42

GoogleCodeExporter commented 8 years ago
It's not part of the baseline spec as far as I know, but it would be a nice 
addition.
 Lower priority than some other updates, though, like reducing memory footprint.

Original comment by jeff.pow...@gmail.com on 23 Apr 2009 at 6:39

GoogleCodeExporter commented 8 years ago

Original comment by jeff.pow...@gmail.com on 23 Apr 2009 at 6:39

GoogleCodeExporter commented 8 years ago
Would just like to point out that as I was testing the library against JPEG 
images 
produced by my camera, the images were all of the Hierarchical type. 
Considering how 
this library would be utilized by people to do client side resizing of images. 
I' 
think this might be a higher priority then low?

Original comment by maraud...@gmail.com on 10 May 2009 at 4:04

GoogleCodeExporter commented 8 years ago
I feel a little odd asking for anything after getting this whole fantastic jpg 
library for free but I do have to agree with marauderz, that many images that 
come 
from cameras appear to be hierarctical (whatever that is, I just know it throws 
an 
exception about it). This puts a big dent in the ability to use the library if 
certain users essentially won't be able to use it for any of this own photos. 
Hopefully the vast majority of pics are not like this but I know that just 
trying my 
own photos, I was able to easily find some that were hierarchtical. It's going 
to be 
an interesting challenge to explain to average Joe why their friend's jpg will 
load 
but their's won't.

Aside from that, great library; fantastic job!

Original comment by tgreenfi...@gmail.com on 25 May 2009 at 7:06

GoogleCodeExporter commented 8 years ago
This format will be supported soon.  However, until these comments I haven't 
been
aware of a single camera that uses this format.  It'd be interesting to find 
out how
prevalent this format actually is.  marauderz, what model is your camera?

Original comment by jeff.pow...@gmail.com on 25 May 2009 at 7:08

GoogleCodeExporter commented 8 years ago
My camera is a Sony Alpha 350, it's one year old. 

tgreenfield : I too feel uneasy about requesting for the feature support. 
But... it's 
not something that I can fix myself.

Original comment by maraud...@gmail.com on 25 May 2009 at 8:01

GoogleCodeExporter commented 8 years ago
I did more research and found that actually very few pictures kicking on the 
hierarchtical exception. Unfortunately, I can't seem to find any rhyme or 
reason to 
which ones do. Pictures from the same carmera (Canon Digital Rebel) will work 
just 
fine; it just depends on the picture. Unfortunately, I don't know the history 
of the 
file so I'm not sure if it's ever been post-processed. I also noticed that if I 
open 
an offending file in photoshop and resave it doesn't not have the problem 
anymore. 
Which makes me wonder if maybe there a bug in the decoder library and the file 
is 
actually not hierarchtical? Just a thought. I attached a file that causes the 
exception if anyone wants to take a look.

Original comment by tgreenfi...@gmail.com on 14 Jun 2009 at 8:12

Attachments:

GoogleCodeExporter commented 8 years ago
That's an interesting find indeed tgreenfield, I have this urge to start 
throwing 
all the files I have from my camera at it and see what sticks but I'm a bit 
tied up 
now.

Original comment by maraud...@gmail.com on 18 Jun 2009 at 1:59

GoogleCodeExporter commented 8 years ago
That's an interesting find indeed tgreenfield, I have this urge to start 
throwing 
all the files I have from my camera at it and see what sticks but I'm a bit 
tied up 
now.

Original comment by maraud...@gmail.com on 18 Jun 2009 at 1:59

GoogleCodeExporter commented 8 years ago
Hi,

As for SL3 (and WPF) it is impossible to get a preview of a 'progressive jpeg'. 
This
can be a very useful feature with large images that take allot of time to 
download.
This was actually the reason I came upon this utility and would be very happy 
to see
this feature as part of the fjcore in the future.

Gilad.

Original comment by gilad.ka...@gmail.com on 23 Aug 2009 at 2:00

GoogleCodeExporter commented 8 years ago
FANTASTIC LIBRARY! Thanks for sharing!

I have a number of different users that have had images from a range of cameras 
(mostly 1 year old or less). The hierarchical support issue is occurring quite 
often. I have had NO OTHER ISSUES. I think it is therefore probably the most 
critical bug with this library. I have been looking for workarounds without 
much success.

Is there an expected completion date for this?

Thanks again!

Original comment by yusuf.en...@gmail.com on 8 Jun 2010 at 8:30

GoogleCodeExporter commented 8 years ago
Hi. We too love this library but are super frustrated with this hierarchical 
jpeg limitation.  We have found that a Sony DSLR-A100 uses this format fwiw.

Original comment by davidap...@gmail.com on 14 Jul 2011 at 11:21

GoogleCodeExporter commented 8 years ago
Hi, this is a great library, was wondering if the Unsupported Codec Type: 
Hierarchial JPEG, issue has been resolved within a new release.  I am currently 
working on a project to resize jpeg images and submit them to the home office 
for insurance policies, and i am getting a number of users that report this 
message.  I am hoping this has been resolved, otherwise I have to find a work 
around for the issue.

Original comment by ChadGhan...@gmail.com on 11 Jun 2012 at 3:31

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
I've fixed this bug in the GitHub fork for this project. 

https://github.com/briandonahue/FluxJpeg.Core

Original comment by e.fegge...@gmail.com on 22 Jun 2014 at 10:20