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

JPEG error: SOI not found #41

Closed
makr28 opened this issue Aug 24, 2018 · 5 comments
Closed

JPEG error: SOI not found #41

makr28 opened this issue Aug 24, 2018 · 5 comments

Comments

@makr28
Copy link

makr28 commented Aug 24, 2018

I don't think this would be specific to Node.js but I don't know for sure.

But I am getting the following when using the latest UTIF master code, when I try to view a tiff document that uses new style Jpegdecoder.

The following code is in method UTIF.decode._decodeNewJPEG = function(img, data, off, len, tgt, toff)

parser = new UTIF.JpegDecoder();

returns

g {M: null, B: -1}
   B: -1
   M: null

then

parser.parse("buff")

returns

g {message: "JPEG error: SOI not found"}

@photopea
Copy link
Owner

Hi, could you please give us a file, which does not work with UTIF.js ? Are you sure that file worked before?

@makr28
Copy link
Author

makr28 commented Aug 24, 2018

I can't attach a file here but I replied to your latest comment with the file thru gmail. I hope that worked

@makr28
Copy link
Author

makr28 commented Aug 24, 2018

I tried multiple online converters to get new type 7 examples (I will email them to you. They do not work either. I can't get any Type 7 working.

@photopea
Copy link
Owner

Hi. So this error was not related to a JPEG library, but to an incorrect reading of data from IFD. This bug appeared several months ago. Too bad you did not update your UTIF.js back then, so we could fix is earlier. All this time, I thought it is related to a JPEG library.

It was fixed and it should work now. But there is another bug - some files appear to have incorrect colors: #42

@makr28
Copy link
Author

makr28 commented Aug 28, 2018

Yeah I get that, unfortunately we couldn't use your UTIF without it being thru an npm release for stability reasons. Like if you update master and were using the your git URL in our package.json, we get every update. But for npm we don't automatically get new stuff unless we specifically change what version we are requesting. So Once @Scimonster releases we can switch it back to yours.

Thanks for working on this by the way, I had left my work computer at work and didn't get a chance to send you the requested things.

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