CompuServe Thread

#TIFF problem

10 messages in this thread
#48713From: Ron MenelliDec 20, 1992 8:47 PM
Ben, I've just uploaded a TIFF file to the Black Belt section. The file loads fine on a NeXT, but fails on the second (and first) version of the TIFF loader. Could you take a look at it? I have more files where that one came from, if you're interested. Thanks, Ron Menelli
#48732From: Black Belt SystemsDec 21, 1992 12:53 AM
Yep, you bet – I'll D/L now, and we'll go at it tomorrow. Where did this file come from, just out of curiosity? –Ben …via AutoPilot
#48757From: Black Belt SystemsDec 21, 1992 3:42 PM
Further on that TIFF file…. we've got the loader loading it. It was a bit "funny", but reading the TIFF spec (carefully) that funnyness is allowed. –Ben …via AutoPilot
#48759From: Ron MenelliDec 21, 1992 5:12 PM
The file came from a collection of files that are on a NeXT system. There are a bunch of them there, and I'm not sure where they came from :-). Thanks for the prompt response. -Ron 72537,1361
#48779From: Black Belt SystemsDec 22, 1992 12:46 AM
You bet – I'll have the fixed version posted tonite. –Ben …via AutoPilot
#48847From: Ron MenelliDec 23, 1992 9:23 AM
Ummmm….. I'm still having problems with that file I uploaded. It seems to come out somewhat garbled, but it does load instead of locking up now. Could you check the loader that was uploaded here against the TIFF I uploaded? Thanks again, Ron "The bane of a TIFF reader's existence" Menelli 72537,1361
#48889From: Black Belt SystemsDec 24, 1992 1:19 AM
We did, Ron – what happened – what do you mean by "garbled"? –Ben …via AutoPilot
#49038From: Ron MenelliDec 27, 1992 9:18 PM
Well, I've posted a file (sunset.iff) that is a 320×200 IFF rendering of the TIFF file. That should give you an idea. BTW, my machine does not have enought memory to allocate an undo buffer, but does have enough for the primary, in case that might have something to do with it. -Ron
#49078From: Black Belt SystemsDec 28, 1992 12:40 PM
Ah! That was your sunset file? That thing loads fine – put Imagemaster into "Exact Image" and you'll see it. What's happening is that becuase that's a very high resolution dithered file, the subsampling Imagemaster does to make it fit all onscreen grabs pixels that aren't near each other. Here, try this: Scale the image to 640×400 using the tools in the Process panel. Then look at the results using "luma" mode. You'll see it's all there. –Ben …via AutoPilot
#49172From: Ron MenelliDec 29, 1992 9:24 PM
Ah, I understand now… Thanks for the clarification. -Ron