libexif-devel — This is the place where your questions about libexif will be answered.

[Libexif-devel] libexif and TIFF files

[Jason V. P. <ja...@mi...>]

Greetings folks -

Lutz pointed me at this mailling list after I asked him about TIFF support. 
I see there have been a number of discussions on it during the summer
months, but haven't seen anything recent.  Has anyone done any work on it? 
Any guinea pigs needed? :-)

I have a camera (D1x) that produces TIFF files.  It does look like there's
some sort of interesting data stored in the file.  Dunno if it's
technically EXIF or not?  In any event, I'll be happy to test code, etc, if
anyone needs any help.

My ultimate goal would be to have an EXIF patch for the TIFF plug-in
in GIMP, similar to the one Lutz wrote for the JPEG plug-in.  I'd like to be
able to open TIFFs in GIMP, edit them, and then save them back as JPEGs with
the appropriate information stored.

Thanks!

jas
-- 
Jason Van Patten
AOL IM: Jason VP 

Re: [Libexif-devel] Re: Problems compiling exif-gtk and gphoto2 w/ libexif

[Lutz <lu...@us...>]

On Fri, 2002-09-20 at 02:01, Robert Davis wrote:
>  >> gphoto2-filesys.c: In function `get_exif_mtime':
>  >> gphoto2-filesys.c:101: structure has no member named `ifd0'
>  >> gphoto2-filesys.c:103: structure has no member named `ifd_exif'
>  >> gphoto2-filesys.c:106: structure has no member named `ifd_exif'

(...)

> pkg-config says 0.5.6. I searched my whole HD for the exif includes and=20
> only found the one location.

Then libgphoto2/configure didn't detect that. rm config.cache and
configure again. Send me all output of configure.

Lutz
--=20
+----------------------------------------------+
| Lutz M=FCller                 +49 (7156) 34837 |
|                                              |
| Hans-Sachs-Strasse 5                         |
| 71254 Ditzingen       http://www.topfrose.de |
| Germany           lu...@us... |
+----------------------------------------------+

[Libexif-devel] Re: Problems compiling exif-gtk and gphoto2 w/ libexif

[Robert D. <rg...@ho...>]

 >> gphoto2-filesys.c: In function `get_exif_mtime':
 >> gphoto2-filesys.c:101: structure has no member named `ifd0'
 >> gphoto2-filesys.c:103: structure has no member named `ifd_exif'
 >> gphoto2-filesys.c:106: structure has no member named `ifd_exif'
 >
 > There are some checks for your libexif version in libgphoto2. Do you
 > happen to have multiple versions of libexif installed on your system
 > (for example /usr or /usr/local)? What does "pkg-config --modversion
 > libexif" say?

pkg-config says 0.5.6. I searched my whole HD for the exif includes and 
only found the one location.

Robert Davis

Re: [Libexif-devel] Problems compiling exif-gtk and gphoto2 w/ libexif

[Lutz <lu...@us...>]

On Wed, 2002-09-18 at 04:48, Robert Davis wrote:
> cc1: warnings being treated as errors
> gtk-menu-option.c: In function `gtk_menu_option_get_type':
> gtk-menu-option.c:140: warning: pointer of type `void *' used in arithmet=
ic
> gtk-menu-option.c:140: warning: pointer of type `void *' used in arithmet=
ic
> gtk-menu-option.c:140: warning: pointer of type `void *' used in arithmet=
ic
> [etc repeated a few more time]

Comment out -Wall in the Makefile and you should be fine.

> gphoto2-filesys.c: In function `get_exif_mtime':
> gphoto2-filesys.c:101: structure has no member named `ifd0'
> gphoto2-filesys.c:103: structure has no member named `ifd_exif'
> gphoto2-filesys.c:106: structure has no member named `ifd_exif'

There are some checks for your libexif version in libgphoto2. Do you
happen to have multiple versions of libexif installed on your system
(for example /usr or /usr/local)? What does "pkg-config --modversion
libexif" say?

Lutz
--=20
+----------------------------------------------+
| Lutz M=FCller                 +49 (7156) 34837 |
|                                              |
| Hans-Sachs-Strasse 5                         |
| 71254 Ditzingen       http://www.topfrose.de |
| Germany           lu...@us... |
+----------------------------------------------+

[Libexif-devel] Problems compiling exif-gtk and gphoto2 w/ libexif

[Robert D. <rg...@ho...>]

Two problems..

1. Compiling libexif-gtk-0.3.2 with gtk+-2.0.6 get:

gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -DGTK_DISABLE_DEPRECATED 
-I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 
-I/usr/include/pango-1.0 -I/usr/X11R6/include -I/usr/include/freetype2 
-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -g -O2 -Wall 
-Wchar-subscripts -Wmissing-declarations -Wmissing-prototypes 
-Wnested-externs -Wpointer-arith -Werror -c gtk-menu-option.c  -fPIC 
-DPIC -o .libs/gtk-menu-option.lo
cc1: warnings being treated as errors
gtk-menu-option.c: In function `gtk_menu_option_get_type':
gtk-menu-option.c:140: warning: pointer of type `void *' used in arithmetic
gtk-menu-option.c:140: warning: pointer of type `void *' used in arithmetic
gtk-menu-option.c:140: warning: pointer of type `void *' used in arithmetic
[etc repeated a few more time]

2. compiling gphoto2-2.1.0 again libexif 0.5.6 (and 0.5.4):

gcc -DHAVE_CONFIG_H -I. -I. -I. -I.. 
-I../libgphoto2_port/libgphoto2_port 
-DCAMLIBS=\"/usr/lib/gphoto2/2.1.0\" -DLOCALEDIR=\"/usr/share/locale\" 
-I/usr/include/libexif -O2 -mcpu=i686 -g -Wall -Wmissing-declarations 
-Wmissing-prototypes -c gphoto2-filesys.c 
-Wp,-MD,.deps/gphoto2-filesys.TPlo  -fPIC -DPIC -o .libs/gphoto2-filesys.lo
gphoto2-filesys.c: In function `get_exif_mtime':
gphoto2-filesys.c:101: structure has no member named `ifd0'
gphoto2-filesys.c:103: structure has no member named `ifd_exif'
gphoto2-filesys.c:106: structure has no member named `ifd_exif'
make[2]: *** [gphoto2-filesys.lo] Error 1
make[2]: Leaving directory 
`/var/tmp/portage/gphoto2-2.1.0/work/gphoto2-2.1.0/libgphoto2'
make[1]: *** [all] Error 2
make[1]: Leaving directory 
`/var/tmp/portage/gphoto2-2.1.0/work/gphoto2-2.1.0/libgphoto2'
make: *** [all-recursive] Error 1

Thanks for any help,
Robert Davis
Gentoo Linux 1.2

[Libexif-devel] libexif - plenty of bugs in the saving routine

[Lutz <lu...@us...>]

Hi!

I got some patches regarding exif_data_save_data. The code has been
horribly broken...

If you do development with libexif, I suggest you check out the current
CVS version. I hope I fixed all bugs, but one never knows...

Lutz
--=20
+----------------------------------------------+
| Lutz M=FCller                 +49 (7156) 34837 |
|                                              |
| Hans-Sachs-Strasse 5                         |
| 71254 Ditzingen       http://www.topfrose.de |
| Germany           lu...@us... |
+----------------------------------------------+

[Libexif-devel] Re: Nikon MakerNote support - what needs to be done?

[Hugh T. <hu...@au...>]

> Exactly. What you see in CVS is an attempt to a framework for
> MakerNotes. Often, MakerNotes are a simple list of values, for example
>
> Brightness: 3420
> Contrast: -1.5
>
> The problem is that they are not standardized. And that I don't have the
> specifications of any manufacturers' MakerNotes.
>
> If you think the framework that is in CVS is useful, you could code for
> example along libexif/olympus. But if you have other ideas on how to
> handle MakerNotes, please tell them.

In my EXIFutils product I've been gradually added support for various Maker
Note fields as I find out about them. My programs have gone through much
pain as I've adjusted them to handle the new and exciting ways manufacturers
have found to format their maker notes.

As you are starting from scratch, here's a summary of the formats of maker
notes I've encountered. Any framework you set up will need to consider these
variations:

The Maker Note formats I've enountered fall into the following categories:

1. Opaque data structure. I've made no attempt to decode these, I just
display them in hex. Kodak use this, which is sad because I have a Kodak
digital camera ;^(

2. Standard IFD. The Maker Note is formatted just like any other "standard"
EXIF IFD, you just need to know what the field tags mean. All Canon Maker
Notes I've encountered are like this.

3. Standard IFD with header. The Maker Note is formatted as in 2., but is
preceded by a fixed length header. The length of the header depends on the
make/model, but is always constant for that make/model. The header is
typically something like "Nikon\0\1\0". Nikon, Epson, Minolta and Olympus
cameras use this format.

4) TIFF format with Header. Recent Nikon models (eg the D100) have a fixed
length header (similar to 3.), but the header is followed bya complete TIFF
structure containing the Maker Note IFD fields. The implications of this are
(sorry if I'm stating the obvious):
 - all offsets in the Maker Note are relative to the start of the embedded
TIFF header,
not relative the EXIF TIFF header.
 - the byte ordering within the Maker Note may be different to that used
outside the Maker Note.

5) The Odd Man Out. FujiFilm use a format similar to 3. above, but with the
following differences:
 - all offsets are relative to the first byte of the Maker Note field
 - the field in the maker note *always* use Intel byte ordering.

In my programs I've taken the conservative approach, I do not try to parse
the the maker note field at run time to figure out its format. I have a
table of "known" makes/models. If the Make and Model fields in the EXIF data
match one of the known models in the table, I know the format of the Maker
Note.

Hope this helps.

Hugh

[Libexif-devel] Re: Nikon MakerNote support - what needs to be done?

[Duane H. H. <dh...@an...>]

This is another message constructed as a reply to a message found in the
archive (I just joined the list).


>> From: Peter Teichman <peter@xi...> 
>>    Nikon MakerNote support - what needs to be done?   
>> 2002-07-19 07:33 
>> I'm very interested in working on support for Nikon MakerNote tags. 
>>  What needs to be done?  It looks like the MakerNote support in general
>>  isn't wired up at the moment.  Is this the case?
>>  
>>  Peter


The information necessary to decode the Nikon 990 MakerNote is described at

http://www.tawbaware.com/990exif.htm

(max...@ta...)

That page also refers to a page by TsuruZoh Tachibanaya, which appears to be
no longer available, but includes MakerNote info for the Nikon 950, as well
as 
    Olympus D450Z
    Casio QV2000/QV8000
    Fujifilm (Finepix1400,Finepix4700)
    Canon   ( David Burren http://www.burren.cx/david/canon.html)

The Burren link also appears dead.  I have a copy (uncopyrighted) of the
Tachibanaya document, which I can email to anyone interested.

-----------
dhh @ androcles.com

[Libexif-devel] TIFF in Exif

[Duane H. H. <dh...@an...>]

I just joined the list, and found the following in the archives.

>> Is it possible to use libexif to access the exif information embedded in tiff 
>> files?  I`ve figured out that the offset to the exif info is stored in tiff 
>> tag 0x8769, but I`m still figuring out how to get libexif to read that 
>> information, so any hints would be greatly appreciated.
>> 
>> Thanks,
>> 
>> Paul Nolan, CEO Idruna Software Inc.
>> http://www.idruna.com

It *is* possible, and actually fairly easy.  I'd love to see "libexif"
support it, and I can offer a few words which may help. See below.

<ASIDE>
 It's important to state up front that I'm not an "expert"
in image file formats; nonetheless, ever since I bought my Nikon
990 about a year and a half ago, I've been dragging down every
(open-source) software distribution I could find that claims to
deal with EXIF, and poring over the TIFF, JPEG and EXIF specs trying
to understand the incestuous relation between them.  I do have
software (in addition to "libexif") that allows me to manipulate
Exif/Jpeg images (preserving the Exif information) but none of the
distributions so far seem to recognize that the EXIF spec also
covers the uncompressed TIFF format files produced by some cameras
at the highest quality setting...probably because few of us are
eager to chew up nearly 10MB/pix on our flash cards (or whatever).
The point of this lengthy aside is that it would be *very* nice if
"libexif" included support for reading (and *writing*) the Exif
information in TIFF files, and *then* distributions like PHP,
ImageMagick, etc.  used this common interface.  What follows is my
current understanding of how to access Exif information in TIFF
files.  I've used this to locally modify the "epinfo" program
included in the "photopc" distribution (Crosser/Bowen) to access
Exif information in TIFF files from my camera.  A knowledgeable
"libexif" developer should be able to munge "libexif" in a very
short time.
</ASIDE>

Here's the deal.  The existing routines in "libexif" should read
TIFF files jes' fine...you just have to start sooner.  It may be
necessary to recognize additional TIFF tags (I'm not up to speed
on "libexif" yet).

I'm not entirely sure how to explain this, so please bear with me.

When reading an EXIF/Jpeg file, you read a JPEG SOI (2 bytes),
followed by an APP1 header (10 bytes).  The APP1 begins with a TIFF
header, followed by two IFDS.  The first IFD contains an entry which
points to an EXIF IFD.

If the file is TIFF format, the first 12 bytes aren't there.  The
file starts with the TIFF header, including the offset to the first
IFD (which usually follows immediately, but might not).  Reading
the IFDs is exactly the same.  The TIFF IFD0 will contain some TIFF
markers (e.g. ImageWidth, ImageLength, Compression, etc.) which
won't be found in the JPEG IFD0, but that's not a problem if the
reader is prepared to recognize all valid TIFF markers.  At the
same time, The EXIF IFD  in the TIFF file will not include markers
for information already included in IFD0 (e.g PixelXdimension won't
be given because the information has already been included as
ImageWidth).  This won't be a problem for the library, but will
need to be handled at the application level for programs (like
ImageMagick) that want to do image format conversions.

That's it.  Just recognize that the file starts with the TIFF header
and proceed normally.  There are additional TIFF tags which should
be recognized as described in the EXIF spec (2.6.4 "TIFF Rev 6.0
Attribute Information", page 21).  The actual format is described
in the spec starting on page 11, section 2.5.2 "Basic Structure of
Uncompressed RGB data".  The following page includes a nice figure
showing the structure of an entire file.

For completeness, there is one other item which should be dealt
with.  One tag included in TIFF files is the 'Compression' tag.
The TIFF6 spec permits 3 values for this ('1' for uncompressed, 2
for "Modifed Huffman RLE compression", and 32773 for "Packbits RLE
compression").  The JPEG spec include a value ('6') for "JPEG
compressed thumbnail" (no tag for main image), and the TIFF_EP spec
includes a value ('7') for JPEG (baseline) compressed primary image
(that's a TIFF file with the image data in JPEG compressed format).
There's some confusion in my mind about what "libexif" intends to
support, and how it should interface with "libtiff" and "libjepg",
so if I'm boring you with details, sorry (I think what I'd really
like to see is a "libjpextif" that handles every TIFF, JPEG and
EXIF tag ever invented).

At the risk of boring you further, and requiring that this message
be divided into several volumes, I'm going to include some output
from a small program I've been using to try to understand the
structure of jpeg/tiff/exif files of various sorts.  If you are
able to interpret them, they may make the difference between reading
Exif from a jpeg format file and from a tiff format file clearer.

First, here's the start of an EXIF/JPEG file:
(The lines are longer than 80 characters, so beware of line wrap.)

@0000000=00000000:  JPEG SOI 0xffd8 
@0000002=0x000002:  <JPEG_APP1> length 14405, "Exif"
@0000012=0x00000c:  TIFF(II) 0x4949 0x42 (ifd offset = 0000008=0x0008)
@0000020=0x000014:  <IFD0 > 11 entries (at offset 0000022=0x000016)
@0000022=0x000016:      <0x010e=  270> [ImageDescription         ] 0x2=ASCII      11    @158
@0000034=0x000022:      <0x010f=  271> [Make                     ] 0x2=ASCII       6    @190
@0000046=0x00002e:      <0x0110=  272> [Model                    ] 0x2=ASCII       5    @214
@0000058=0x00003a:      <0x0112=  274> [Orientation              ] 0x3=SHORT       1    =1
@0000070=0x000046:      <0x011a=  282> [XResolution              ] 0x5=RATIONAL    1    @228
@0000082=0x000052:      <0x011b=  283> [YResolution              ] 0x5=RATIONAL    1    @236
@0000094=0x00005e:      <0x0128=  296> [ResolutionUnit           ] 0x3=SHORT       1    =2
@0000106=0x00006a:      <0x0131=  305> [Software                 ] 0x2=ASCII       9    @244
@0000118=0x000076:      <0x0132=  306> [DateTime                 ] 0x2=ASCII      20    @276
@0000130=0x000082:      <0x0213=  531> [YcbCrPositioning         ] 0x3=SHORT       1    =2
@0000142=0x00008e:      <0x8769=34665> [Exif IFD Pointer         ] 0x4=LONG        1    =284
@0000158=0x00009e:    ============= VALUES, IFD0 ============
@0000158=0x00009e:  ImageDescription:             
@0000190=0x0000be:  Make:   NIKON
@0000214=0x0000d6:  Model:   E990
@0000228=0x0000e4:  XResolution:  300/1
@0000236=0x0000ec:  YResolution:  300/1
@0000244=0x0000f4:  Software:   E990v1.0
@0000276=0x000114:  DateTime:   2002:06:20 12:13:26
    @00296=0x0128:  <EXIF IFD > 24 entries (at offset 284)
    @00298=0x012a:      <0x829a=33434> [ExposureTime             ] 0x5=RATIONAL    1    @590
    @00310=0x0136:      <0x829d=33437> [FNumber                  ] 0x5=RATIONAL    1    @598
        .
        .
        .
        etc.

Now a similar portion of an EXIF/TIFF file

@0000000=00000000:  TIFF(II) 0x4949 0x42 (ifd offset = 0000008=0x0008)
@0000008=0x000008:  <IFD0 > 19 entries (at offset 0000010=0x00000a)
@0000010=0x00000a:      <0x0100=  256> [ImageWidth               ] 0x4=LONG        1    =2048
@0000022=0x000016:      <0x0101=  257> [ImageLength              ] 0x4=LONG        1    =1536
@0000034=0x000022:      <0x0102=  258> [BitsPerSample            ] 0x3=SHORT       3    @242
@0000046=0x00002e:      <0x0103=  259> [Compression              ] 0x3=SHORT       1    =1
@0000058=0x00003a:      <0x0106=  262> [PhotometricInterpretation] 0x3=SHORT       1    =2
@0000070=0x000046:      <0x010e=  270> [ImageDescription         ] 0x2=ASCII      11    @248
@0000082=0x000052:      <0x010f=  271> [Make                     ] 0x2=ASCII       6    @280
@0000094=0x00005e:      <0x0110=  272> [Model                    ] 0x2=ASCII       5    @304
@0000106=0x00006a:      <0x0111=  273> [StripOffsets             ] 0x4=LONG      192    @1322
@0000118=0x000076:      <0x0112=  274> [Orientation              ] 0x3=SHORT       1    =1
@0000130=0x000082:      <0x0115=  277> [SamplesPerPixel          ] 0x3=SHORT       1    =3
@0000142=0x00008e:      <0x0116=  278> [RowsPerStrip             ] 0x4=LONG        1    =8
@0000154=0x00009a:      <0x0117=  279> [StripByteCounts          ] 0x4=LONG      192    @2090
@0000166=0x0000a6:      <0x011a=  282> [XResolution              ] 0x5=RATIONAL    1    @318
@0000178=0x0000b2:      <0x011b=  283> [YResolution              ] 0x5=RATIONAL    1    @326
@0000190=0x0000be:      <0x0128=  296> [ResolutionUnit           ] 0x3=SHORT       1    =2
@0000202=0x0000ca:      <0x0131=  305> [Software                 ] 0x2=ASCII       9    @334
@0000214=0x0000d6:      <0x0132=  306> [DateTime                 ] 0x2=ASCII      20    @366
@0000226=0x0000e2:      <0x8769=34665> [Exif IFD Pointer         ] 0x4=LONG        1    =386
@0000242=0x0000f2:    ============= VALUES, IFD0 ============
@0000242=0x0000f2:  BitsPerSample:  8,8,8
@0000248=0x0000f8:  ImageDescription:             
@0000280=0x000118:  Make:   NIKON
@0000304=0x000130:  Model:   E990
@0001322=0x00052a:  StripOffsets:  72009,121161,170313,... -> 2090
@0002090=0x00082a:  StripByteCounts:  49152,49152,49152,... -> 2858
@0000318=0x00013e:  XResolution:  300/1
@0000326=0x000146:  YResolution:  300/1
@0000334=0x00014e:  Software:   E990v1.0
@0000366=0x00016e:  DateTime:   2001:03:30 17:16:29
    @00386=0x0182:  <EXIF IFD > 19 entries (at offset 386)
    @00388=0x0184:      <0x829a=33434> [ExposureTime             ] 0x5=RATIONAL    1    @620
    @00400=0x0190:      <0x829d=33437> [FNumber                  ] 0x5=RATIONAL    1    @628
        .
        .
        .
        etc.

Hint: the first column is offset from beginning of file in decimal=hex.

-----------
dhh @ androcles.com

Re: [Libexif-devel] Exif in Tiff files

[Hubert F. <hfi...@te...>]

On jeu, 2002-07-25 at 20:17, ap...@sm... wrote:
> Hi Lutz!
>=20
> Ok, with the instructions from Hubert and my creativity :-) know I have a=
nother
> error message:
>=20
> [nbandres:/tmp/libexif/]% cvs
> -d:pserver:ano...@cv...:/cvsroot/libexif diff -u=
3 -p
> ? Debug
> ? libexif.dsp
> ? libexif.dsw
> ? libexif.ncb
> ? libexif.opt
> ? libexif.plg
> ? libexif.spec
> ? libexif/config.h
> ? po/Makefile.in
> ? test/test-mem
> ? test/test-tree
> cvs server: Diffing .
> /#cvs.lock): No such file or directoryctory for `/cvsroot/libexif/libexif
> 'vs server: failed to obtain dir lock in repository `/cvsroot/libexif/lib=
exif
> cvs [server aborted]: read lock failed - giving up
>=20
> Any other clue?
>=20

Try again.

That usually solves the problem.

Hub

Re: [Libexif-devel] Exif in Tiff files

[<ap...@sm...>]

Hi Lutz!

Ok, with the instructions from Hubert and my creativity :-) know I have another
error message:

[nbandres:/tmp/libexif/]% cvs
-d:pserver:ano...@cv...:/cvsroot/libexif diff -u3 -p
? Debug
? libexif.dsp
? libexif.dsw
? libexif.ncb
? libexif.opt
? libexif.plg
? libexif.spec
? libexif/config.h
? po/Makefile.in
? test/test-mem
? test/test-tree
cvs server: Diffing .
/#cvs.lock): No such file or directoryctory for `/cvsroot/libexif/libexif
'vs server: failed to obtain dir lock in repository `/cvsroot/libexif/libexif
cvs [server aborted]: read lock failed - giving up

Any other clue?

Thanks.

Andres.

Re: [Libexif-devel] Exif in Tiff files

[Hubert F. <hfi...@te...>]

According to ap...@sm... <ap...@sm...>:
> Hi Lutz!
>=20
> Quoting Lutz M=FCller <lu...@us...>:
>=20
> > Could you send me a "cvs diff -u3 -p" of that?
>=20
> I tried, and it said to me:
>=20
> [nbandres:/tmp/libexif/]% cvs
> -d:pserver:ano...@cv...:/cvsroot/libexif login
> Logging in to :pserver:ano...@cv...:2401/cvsroot=
/libexif
> CVS password:=20

This is only needed ONCE.

>=20
> [nbandres:/tmp/libexif/]% cvs diff -u3 -p -d
> ":pserver:ano...@cv...:/cvsroot/libexif" libexif=
 | more
> cvs diff: authorization failed: server cvs.libexif.sourceforge.net reject=
ed acce
> for user anonymousxif
> cvs diff: used empty password; try "cvs login" with a real password

"cvs diff -u3 -p" is enough since you already are in checked out tree.

Note that -d option always come BEFORE the cvs subcommand.


Hub
--=20
Job-less AbiWord hacker. - http://www.teaser.fr/~hfiguiere/
Cell phone: +33 6 18 01 42 11
GPG fingerprint: 6C44 DB3E 0BF3 EAF5 B433  239A 5FEE 05E6 A56E 15A3

Re: [Libexif-devel] Exif in Tiff files

[<ap...@sm...>]

Hi Lutz!

Quoting Lutz M=FCller <lu...@us...>:

> Could you send me a "cvs diff -u3 -p" of that?

I tried, and it said to me:

[nbandres:/tmp/libexif/]% cvs
-d:pserver:ano...@cv...:/cvsroot/libexif login
Logging in to :pserver:ano...@cv...:2401/cvsroot=
/libexif
CVS password:=20

[nbandres:/tmp/libexif/]% cvs diff -u3 -p -d
":pserver:ano...@cv...:/cvsroot/libexif" libexif=
 | more
cvs diff: authorization failed: server cvs.libexif.sourceforge.net reject=
ed acce
for user anonymousxif
cvs diff: used empty password; try "cvs login" with a real password

The username ("anonymousxif") is strange, but I don't know why. Any clue?

Andres.

Re: [Libexif-devel] Exif in Tiff files

[Lutz <lu...@us...>]

On Wed, 2002-07-24 at 20:03, ap...@sm... wrote:
> Finally, I had the time to use the CVS version of libexif. It works fine!=
 Also,=20
> after a few changes, I compiled the libexif in Visual C++ 6.0 (Windows).

Could you send me a "cvs diff -u3 -p" of that?

Lutz
--=20
+----------------------------------------------+
| Lutz M=FCller                 +49 (7156) 34837 |
|                                              |
| Hans-Sachs-Strasse 5                         |
| 71254 Ditzingen       http://www.topfrose.de |
| Germany           lu...@us... |
+----------------------------------------------+

Re: [Libexif-devel] Exif in Tiff files

[<ap...@sm...>]

Hi Lutz!

Quoting Lutz M=FCller <lu...@us...>:

> Yes. I committed a fix to CVS such that libexif now saves the
> Interoperability IFD Pointer in the EXIF IFD.=20

Finally, I had the time to use the CVS version of libexif. It works fine!=
 Also,=20
after a few changes, I compiled the libexif in Visual C++ 6.0 (Windows). =
So if=20
you need the source code and proyect that I'm using to do that, let me kn=
ow.

Andres.

Re: [Libexif-devel] Nikon MakerNote support - what needs to be done?

[Lutz <lu...@us...>]

On Fri, 2002-07-19 at 16:33, Peter Teichman wrote:
> I'm very interested in working on support for Nikon MakerNote tags.=20
> What needs to be done?  It looks like the MakerNote support in general
> isn't wired up at the moment.  Is this the case?

Exactly. What you see in CVS is an attempt to a framework for
MakerNotes. Often, MakerNotes are a simple list of values, for example

Brightness: 3420
Contrast: -1.5

The problem is that they are not standardized. And that I don't have the
specifications of any manufacturers' MakerNotes.

If you think the framework that is in CVS is useful, you could code for
example along libexif/olympus. But if you have other ideas on how to
handle MakerNotes, please tell them.

Lutz
--=20
+----------------------------------------------+
| Lutz M=FCller                 +49 (7156) 34837 |
|                                              |
| Hans-Sachs-Strasse 5                         |
| 71254 Ditzingen       http://www.topfrose.de |
| Germany           lu...@us... |
+----------------------------------------------+

[Libexif-devel] Nikon MakerNote support - what needs to be done?

[Peter T. <pe...@xi...>]

I'm very interested in working on support for Nikon MakerNote tags. 
What needs to be done?  It looks like the MakerNote support in general
isn't wired up at the moment.  Is this the case?

Peter

Re: [Libexif-devel] Exif in Tiff files

[Lutz <lu...@us...>]

On Wed, 2002-07-10 at 15:58, Paul Nolan wrote:

(...)

> so while I don't think you`ll find a=20
> standard EXIF header, the data is there.

It seems TIFF just saves a directory (IFD) without header. It should be
easy to adjust libexif to scan that. However, I won't do that - libexif
does all I need (reading/writing EXIF data as described in the standard)
and I honestly have no ambition to search for a TIFF spec and
read/understand that.=20

But if you like, have a look at
libexif/exif-data.c/exif_data_load_data_content and see if you can adapt
it. Patches welcome.

Lutz
--=20
+----------------------------------------------+
| Lutz M=FCller                 +49 (7156) 34837 |
|                                              |
| Hans-Sachs-Strasse 5                         |
| 71254 Ditzingen       http://www.topfrose.de |
| Germany           lu...@us... |
+----------------------------------------------+

Re: [Libexif-devel] Exif in Tiff files

[<pa...@id...>]

> I had a look at it, searched for the ASCII string "Exif" and couldn't
> find it. I know that TIFF uses something like EXIF (or EXIF has been
> designed with TIFF in mind), but: Are you sure there is real EXIF
> information in the TIFF file?

Well, these files contain TIFFTAG_ExifOffset 0x8769, which is supposed to be 
an offset to a private exif directory (in this case somewhere around 0x670 
bytes into the file, +-8 due to tiff values being offset 8 bytes past the 
start of the file), and software such as NikonView is able to read settings 
such as shutter speed and focal length, so while I don't think you`ll find a 
standard EXIF header, the data is there.  Hmm, now I`m confused, I can't find 
the tags in the file that NikonView says are there.  Ah, hang on, they are 
there, but in a different byte order.  For that file, the shutter speed was 
1/250 at f/11, ISO 200, focal length 25mm if that helps you find the values in 
the file.

Thanks,

Paul Nolan, CEO Idruna Software Inc.
http://www.idruna.com

Re: [Libexif-devel] Exif in Tiff files

[Lutz <lu...@us...>]

On Wed, 2002-07-10 at 12:51, Paul Nolan wrote:
> Sorry, I don't actually have a Nikon D1x so can't change the image size, =
all I=20
> have are sample images, but what I`ll do is take one that was grossly und=
er=20
> exposed and zip it, that brings it down to 2.2mb:

I had a look at it, searched for the ASCII string "Exif" and couldn't
find it. I know that TIFF uses something like EXIF (or EXIF has been
designed with TIFF in mind), but: Are you sure there is real EXIF
information in the TIFF file?

Lutz
--=20
+----------------------------------------------+
| Lutz M=FCller                 +49 (7156) 34837 |
|                                              |
| Hans-Sachs-Strasse 5                         |
| 71254 Ditzingen       http://www.topfrose.de |
| Germany           lu...@us... |
+----------------------------------------------+

Re: [Libexif-devel] Exif in Tiff files

[Lutz <lu...@us...>]

On Wed, 2002-07-10 at 10:55, Paul Nolan wrote:
> I`m just uploading a 7.7mb tif file now that has exif info embedded, crea=
ted=20
> by a Nikon D1H. http://www.idruna.com/~upload/DSC_0020.TIF

Is it really necessary for me to download 7.7mb (over ISDN)? Don't you
have something smaller, like 1mb for example?

Lutz
--=20
+----------------------------------------------+
| Lutz M=FCller                 +49 (7156) 34837 |
|                                              |
| Hans-Sachs-Strasse 5                         |
| 71254 Ditzingen       http://www.topfrose.de |
| Germany           lu...@us... |
+----------------------------------------------+

Re: [Libexif-devel] Exif in Tiff files

[<pa...@id...>]

Hi Lutz,

I`m just uploading a 7.7mb tif file now that has exif info embedded, crea=
ted=20
by a Nikon D1H. http://www.idruna.com/~upload/DSC_0020.TIF
I tried using libtiff to get the pointer to the exif data, and then using=
 the=20
exif_data_new_from_data function to read it in from memory, but I`m not=20
familiar enough with the exif standard to get any success.

Thanks!

> > Is it possible to use libexif to access the exif information embedded=
 in=20
> > tiff files?
>=20
> I only tested libexif using JPEG files. If exif_data_new_from_file
> doesn't work, either try to come up with a patch or send me a sample
> TIFF image containing EXIF data.
>=20
> Lutz
> --=20
> +----------------------------------------------+
> | Lutz M=FCller                 +49 (7156) 34837 |

Paul Nolan, CEO Idruna Software Inc.
http://www.idruna.com

Re: [Libexif-devel] Exif in Tiff files

[Lutz <lu...@us...>]

On Wed, 2002-07-10 at 15:43, ap...@sm... wrote:
> I was using the libexif=20
> (versions 0.5.1 and 0.5.3) and when I try to verify the JPEG/EXIF created=
, the=20
> software said to me that the Interoperability IFD Pointer (0xA005) is "in=
side"=20
> the 0th IFD, not the Exif_IFD (where it's supposed to be). Is this a prob=
lem on=20
> the library,

Yes. I committed a fix to CVS such that libexif now saves the
Interoperability IFD Pointer in the EXIF IFD.=20

If you like, check out the current CVS version and tell me if it works.

Lutz
--=20
+----------------------------------------------+
| Lutz M=FCller                 +49 (7156) 34837 |
|                                              |
| Hans-Sachs-Strasse 5                         |
| 71254 Ditzingen       http://www.topfrose.de |
| Germany           lu...@us... |
+----------------------------------------------+

Re: [Libexif-devel] Exif in Tiff files

[<ap...@sm...>]

Hi!

I imagine that this question is for Lutz... :-) I was using the libexif 
(versions 0.5.1 and 0.5.3) and when I try to verify the JPEG/EXIF created, the 
software said to me that the Interoperability IFD Pointer (0xA005) is "inside" 
the 0th IFD, not the Exif_IFD (where it's supposed to be). Is this a problem on 
the library, or there's some way to put one pointer inside the other?

To verify the JPEG/EXIF files I'm using a Fuji application.

Thanks...

Andres.

Re: [Libexif-devel] Exif in Tiff files

[Lutz <lu...@us...>]

On Tue, 2002-07-09 at 23:42, Paul Nolan wrote:
> Is it possible to use libexif to access the exif information embedded in =
tiff=20
> files?

I only tested libexif using JPEG files. If exif_data_new_from_file
doesn't work, either try to come up with a patch or send me a sample
TIFF image containing EXIF data.

Lutz
--=20
+----------------------------------------------+
| Lutz M=FCller                 +49 (7156) 34837 |
|                                              |
| Hans-Sachs-Strasse 5                         |
| 71254 Ditzingen       http://www.topfrose.de |
| Germany           lu...@us... |
+----------------------------------------------+