Topic: Another PPM question

Although I do have my main machine working flawlessly with PPM files generated  from dcraw...

Others machines simply report with an "unsupported pixel format"
or with a strange dialog defining a rasterized bmp by selecting the number of pixels vs bit depth ...

In order  to test this I did tried the same dcraw, same image , same Image analyser version ...

I avoid all of those problems by forcing the TIFF flag in dcraw ...
Any idea why the different behaviour ?

Now a small request :
Would be possible to make a warning ( at opening or different info in the mdi window) when reading 16bits TIFF or 16bits PPM  instead of displaying the filename and "24 bit" ....
I know the image is always showing in 24 bit but sometimes I do have several images (some JPEGs others in TIFF or PPM) with the same picture ...
 
Now for something different:
I visually noticed differences between images (specially low lightining conditions) treated from 16 TIFF files  and 8bits JPEGs inside Image Analyser... smile
So IA still rocks smile

2

Re: Another PPM question

Do you have JasPerLib.dll in the IA folder on both machines? As far as I remember this DLL is used to decode PPM files.

Michael Vinther

> software developer <

Re: Another PPM question

Sorry for the delay...
I have JasperLib inside IA directory in both the machines...

But I think JasperLib is only needed for the JPEG2000 format ...

Is there any way to check the JasperLib.dll  version ?

Regarding the reading of PPM or TIFF I have tried (with some sucess ) to read 16bits PNGs ...  smile
Now my "workflow" is converting the X3F files to 16bits PNG (tru imagemagick) and then read them in IA...

Saving a resulting post-worked  PNG or JPG ... smile

4

Re: Another PPM question

JasPerLib.dll is used for reading files of the following types: *.jp2, *.jpc, *.pnm,*.pgm,*.ppm, *.ras
It doesn't have a version number but I haven't changed it since 2005 as far as I can see. If you want to be sure you can always compare the file size on the two computers. My version is 126.976bytes, but I don't even have any PPM files to test it with.

Michael Vinther

> software developer <

Re: Another PPM question

I do have 2 different JasPerLib.dll files ...

One with   129 536 bytes ( unknown origin)
other with 126 976 bytes ( from Image Analyser installation) ...

Tested IA by starting afresh each time
with a different jasperlib.dll inside de IA directory.

Same result....  sad
"Unsupported Pixel format error..."

Although my "main" working machine is using the 126 976 bytes dll without any problem...

Any more ideas ?

6

Re: Another PPM question

Strange. Is it exactly the same PPM file you load on the two machines? In that case I don't know.

Michael Vinther

> software developer <

Re: Another PPM question

Again more info (and a small mistake smile  ...

The machine where I have IA working with the 16 bit PPM files has
another JasPerlib.dll ( 136 704 bytes, created : 26  May  2005, 10:17:00) ...

I suppose I will keep it as it is ... smile

Why does this version work with the PPM instead of the more recent one ???

8

Re: Another PPM question

I probably didn't test the updated JasPerLib.dll with PPM files as I don't use that format myself so I didn't notice that PPM support was broken.
Could you possible send me some PPM files that worked with the old version but not with the latest? Then I can check if it is easy to fix.

Michael Vinther

> software developer <

Re: Another PPM question

After some more tests it seems that both
PPM and PNG file formats
(at least with 16bits per channel)
are "broken" with the latest JasperLib.dll ...

With the "old" version IA does seem stable enough to work fine.

Any update ?

10

Re: Another PPM question

The PNG handler is not is JasPerLib DLL so that would be strange...

Michael Vinther

> software developer <

Re: Another PPM question

Oops ... smile
Please disregard the PNG problem...
It seems that somehow the extension was *.png but the contents of the file were in fact  PPM ... smile
So the problem is still with PPM files... ( still JasperLib DLL )

Nonetheless my apologies for the misleading PNG problem...
But as I wrote before it would be nice to have any reference of the PNG image or PPM image being read with more than 8bits per channel...

A small flag on top of the image window , much like it happens now with the "image changed"  asterisk would be nice...

Thanks in advance ...

12

Re: Another PPM question

I have updated the latest beta with a new JasPerLib.dll which should support PPM and JPEG2000 in more pixel formats.
If you select Operations | Show image information in IA you can see the source file pixel format for some files (depends on the individual file format handler but JasPerLib now does it)

Please help me test that the different file formats still works...

Michael Vinther

> software developer <

13 (edited by MarkMarques 2010-08-09 21:33:27)

Re: Another PPM question

I have tested with the new JasperLib but still does not work ... sad

It opens a "load RAW uncompressed bitmap" dialog asking for the resolution
and pixel format ( 8 or 24 bit) plus a header ...

Tried with the correct height and width values but with no success sad
If I left the automatic (height or width) (I suppose calculated from the filezise ...) I get an error reporting :
"read less than expected" ...

Although in my machine I still can read correctly the PPM files even with the updated JasperLib...
So in my Numer 1 machine I do have some DLL or something that allows me to read the PPM file passing it to IA in way that JasperLib understands it...

I another machine I  made an IA complete fresh install ( installation EXE and putting afterwards the beta release) but it can not read the PPM file... sad

I suppose that in my machine I installed something ( NetPbm or something that allows JasperLib understand the 16bit files)
(In a similar way I can say that Imagemagick is not in the middle of this...)
One of "bad machines" has Imagemagick installed ...

14

Re: Another PPM question

I'm surprised. I can open the PPM files just fine with the latest JasperLib DLL. It should be in the the folder with the executable and its size should be 136,192 bytes.

Actually the RAW loader should only appear if IA cannot find the DLL. That is the default behavior when it gets a file with an unknown extension, and it should only be unknown if the DLL is not present. Does your file have the correct extension?

By the way, IA stores color images internally in 24bit format even though the source precision is higher. Some operations temporarily uses high (usually 32 bit per channel floating point) precision but the result is converted back to 24bit at the end of each operation.

Michael Vinther

> software developer <

Re: Another PPM question

As I wrote in the previous post:
in  the main machine the PPM file is read correctly
with the most recent verson of JasperLib...

In a completely new machine with IA 1.31 exec + latest beta zip the same PPM image is not read being identified as "RAW" data ...

In the main machine IA image information reports :

filename : sdim0354.ppm
image dimensions : 2688x 1792
Pixel format :24 bit
Total Number pixels: 4.816.896
Number of color used: 51938
Source file information: 48bpp

Every thing is correct ( at least I suppose so ... smile )

Is there any way to have a "debug dialog" reporting which external libs are in memory used from IA ...

Later on I will try if the netPBM files or even cygwin have something to do with this PPM problem ...

16

Re: Another PPM question

Strange. The only hint on what DLLs are loaded is that the names are shown in the splash screen, but only for a very short time. It is not depending on any external libraries, only my DLLs.

Michael Vinther

> software developer <

17 (edited by MarkMarques 2010-08-11 10:24:47)

Re: Another PPM question

After some reading of the PPM file format I noticed that there problems regarding the
big or litle endian in the header files ...
in the wikkipedia and 16 bits header files ...

"http://en.wikipedia.org/wiki/Netpbm_format#PPM_example"



So I noticed that the difference between my "working machine" and all the others is the processor ...
In the working machine It has an "old" 64 bits Athlon processor not an Intel  ...

Perhaps thats the difference ? smile
Somewhere Windows get confused with the  16-bit endianness of the pixel packing order in the header ?

Regarding the idea of a more "persistent" way to show off which libs and or which  plugins are installed , in a "Debug | Info" information window or even in the About window ?

18

Re: Another PPM question

The CPU will not make any difference, because the raw import dialog only appears if the DLL is not loaded at all.

I have update the beta download with a version which shows the version of all loaded plugins.

Michael Vinther

> software developer <

19 (edited by MarkMarques 2010-08-11 19:11:15)

Re: Another PPM question

I have tried the latest beta and ahve the following list:
DecorrelationStretching.dll 1.1.2005.0
DiagramReader.dll
FractInterpolation.dll 3.1.2010.0
HDRCombine.dll .1.2.2009.0
JasPerLib.dll 1.3.2010.0
RasterExport.dll 1.2.2006.0
SeamCarving.dll 1.0.2008.0
VectorGraphics.dll 1.3.2008
View3DModel.dll 1.7.2007.0
TIFFRead.dll 1.6.2010.0

Any more ideas ?
Still not opening any PPM file .... sad

20

Re: Another PPM question

Not really. How about TIF files, can you open them? They use the same plugin  system as JP2 and PPM files, just another DLL.

Try making a new folder and put only Analyzer.exe and JasPerLib.dll in it, and see if that works.

Michael Vinther

> software developer <

21 (edited by MarkMarques 2010-08-11 19:36:53)

Re: Another PPM question

I made 2 tests ...
I have tried to read the TIFF file generated by dcraw  (with success.. )

Copied Ianaliser.exe , IA.drc and JasperLib to a single dir and executed ...
Ia started Ok and reported JasPerLib as the only dll available...

But still it does not read the PPM files.... sad
The RAW file dialog appears ...

The dir without the TIFFRead.dll lib does not read the TIFF files , as expected ...

22

Re: Another PPM question

Very strange. I assume that it is exactly the same PPM file with the same name that you can open on the other PC?

Michael Vinther

> software developer <

23 (edited by MarkMarques 2010-08-11 21:40:53)

Re: Another PPM question

In reality it is not the same file...
Although it has always the same PPM header ...

-----------------------------
P6
2688 1792
65535
binary data
-----------------------------

As soon I can I will try to use the latest version on the "working machine" ...

with the latest working machine IA reports :
DiagramReader.dll
JasPerLib.dll 1.3.2010.0
Plugin.dll 6.0.128.0
DecorrelationStrecthing.dll 1.1.2005.0
fractInterpolation.dll 2.0.2006.0
Interface8bf.dll 0.1.2005.0
ProfileLine.dll 1.1.2006.0
VectorGraphics.dll 1.3.2008.0
View3DModel.dll 1.7.2008.0
TIFFRead.dll 1.6.2010.0

The only noticeable difference are the Plugin.dll and the the Interface8bf.dll ...

Comments?

24 (edited by harrybelmont123 2010-08-13 2:36:16)

Re: Another PPM question

image analyzer works fine for my XP operating system but does not meet the same success with vista or windows 7. There are lots of things that are being asked like validation of OS license and similar things like that.    online pokies

Re: Another PPM question

Made small experiment...
Tried the idea of putting IA.exe with JasperLib.dll ...
But this time in the "working machine" ...
And it still works OK ... smile
So we can rule out "internal IA problems" ...

So the problem with "Other machines" is External to IA ...  sad

I will try to find out which software is responsable for this ...

As soon as I have some more info I will post ... smile